Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, January 7, 2015 8:42 AM
Hey,
I have a very strange behavior.
During SCCM PXE deployment I use windows PE.
If I boot first time into windows PE the property "Win32_TimeZone" -> Bias or ActiveTimeBias or TimeZoneKeyName are all correct. (Same with the registry keys in HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation)
If I now restart again into windows PE (e.g. because the Windows PE loaded from WDS is a different one then the one assigned to TaskSequence or because I do a restart into Windows PE assigned to Task Sequence) the properties are all set to "Pacific Standard Time".
Does anyone know where this comes from?
Is there a fix available for it?
Thank you for help
Kind Regards
mk-maddin
All replies (3)
Thursday, January 8, 2015 8:31 AM âś…Answered
Hi,
You could try to sync the time with a server using the method in the blog below.
"I had the idea to try and sync time whilst the PC is still in the WinPE environment and it turns out it can be done, albeit using a different method. There are no W32Time services etc in WinPE so we have to look back to the old NT days where we used to use a command called NET TIME. Lo and behold, this old command set works in WinPE!
The next problem was getting WinPE to be in the right Time Zone. As default, WinPE is set to Pacific Time GMT-8. This can be changed by building the WinPE boot.wim to be set to your localised zone but in order to avoid having to do that, I just exported a registry file from HKLM\System\CurrentControlSet\Control\TimeZoneInformation and place these two files in the DeploymentShare$\Scripts folder on the deployment servers"
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Best Regards,
Joyce
Wednesday, January 7, 2015 9:59 AM
In what use case does this matter at all? The time zone will usually be corrected after the client retrieved policies from the MP.
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, January 7, 2015 12:32 PM
Hey Thorsten,
mostly this doesn't matter. But in my case it does...
The scenario used is error handling. If an error appears the log files are copied automatically to central server. Additionally a WMI query for the task sequence status message queries are performed. The error is highlighted with red. For this the UTC time is required.
This is very helpful if some problems like local bios settings etc. are the reason for the failure.
The technical engineers installing devices can fix the problem by themselves without need to contact SCCM admins.
Here is a screenshot of the resolution that is displayed (if the UTC value is correct):
