Why did the machine go back in time? Do other machines that don't break the laws of physics continue without error? :) Was there a big change in TimeZone, were the machines just wildly out of sync?
Executing command line: "C:\_SMSTaskSequence\OSD\ICC0001E\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\ICC0001E /config:MobileClient.TCF /status:536 OSDSetupHook 9/11/2015 5:02:42 PM 1928 (0x0788) Process completed with exit code 0 OSDSetupHook 9/11/2015 2:08:31 PM 1928 (0x0788) From: [email protected] [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Friday, September 11, 2015 12:40 PM To: [email protected] Subject: RE: [MDT-OSD] Failing TS Here you go. I don't see anything bad.. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Keith Garner (Hotmail) Sent: Friday, September 11, 2015 2:03 PM To: [email protected] <mailto:[email protected]> Subject: RE: [MDT-OSD] Failing TS Can you share the Smsts.log (compressed). From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Friday, September 11, 2015 10:27 AM To: [email protected] <mailto:[email protected]> Subject: [MDT-OSD] Failing TS We have upgraded our server to 2012 SP2 and CU5. We still have MDT 2012 Update 1 installed, 2013 Update 1 is in the works if I can keep other stuff from breaking. We have also upgraded the ADK for Windows 10 also. Now our existing Task Sequences are failing! I have been scratch my head on this and I just don't get it. It runs all the way up to this step: Once it gets there, it says it is installing the ConfigMgr client for a few minutes, then just blows out of the TS and straight to the login screen for Windows. It never finishes the TS, just dies. I have never seen this before! I am guessing something with the upgrade and I may need to recreate my Task Sequences to fix? If that is the case, I will get on 2013 Update 1 since I will need to create new ones then. Any input/insight/thoughts are much appreciated. Mike L.
