>>Hi,
>>
>>I know we have some networking people around here, so hopefully one of you can tell me what needs to be done.
>>
>>I have a small network with 6 workstations connected to a file server running WIndows Server 2003. They are all part of a domain. For whatever reason, the users do an end of day procedure at about 2pm. They change the date on their workstations to be "tomorrow's" date, so that all transactions after 2pm get posted as being for "tomorrow". This was actually done previously by changing the server date and the workstations would automatically synchronize date with the server.
>>
>>The server died on Monday so a new server was swapped in. The new server was supposed to have been configured exactly like the old one, but something seems to be missing as the date/time synchronisation is not happening.
>>
>>For now, they are changing the date on each workstation and not on the server, but if they forget to change it back before shutting down, the next day they get a message that they cannot log onto the domain because the date/time does not match the server's. So they then need to log on to the local PC as an administrator, change the date, log off and then log back onto the domain.
>>
>>Any ideas what I missed? Or any ideas on what I can do so that the date/time gets synchronised when switching the PC on every morning? (I tried a "net time \\myserver /set /y" batch in the user's startup menu, but no go as this seems to run too late).
>>
>>Thanks for any help,
>
>I think all logins have login and logout scripts installed on old server that do this when the user login or logout.

Hi Boris,

no, they didn't have a login script. As a workaround I actually tried to create a login script to do it, but the script fired too late in the startup process: Windows would show the error that the date is incorrect as soon as the user tried to login, before the batch file ran.