We have the same problem. We have just instructed our helpdesk to tell the users to install one application first, and then the other.
On Thu, Jun 20, 2013 at 12:36 PM, Brian Marobella < [email protected]> wrote: > Hi All,**** > > We're trying to deploy to a ConfMgr 2012 SP1 application that has a > dependency on another app that requires a reboot before the deployment can > proceed. The issue that we have is there doesn’t seem to be a way to > instruct the deployment to proceed where it left off after the reboot. > This would be similar to how a Task Sequences Restart command picks up at > the next command after the Task Sequence reboot. Using a Task Sequence in > this case does not help because the software is made available to users, > not devices. **** > > ** ** > > The only options we think we have are:**** > > **1. **Create an all-inclusive scripted installation that installs > the dependent app, set the auto logon and run once reg keys, reboots and > completes the application installation**** > > **2. **Tell the user to restart the deployment from the catalog > after the reboot. **** > > ** ** > > ** ** > > We can’t be the only admins running into this issue when deploying > App-Model deployments. I figure I’d throw it out there to see what, or if, > there is a way in ConfigMgr App-Model to provide a complete solution for > our users.**** > > ** ** > > Thanks for your time.**** > > ** ** > > ** ** > > ** ** > >
