Article ID: 974636 - View products that this article applies to.
Consider the following scenario:
AD RMS caches a pool of global catalog servers to improve the performance of Active Directory queries. When a global catalog server becomes unavailable, the global catalog server should be removed from the pool.
However, the removal of some faulty global catalog servers does not work as expected. Those faulty global catalog servers remain in the pool until the server that is running Internet Information Services (IIS) restarts. Therefore, some RMS jobs fail when AD RMS queries these global catalog servers. This behavior causes AD RMS to stop working when the whole pool contains faulty global catalog servers.
To work around this issue, you could use the "iisreset.exe" command to restart the IIS service on the server that is running IIS without having to restart the server.
Hotfix informationA 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 Web site:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesTo apply this hotfix, the computer must be running Windows Server 2008 R2. Additionally, the computer must have Active Directory Rights Management Services installed.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfix.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2008 R2 file information note
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately . MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
Article ID: 974636 - Last Review: October 14, 2009 - Revision: 1.1