Thanks in advance

This issues all smell like a 'Service' coming up!!
A Service which runs under admin privilege on the workstation and listens to a specific commandfile in a specific folder.
If a file with that name is placed in that folder, the command in that file are being executed by the service under admin level.

Regards,

Marc

------------------
M.A.C. Duiker (Marc)
Migration Specialist (MCSE)
MarcDuiker@CompuServe.com

Hmmmmm...... The brain is chewing on it....

Bryce

first off you will need Timeserv from the NT resource kit, read the htm file and see how it works.

2nd, here is some really rough kic code that I found, that you run on an administrators computer that will install the service on to the workstations.

!!!You should use this just as a guideline for yout final code!!!

Do
$x=$x+1
SHELL "XCOPY C:\TEMP\TIMESERV.* {Workstation}\c$\winnt\system32 /y"
SHELL "XNET INSTALL \\{Workstation}\TimeServ /b:timeserv.exe /n:Time Service/LocalSystem"
SHELL "XNET START \\{Workstation}\TimeServ"
UNTIL X={Number of Workstations}

Any other questions, I would be glad to help
Bryce

here is another way to do what you want.

I believe all that's required is to grant the "Change system time" right to everyone in User Manager for Domains. Pick the domain that the computers are members of. That is, if you have an account domain and one or more resource domains, focus User Manager for Domains (not UM for the local machine) on the resource domain(s). User rights are domain wide so you don't have to do this on each client box.

SETTIME @LSERVER

This is my absolute last reply for now. .

Just a 'junior member' but try this. . . or I may be able to help further with the actual script. . .Its something I have been wanting to try for a long time. Here is the concept.

;;--------------------------------------

During a users logon script processing, you can add a registry entry to make the next
login an automatic admin login, with a RunOnce entry to a batch file or other script. Then initiate a shutdown and restart.

When the machine reboots, it should automatically login using the administrative account. Your RunOnce script should remove the AutoAdmin login, and then initiate a quiet install of SW, before doing another shutdown.

If you create a unique Admin account for doing this, you can assign it a
logon script that does the installation instead of using the RunOnce key.
This means that as the user never leaves the logon script they don't gain admin access to the machine during the installation. If they cancel the script it automatically logs them out, and keeps your security.

To do an automatic logon make the following entries.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="YourAdminAccount"
"DefaultPassword"="AdminPassword"
"DefaultDomain"="YourDomain"
"AutoAdminLogon"="1"

To remove an automatic logon make the following entries.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"=""
"DefaultPassword"=""
"AutoAdminLogon"="0"

;;---------------------------------------

Reduce risk by adding this. It will cause the Login script to run before anything else can be done.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogin\RunLoginScriptSync

;;----------------------------------------