A Group Policy object is not applied as expected after you restart a Windows XP-based client computer or a Windows Server 2003-based computer (886516)
The information in this article applies to:
- Microsoft Windows XP Professional
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Media Center Edition
- Microsoft Windows XP Tablet PC Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
SYMPTOMSWhen you restart your Microsoft Windows XP-based client
computer or
your Microsoft Windows Server 2003-based computer after
you join a domain, a Group Policy object (GPO) may not be applied as
expected.CAUSE This issue may occur if the client's computer system clock
is set to a different time than the time that is set on the domain controller
computer. WORKAROUNDTo work around this issue, use one of the following methods. Method 1: Resync the computer before you restartTo make sure that the GPO is applied successfully when you restart
the client computer, follow these steps before you restart the client computer:
- Click Start, click Run,
type cmd, and then click OK.
- At the command prompt, type the following commands, and
then press ENTER at the end of each command:
w32tm /config /update
w32tm /resync Note After you complete each command, you receive the following
message:The command completed
successfully. - Type exit, and then press ENTER to
quit the command prompt.
- Restart your client computer.
Method 2: Restart the client computer two timesTo make sure that the GPO is applied successfully, restart your
client computer two times after you first join the domain.
Modification Type: | Major | Last Reviewed: | 9/22/2006 |
---|
Keywords: | kbtshoot kbprb KB886516 kbAudEndUser kbAudITPRO |
---|
|