Article ID: 894567
Article Last Modified on 10/18/2006
APPLIES TO
- Microsoft Internet Explorer 6.0
- Windows Internet Explorer 7 for Windows XP
- Windows Internet Explorer 7 for Windows Server 2003
- Windows Internet Explorer 7 for Windows Server 2003 IA64
SYMPTOMS
When you try to connect to a server by using Remote Desktop Connection with a new user account, some registry subkeys that are related to Microsoft Internet Explorer or Windows Internet Explorer may be missing. This problem occurs if the server is using Internet Explorer as a shell.
The toolbars in Internet Explorer may not be displayed correctly or may be missing. Home pages and proxy settings that are defined by Group Policy settings may not be applied.
When you investigate the registry for that user profile, you see that many subkeys are missing in the following subkeys:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
In Microsoft Windows Server 2003, the IEHarden key is not created, and you are not prompted that the site is not in a secure zone. Active Setup also does not run when Internet Explorer is not set up as the shell when you log on for the first time.
CAUSE
Large sections of your registry are not created until you log on for the first time. The HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client subkey does not exist in the HKEY_USERS\.DEFAULT\Software\Microsoft branch before you log on.
HKEY_USERS\.DEFAULT is the template for all new users on any Windows computer. The Terminal Server Client branch is not created until after the user logs on the first time.
When Internet Explorer replaces Windows Explorer as the shell, this branch is not created until after you are logged on the first time. Therefore, some security settings may not be available until you log on the second time.
WORKAROUND
To work around this problem, use one of the following methods:
- Log on to a full desktop to let Active Setup complete the setup of Internet Explorer.
- Set the .default profile to include the required registry subkeys for new users. Typically, you can do this by importing the Terminal Server Client subkey from the HKEY_CURRENT_USER hive of the registry to the .default user profile.
- Create a logon script that adds the registry subkeys that are missing.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
Keywords: kbtshoot kbregistry kbprb KB894567
