Yes, I ran this on my Win2K system when creating this script. Recommend checking the registry to confirm these keys exist/are accessible to you. Perhaps, though I am not sure, it may be an issue with local user rights in seeing these keys. Since not all users can adjust the clock of a WinNT/2K system, the user id you are testing with may be restricted in this manner. Check User Manager, User Rights, Change the System Time entry to confirm for your network.FYI - a quick check of a WinNT system also shows the presence of these keys.
As for these being 'REG_NONE', I an not sure of your point, except perhaps this indicates the possible security restrictions I noted above.
As for variable to send to another script - I assume you want a variable that reflects GMT time in comparison with the local workstation time. That could be something like: $PassGMT = $GmtHr + ":" + $GmtMin + ":" + $ChkSec (a variable not parsed in original version of script I posted but you can add. There is no point in adjusting this value seperately as GMT offsets do not account for seconds). $PassGMT should look like: 09:23:37. I have not tested this.
Of course, the accuracy of $PassGMT is only as good as the accuracy of the local workstation clock. If the GMT time is very important, you also require a good time server to keep accurate time that can be checked at every login (or perhaps more frequently) by each workstation so the local clock can be synchronized. The time server will need to check with authoritative source such as U.S. Naval atomic clock, etc.
Also, if your company has offices in multiple time zones you must confirm each workstation properly set for the correct time zone, and authenticates against time server within its time zone. If systems configured centrally and distributed nationally, possibly time zones improperly set to configuration center time zone.
Bill
