You are just done away with a software deployment in production environment. Soon you flooded with complain that something went wrong with the deployment and it need to be stopped immediately.
What should be your next step? What are the best practices to deal with miss deployment?
The most common answer i have heard is : Delete the deployment.
Well, that’s sound good to stop the deployment on new machine. You just deleted the deployment and relaxed.
However, trouble is not over here. You got a call from higher management and they asked you to provide the list of all users / machines impacted by deployment. Once identified, you have to work on remediation plan.
Now you have another challenge.
How you can pull out these details? When you deleted the deployment, its remove all such details from SCCM along with deployment.
So, what are the best option to deal with wrong deployment? There are many such option available which you can use to stop the deployment. This will also ensure you have historical data available if required for reporting / remediation purpose.
- Expire the deployment by setting Deployment End Date to past.
- Remove the content from the distribution point(s). This way client would not be able to deploy when it already received the policy.
- Switch deployment target to a blank Collection.
- If its CM2012 Application then you can just right click on an application and select “Retire”.
- Configure Management Point for HTTPS | ConfigMgr | SCCM
- Configure Software Update Point for SSL | ConfigMgr | SCCM
- Deploy client authentication certificate for SCCM clients
- SCCM CMG Part 1 | Cloud Management Gateway (CMG) Setup Guide
- SCCM CMG Part 2 | Issue, Enroll & Export Server Authentication Certificate
- SCCM CMG Part 3 | Configure SCCM Site for SSL
- SCCM CMG Part 4 | Integrate Azure Active Directory with ConfigMgr
- SCCM CMG Part 5 | Setup Cloud Management Gateway
- SCCM CMG Part 6 | Validate CMG Health & Client Communication
- Location of smsts.log file during Operating System Deployment (OSD)
- Schedule SCCM Client Reboot through ConfigMgr
- Check Software Center Business Hours of Remote Computer
- SCCM Software deployment strategy
- How to deal with wrong deployment in ConfigMgr
- How to Initiate SCCM client agent actions using PowerShell
Subscribe to Techuisitive Newsletter
Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.