Jump to content

Recommended Posts

Posted

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?

Posted
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.
Posted
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

Posted
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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...