SCCM App Deployment - Scheduled to deploy after <date>

[CHiLL]

I have created an application to deploy out to the whole site via SCCM, and would like it to be deployed as soon as possible and have a deadline as to when all machines should have it. However, I have created the application deployment with what I thought was the correct settings, however the clients are showing 'scheduled to install after 1/22/2018'. In the scheduling tab of the deployment, I have configured the following:

 

Time based on: UTC

Schedule the application to available at: 22/12/2017 13:01 (I originally used the make available from now option, which sets the available from time to the time when the deployment was created)

Installation deadline: Scheduled at 22/01/2018 21:00

 

I have deployed this application to a collection called 'Application Deployment | All Windows 10 | 64-bit'. (Which as it sounds, contains all Windows 10 64-bit clients)

I have a maintenance Window enabled for 'All Deployments' on another collection called 'Software Updates - Windows 10' (Which as it sounds, is for Windows Updates and contains all Windows 10 clients)

 

Do maintenance windows cover application deployments? If so, I am assuming that the maintenance Window will still take effect and prevent the application installation outside of the window, even if it application deployment and maintenance windows are configured on different collections? As the machine is a member of both groups.

[Steve21]

If they both fall under it yes it takes precedence, but there's an option to ignore the maintenance windows if you want it out sooner.

 

Under user experience if you select the software install as ticked, but leave system restart unticked it'll install it outside the windows but won't restart etc

 

Normally we'd set the deadline earlier, and then use that option if we want it out sooner. As that'll only trigger once the deadline hits (but then it still uses the maintenance window after the deadline hits if that makes sense?)

 

Steve

[CHiLL]

If they both fall under it yes it takes precedence, but there's an option to ignore the maintenance windows if you want it out sooner.

 

Under user experience if you select the software install as ticked, but leave system restart unticked it'll install it outside the windows but won't restart etc

 

Normally we'd set the deadline earlier, and then use that option if we want it out sooner. As that'll only trigger once the deadline hits (but then it still uses the maintenance window after the deadline hits if that makes sense?)

 

Steve

I've tried doing that before, however I've had issues with pending reboots in the past, specifically with the /norestart switch. So with the 'Software Installation' checked, but 'System Restart' unchecked for a deployment with /norestart...the software would install and the user would receive a notification that a restart was pending. Then the user would be asked to either restart now or postpone for up to four hours. If postponed, the user would then receive a message saying 'this computer will restart in 90 minutes'. This restart cannot be prevented and it will restart (which is extremely annoying). I don't know if changing the user notifications to 'Hide in Software Centre and all notifications' would prevent this, but I'm assuming not.

[Steve21]

Do you have Windows Updates via WSUS configured as well as SCCM Updates then?

 

Steve

[CHiLL]

Do you have Windows Updates via WSUS configured as well as SCCM Updates then?

 

Steve

No, only via SCCM. Though this is happening with both Application Deployments and Software Updates.

[Steve21]

Strange, shouldn't be doing it for software :s

 

I'm assuming your maintenance windows are set the right way around? That they're set for out of hours, not in hours?

 

And you definitely are picking the suppress restart options on the deployment options?

 

Steve

[CHiLL]

Strange, shouldn't be doing it for software :s

 

I'm assuming your maintenance windows are set the right way around? That they're set for out of hours, not in hours?

 

And you definitely are picking the suppress restart options on the deployment options?

 

Steve

Well I certainly don't plan on working between 9pm and 6am!

 

I can confirm that the application deployment is set as 'Required', rather than 'Available'. 'Software Installation' is checked and 'System restart' is unchecked. I have definately also used /norestart in the deployment.