Last updated on March 30th, 2023 at 06:04 pm
Some time ago there was a bug within SCCM where when you deployed an application, you had to change the deployment date back a day to make it work.
This seemed to have been fixed when moving over to current branch but this issue has raised it’s head again. This will cause clients trying to install the deployment to get a failed installation notification.
So, the fix is pretty simple, we need to change the deployment scheduling to the previous day and then it should work. Go to your application in the SCCM console and then onto the Deployments tab at the bottom:
Then right click on your deployment that is not working and click Properties:
This will then bring up the deployment properties box. You should now click on the Scheduling tab and change the date to the day before:
Click the OK button and then go ahead and retry the installation on the client side.
In some rare cases, we have seen that if there has already been a failed install, you may have to clear the clients SCCM cache.
If you want to be notified when we post more quality guides like this one, sign up to our free subscription service and you will receive an email when a new post is live.
No need to worry, we will not be filling your inbox with spam and you can unsubscribe anytime you like.