Is it showing exactly 24 hours in advance? I've seen the time in the logs be off before but never that far off. The time being off has to do with timezone, WinPE portions of the TS do not have a set timezone which causes inconsistencies in the logs when it's later converted. However, I do not believe this has anything to do with the functionality of KMS. Windows attempts to activate every time it connects to the network by looking through DNS for the appropriate KMS entry. If after several reboots post-deployment the machines are still not activating automatically, then there's a KMS and/or DNS configuration problem, not a TS problem.Scott Gill SCCM Consultant

If the task sequence is running in full OS then it uses the OS time. If the task sequence is running in WinPE then it uses the time from the BIOS without allowing for timezones. In my TS I a step to activate - cscript.exe c:\windows\system32\slmgr.vbs /ipk [KMS key]

Hi, We r facing issue in OSD ..my whole task sequence runs perfectly but systems are not getting activated automatically through KMS. After drill down I found SMSTS log modified date show tommorrows date. Machines are comes in domain in tasj sequence and update its time to proper time. Manaually I can activate through KMS. Please suggest. From where it is getting time and date information while task sequence run? SiddheshM MCTS