Welcome to KORG!!

DO NOT use scripts to sync time. Time - since NT/XP - has been handled through Windows AD. For workstations, the W32time process provides adequate time sync with no administrative effort.

For Windows 2000/2003 servers running mission-critical services - NOT AD SERVERS!! - a third-party NTP service should be used to provide higher time accuracy.

The best solution is to use NTP on a server or router and obtain time from an external source. Have your PDCe obtain time from that device - this is the only configuration needed. All other DCs sync automatically with the PDCe, and all workstations sync automatically with the DCs. Everything is happy. Mission-critical servers use a 3rd party service to sync with the primary time server.

Windows 2008 servers do provide higher accuracy sync. This higher accuracy is usually only needed for servers involved in SQL processing - the database servers and their clients. A fully ported version of NTP for windows is available from http://www.meinberg.de/english/sw/ntp.htm.

As far as your printer errors go, try adding a @SERROR macro to your error message so you can see what error occurred. Something like
 Code:
@SERROR ' occurred when adding printer' @CRLF


Glenn
_________________________
Actually I am a Rocket Scientist! \:D