I'll look into filing it tomorrow on connect. We are exclusively using the application catalog because we are advertising to users, not devices. Because of this, we need to use applications and cannot use task sequences or packages.
On Thu, Jun 20, 2013 at 6:47 PM, Benjamin Monrad <[email protected]>wrote: > This may or may not be helpful as a workaround, but I have an AV client > migration I'm running with Package and Program (not Application) chained > with "Run another program first", if that is an option... > 1. .bat file to remove old AV, ConfigMgr restarts system > 2. Install AV management agent > 3. Install AV client > > In the past I had one chained like this, when the client package was like > 300MB and we didn't want to wait so long for download after the old AV was > removed. > 1. cmd.exe /c dummy program to download AV management agent to cache > 2. cmd.exe /c dummy program to download AV client to cache > 3. .Bat file remove old AV, ConfigMgr forces reboot > 4. Install AV management agent > 5. Install AV client > > I know you lose some of the value of the Application model, but it gets > the desired effect in the end. > > > > > On Thu, Jun 20, 2013 at 10:36 AM, 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.**** >> >> ** ** >> >> ** ** >> >> ** ** >> >> > >
