John.
The users must be able write timeserv.exe to %SYSTEMROOT%\System32 and timeserv.ini to %SYSTEMROOT%. This means that assuming the user is running this as part of their Login Script, they'll need to have write permissions (Local Admin Rights?) to the target directories. One way of avoiding this would be to use your admin rights and put the files directly on to the users' pc.
Logged on as an Administrator, you should be able to put the files on to the local workstations remotely.Try a "net use t: \\workstation-name\c$" in a command prompt from your workstation; this should map t: to the remote c: drive. You can then copy the files manually.
("net use t: /d" to delete the mapping afterwards!)
You've still got the problem of installing the service now that the files are on the local HDD; Normal users won't have permissions to write in the services section of the local registry.
If you're just trying to sync client PC times, why not try out what the MS Article below says; leave the PDC to TimeSync with whatever it's currently talking to, and follow these instructions for setting up the PDC.
http://support.microsoft.com/support/kb/articles/Q131/7/15.asp?LN=EN-GB&SD=gn&FR=0
Then all you'll need to do in the Client Login Script is a
"net time \\pdc /set /yes"
This is literally what your client login .bat will need to say, possibly preceeded with an "@echo off" to keep it tidy!
Good Luck,
Jason.