I have a domain controller running Windows Server 2003. I had recently updated a few PCs to Windows 7 Professional x64 that run the 32 bit Windows XP "Mode". The reason for this is so that we can still use our 32 bit VB time clock application along with a few others. The issue I'm having, with these PCs only, is that the time clock will randomly punch out employees sometimes 2 days in the future. The time clock opens a batch file that uses net time /set to sync the time with the server. However this is only allowed by domain admins, and is greyed out in the local policies. The users with the Virtual XP are local admins. The batch file errors with an error 1314 privilege not held by client. I've tried w32tm/resync as well with no positive results. Please help!

Do you really need to be doing that "net time /set" to sync the time on the PC with the DC? Those PCs, if they are joined to the domain, ought to be in sync already with the DC. AFAIK, the ability to change date/time on a PC is a local security policy/right. You would need to manually add the group "YOURDOMAIN\Domain Users" on each PC in question by running the Local Security Policy application, in Security Settings, Local Policies, User Rights Assignment, Change The System Time.As a separate issue, it would seem that there is a bug in the Time Clock application, if it is getting the date/time so wrong that it is sometimes 2 days in the future.