Now use File | Export and save that with an appropriate name, in my case EasternTime.reg to your DeploymentShare$\Scripts folder. Here’s the US Eastern Time Zone rgistry contents on a Windows 10 build: Set the time zone on a device and browse to HKLM\System\CurrentControlSet\Control\TimeZoneInformation. You can #HarryHack it and copy the files needed but that wouldn’t be supported in a strict change control environment so the easy answer is to fall back to the NET TIME command. Some may think to try using W32Time services via W32TM.exe but since the device is still in WinPE that doesn’t exist. So the challenge is how would you set the time, preferably using a script, during the Windows deployment process, in this case using MDT. If you make a request that’s from 16 hours in the past, well, a server would not accept it – make sense? It happened to be in this case that there’s a 16 hour difference right now between China (where the Lenovo BIOS was configured) and the WinPE default timezone which is set to Pacific Time GMT-8. Why would this matter? Well when you make network communications, they are done with a time stamp. The root cause was that these were Lenovo devices and they had a time sync issue. Some failed immediately and others much later because of a failed domain join. There was a curious issue that came about where a small percentage of devices were having issues with OSD.
0 kommentar(er)
