Consider the following scenario:
- You have a Windows Server 2008 R2-based domain environment that has a certification authority (CA) and Remote Desktop certificates configured.
Note For more information about how to configure Remote Desktop certificates, go to the following Microsoft website:
- You have a Windows 7 Service Pack 1 (SP1)-based or Windows Server 2008 R2 SP1-based computer that uses Network Access Protection (NAP) 802.1X enforcement in the domain.
This issue occurs because of a delay in the initial setup of NAP 802.1X configuration when you start the computer. Before the connection from the computer to a domain controller is established, the Remote Desktop Configuration service checks whether the certificates need to be updated. However, the service cannot decode the certificate without domain controller connectivity. Therefore, a new certificate is requested to be generated.
Hotfix informationTo resolve this issue, install the hotfix on the Windows 7 SP1-based or Windows Server 2008 R2 SP1-based computer that uses NAP 802.1X. After you install this hotfix, a ConnectDCTimeoutregistry entry is created under the following registry subkey:
\HKEY_LOCAL_MACHINE\ System\CurrentControlSet\Control\Terminal ServerYou can configure the poll timeout for the domain controller connectivity check by configuring the ConnectDCTimeoutregistry entry.
- The default DWORD value of the ConnectDCTimeoutregistry entry is 20000(20 seconds).
- The minimum DWORD value of the registry entry is 0.
Note Under this configuration, the domain controller connectivity check is performed immediately.
- The maximum DWORD value of the registry entry is 600000(10 minutes).
Note If you set a value that is greater than 600000, the registry entry still uses 600000 as the configuration.
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.
PrerequisitesTo apply this hotfix, you must be running Windows 7 SP1 or Windows Server 2008 R2 SP1.
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
Registry informationTo apply this hotfix, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
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:
824684 Description of the standard terminology that is used to describe Microsoft software updates