agarabaghi Posted September 25, 2013 Posted September 25, 2013 For some reason when I deploy my regular task sequence on some machines it seems to reboot mid application installs and then the deployment prompts that an in-progress sequence has been detected and would you like to continue or start over. Hitting continue works and it finished with 0 errors. But what could be causing this?
morganw Posted September 25, 2013 Posted September 25, 2013 Running an application installer without suppressing it's reboot request will do this. Differences may be down to prerequisites (such as Visual C++ runtime) being already on some machines. I've also seen installation problems when using HIDESHELL=YES with certain applications.
agarabaghi Posted September 25, 2013 Author Posted September 25, 2013 THe thing is this same customesettings.ini file would work without issue in MDT2010... now sure what has changed.
agarabaghi Posted September 25, 2013 Author Posted September 25, 2013 Is there a way to see a log file once the deployment has finished and see what is causing the reboots?
ChrisH Posted September 25, 2013 Posted September 25, 2013 Yes look here for locations: MDT 2010 & 2012 Your best using a proper log viewer as well as they usually highlight stuff for you better.
Jamo Posted September 25, 2013 Posted September 25, 2013 Is there a way to see a log file once the deployment has finished and see what is causing the reboots? Yes, go to either c:\MININT\OSDLOGS (i think) (if it still exists) or if the cleanup is finished check C:\Windows\Temp\DeploymentLogs\bdd.log You can read them with the sccm toolkit (free download) which has a log viewer called trace32/cmtrace(in2012) Download System Center 2012 Configuration Manager Service Pack 1 Component Add-ons and Extensions from Official Microsoft Download Center
Jamo Posted September 25, 2013 Posted September 25, 2013 Yes, go to either c:\MININT\OSDLOGS (i think) (if it still exists) or if the cleanup is finished check C:\Windows\Temp\DeploymentLogs\bdd.log You can read them with the sccm toolkit (free download) which has a log viewer called trace32/cmtrace(in2012) Download System Center 2012 Configuration Manager Service Pack 1 Component Add-ons and Extensions from Official Microsoft Download Center Also read bdd.log in both cases, it is an amalgamation of all the logs together
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now