Daylight savings time in WinPE RRS feed

  • Question

  • In our MDT environment, we are collecting a lot of data about the deployments and putting them into SQL for reporting. One of the things we are interested in is how long the deployments take.

    In the beginning of the task sequence, we have a Powershell script that gets the current time and puts it into a variable called 'deployStartTime'. At the end of the task sequence we also get 'deployEndTime', and from those two values we can get the total build time.

    The problem is that SOME of our deployments are recording a 'deployStartTime' that is an hour ahead of the actual time, and so the 'deployStartTime' is AFTER the 'deployEndTime' (because once it reboots into Windows 7, the time is correct), which messes up our calculations.

    Our assumption is that this must be due to Daylight Savings Time, but why does it only happen on some builds?

    Does it have to do with when the boot media was generated? That seems unlikely, but since we have lots of techs out there deploying machines (we only use USB boot media, no PXE), the only difference we can think of is the age of their boot ISOs.

    I've done some research, and apparently WinPE just ignores Daylight Savings Time? But why would most of our builds have the correct time in WinPE, but some of them do not?

    EDIT: We are in California, so Pacific Time Zone.

    Tuesday, March 24, 2015 4:45 PM