A machine that has been properly set up will pass this test: > python -c "import datetime;print datetime.datetime.fromtimestamp(1301643000)" > Should yield "2011-04-01 00:30:00" if the DST settings are correct.

Hi, armen, is there an action for relops on this?

(In reply to Amy Rich [:arich] [:arr] from comment #1) > Hi, armen, is there an action for relops on this? We're trying to figure out the XP machines are coming out of imaging without the correct DST.

Mark make sure this kb file is applied the base image: \\dc9\SYSVOL\releng.ad.mozilla.com\files\tz\WindowsXP-KB955839-x86-ENU.exe

On a fresh install of XP I ran: python -c "import datetime;print datetime.datetime.fromtimestamp(1301643000)" and got the expected result. However, I do not see the KB Q mentioned being applied. Should I go ahead and add that KB to the install?

The dst patch 8s applied in gpo however, as I mentioned earlier it woukd be more efficient to put into the base install

Currently applied with the "Set_PDT_Timezone" if you need reference

and to clarify the other parts should remain in GPO as they make sure that machines get the DST timezone set. The only parts that need to be moved are the file copy of the KB.exe and the single scheduled task that applies it.

The scheduled task in the gpo that contained The WindowsXP-KB955839-x86-ENU.exe has been disabled. The KB has been moved into the production task sequence in the step KB955839.bat: cmd /c Z:/scripts/xp/KB955839.bat xcopy Z:\scripts\WindowsXP-KB955839-x86-ENU.exe c:\ cmd /c c:\WindowsXP-KB955839-x86-ENU.exe /quiet /norestart sleep 10 rm c:\WindowsXP-KB955839-x86-ENU.exe When the images are refacter post Windows on Puppet this will be moved into the build task sequence. tested the MDT installed and it completed without error, and the KB was present post install.