I want to create SMS Collections based on Organizational Units. However, when I go to "System Resource", our SMS 2003 site database does not have data for the "System Group Name", "System Container Name", and "System OU Name."
Discovered that the [Active directory system GROUP] discovery populates these values. Turned in on today and "bam"!, there they were!
Wednesday, May 19, 2010
Windows 2003 Server Time Synchronization
Several of the client Windows XP machines are out of synch in regards to the system time. Even the windows servers were out of synch with themselves. To resolve the problem, I needed to use w32tm utility to set the time, not the "net time" command.
A note from http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/db179f69-2a9a-40d9-88de-2b370f7dc863 was helpful, stating that " the “Net Time” command is supposed to work for Windows 2000 based machines. It uses the protocol called Simple Network Time Protocol or SNTP which means it’s a “simple” version of NTP and lacks some of the more complex algorithms which provide more accurate and stable time for NTP clients. For Windows Server 2003 / Windows XP or above machines, they use NTP instead of SNTP. "
The following two commands actually synched the time:
w32tm /config /syncfromflags:manual /manualpeerlist:"clock list"
w32tm /config /update
A note from http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/db179f69-2a9a-40d9-88de-2b370f7dc863 was helpful, stating that " the “Net Time” command is supposed to work for Windows 2000 based machines. It uses the protocol called Simple Network Time Protocol or SNTP which means it’s a “simple” version of NTP and lacks some of the more complex algorithms which provide more accurate and stable time for NTP clients. For Windows Server 2003 / Windows XP or above machines, they use NTP instead of SNTP. "
The following two commands actually synched the time:
w32tm /config /syncfromflags:manual /manualpeerlist:"clock list"
w32tm /config /update
Subscribe to:
Posts (Atom)
