PENDING Schedule application to install at next reboot

[abnranger67]

Hi team, I looked but did not find if this was even possible. We were a RES One Automation (Ivanti) shop and just moved to SCCM. In RES, when you schedule a push/deployment, you are presented with a dropdown that offered options such as Immediately, After the next boot, After every boot, etc. Does SCCM have something like that when scheduling? I want to install an application, but want it to trigger when the computers come up from a reboot. Any idea if such a feature exists if not, some ideas. I suppose one way would be to use a Windows task schedule, but hopefully, I won't have to.

 

[Prajwal Desai]

I don't think such feature exists in Configmgr. You can deploy an application as required but not specifically define to install it after reboot. I am curious to know why do you want the app to install only after the reboot?.

 

[Garth]

With a package you can do log on and Log off BUT I have never found them reliable. Like Prajwal, What is the end goal here?

 

[abnranger67]

I don't think such feature exists in Configmgr. You can deploy an application as required but not specifically define to install it after reboot. I am curious to know why do you want the app to install only after the reboot?.

These are devices that perform sensitive processes and tasks, so getting them in an opportune window for deployment is hard. However, I know that they have to or will reboot at some point, so the idea is to catch them at that time so that the application will install when it comes back up before they put it back into production to do its normal processes. That is one feature I leveraged a lot with Ivanti's RES Automation. As mentioned, at the time of schedule I can pick from a list of options and one was at the next reboot.

 

[SchmilK]

I'm struggling with this as well. We are moving from Desktop Authority to MECM and when SentinelOne (antivirus) is upgraded, the user is notified there is no Antivirus installed - but then never says Antivirus is now installed so they worry.

In Desktop Authority we had the ability to run scripts at logoff/shutdown/reboot and during windows startup, allowing critical apps like this to install without the user knowing.

I have been trying to use the "Only install when no user is signed in" but find that very unreliable on computers that have an automatic reboot policy.

 

[Stanley Road]

how about using the RunOnce or RunOnceEx reg key? Just a thought

 

[ejmichaud]

Hi team, I looked but did not find if this was even possible. We were a RES One Automation (Ivanti) shop and just moved to SCCM. In RES, when you schedule a push/deployment, you are presented with a dropdown that offered options such as Immediately, After the next boot, After every boot, etc. Does SCCM have something like that when scheduling? I want to install an application, but want it to trigger when the computers come up from a reboot. Any idea if such a feature exists if not, some ideas. I suppose one way would be to use a Windows task schedule, but hopefully, I won't have to.

You can accomplish this easy enough with PowerShell. When Configuration Manager runs the deployment, have it run a pre-execution script which copies the contents of the application/package to a temporary folder, creates a scheduled task to run at next boot with an action to call the installer you copied into the temporary folder (and then deletes the temporary folder when the installation is complete). We have several installs that only run at boot. Note: you may want to bump up the default priority of the scheduled task for it to start quicker after the boot.

 

[Stanley Road]

I guess another question would be "how do you get users to reboot their pc's?"

 

[ejmichaud]

I guess another question would be "how do you get users to reboot their pc's?"

We use a custom "Reboot needed" script combined with Coretech Shutdown tool (old community tool/utility) that prompts the end user to restart their device. The script runs on every device every day and looks to see if there is a reboot needed by the device (one of the "reboot needed" triggers is a registry value we can set as needed). When a reboot is needed the Coretech Shutdown tool is called and the user is then prompted to restart their device. The amount of time is all customizable VIA the command line used to call the shutdown tool.

When we run an application that should only be installed following a restart, in addition to creating the scheduled task, we set the registry value that signals the device needs a restart. The "Reboot needed" script eventually runs on the device and them prompts the end user to restart.