You have a domain controller that is running Windows Server 2008 R2 in an Active Directory domain environment.
You install the Remote Server Administration Tools (RSAT) on a client computer that is running Windows 7.
You start Group Policy Management Console (GPMC), and then create a new Group Policy Object (GPO).
You create a new Scheduled Task (Windows Vista and later) Group Policy preference item in the GPO.
You enable the Apply once and do not reapply option for the preference item.
You apply the GPO to the client computer.
You try to save a report of the Resultant Set of Policy (RSoP) information for the client computer by using one of the following methods:
Use Group Policy Results Wizard in GPMC.
Run the gpresult /h filename command on the client computer.
In this scenario, one of the following issues occurs:
You receive the following error message in GPMC:
An error occurred while generating the report: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index
The gpresult /h filename command generates a blank .html file.
Note These are reporting issues. The Group Policy preference setting is applied to the client computer successfully.
The issue occurs because the Group Policy reporting module incorrectly uses hard-coded index values to query the task information about a scheduled task. If the task information is not saved at the hard-coded index location, these issues occur.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, you must have the RSAT installed.
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
To apply the hotfix in this package, you do not have to make any changes to the registry.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Windows 7 and Windows Server 2008 R2
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
To work around this issue, use one of the following methods:
Disable the Apply once and do not reapply option.
Configure the preference item to be Scheduled Task instead of Scheduled Task (Windows Vista and later).
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to configure a Scheduled Task (Windows Vista and later) preference item, visit the following Microsoft website:
Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Foundation, Windows Server 2008 R2 Standard, Windows Web Server 2008 R2