chimmez Posted December 16, 2015 Report post Posted December 16, 2015 Hi everyone, just a quick and strange bug. I have a captured Windows 10 1511 ENT wim, which is clean except for the removal of a few 'modern' apps (i.e. Xbox etc). This wim is being deployed from SCCM Current Branch and is a really basic task sequence (nothing too complicated going on, just the regular deploy ts). The systems are then being joined to the domain. After about 30 minutes, the date and time of the system reverts to when the Wim was captures (last Friday). Not only does the system time change, it changes the time in the BIOS of the machines. The system gets the correct time at the time of deployment. An Event ID of "1" gets logged, that simply says that the reason for a time change is "An Application or system component changed the time". Any ideas why this would happen? Seems a little odd.. Thanks! Quote Share this post Link to post Share on other sites More sharing options...
Smiley1244 Posted March 11, 2016 Report post Posted March 11, 2016 Hi there, Did you get any where with this issue? I'm seeing the same thing but it happens during the our SCCM TS. I've ensured the wim is correctly sysprep'd but this keeps happening Quote Share this post Link to post Share on other sites More sharing options...
nathan_bird Posted March 15, 2016 Report post Posted March 15, 2016 Same issue being experienced here. Be interested to hear if you managed to get it resolved or not? Quote Share this post Link to post Share on other sites More sharing options...
rbisset Posted March 18, 2016 Report post Posted March 18, 2016 I'm also getting this now too! Quote Share this post Link to post Share on other sites More sharing options...
benjamins Posted April 1, 2016 Report post Posted April 1, 2016 This issue kept me busy the whole freeking week, I gave up frustrated and removed the apps offline via DISM from the original install.wim I created and captured the reference machine on VM (VMware ESXi 5.5 and Hyper-V) with the same effect. Same procedure as i created all Reference machines previously (WIN8.1 and 7 and Server 2012R2), never had this strange behaviour Best Regards from Germany, Benjamin Quote Share this post Link to post Share on other sites More sharing options...
mblack33 Posted April 4, 2016 Report post Posted April 4, 2016 If you go into the registry HKLM/system/services/w32time, try setting the securetimeconfidence calue to 0 Quote Share this post Link to post Share on other sites More sharing options...