SSCM – How to deal with wrong Deployment

-


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 is the best practice 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 removed all such details from SCCM along with deployment.

So, what is the best practice? 

 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”.



Comments

  1. Abhishek PandeyApril 15, 2018 at 1:34 AM

    Well that's crisp and very informative, looks good to learn and keep in mind.

    ReplyDelete
  2. SabirDecember 19, 2018 at 4:42 PM

    Great Article. Should always be considered as the "Backup Plan" if you are dealing with mass deployment via Change Management process.

    ReplyDelete

Post a Comment

Popular posts from this blog

SCCM Software Distribution Troubleshooting

-
Image
1.    Content Monitoring and Validation from Console The below article provide details of content monitoring and validation from console. https://blogs.technet.microsoft.com/inside_osd/2011/04/06/configuration-manager-2012-content-monitoring-and-validation/ 2.    Reports SCCM reports should be the first thing to check the software deployment status. By looking into the report you can determine the scope of failure such as large scale failure, location based failure or client specific issues. A large scale failure may be caused by an issue with package or programe while issue can be related with specific client if deployment failure rate is low and limited to few clients. There are multiple reports available for each category.  All Software Distribution reports can be found in below folders under Monitoring > Reporting > reports. ·          Software Distribution – Collections ·          Software Distribution – Content ·          Software Di
Read more

Powershell - List AD Organizational Unit and GPOs linked to them

-
The below script will search Active Directory for all Organizational Unit which contain specific name and list them along with all Group Policies linked to those OUs. Example: The below command will get a list of all OUs which name contains 'Test'. It will also show the details of all GPOs linked to OUs. Usage Example: .\Get-OUList.ps1 –OUName “Test” #Script [ CmdletBinding () ] Param (   [ Parameter (Mandatory = $True ) ]   [ string ] $OUName   ) $invocation = ( Get-Variable MyInvocation ) . Value $directorypath = Split-Path $invocation . MyCommand . Path $outputfile = $directorypath + "\Result.csv" $OUName = "*" + $OUName + "*" $Results = @() $OUList = Get-ADOrganizationalUnit -Filter * | Where-Object -FilterScript { $PSItem . distinguishedname -like $OUName } foreach ( $OU in $OUList ){     $LinkedGPOs = Get-ADOrganizationalUnit -Identity $OU | select -Expa
Read more

Troubleshooting System Center Endpoint Protection (SCEP) Client

-
Image
Microsoft System Center Endpoint Protection provides an antimalware and security solution for the Microsoft platform. This can be integrated with System Center Configuration Manager. I have consolidated the information which are useful for SCEP client side troubleshooting. 1. Managing Endpoint Protection client with Command Line Interface – MpCmdRun.exe The MpCmdRun.exe (Microsoft Antimalware service command line utility) is very useful tool to manage local Endpoint protection client with command line.  The MpCmdRun.exe is located in C:\Program Files\Microsoft Security Client folder. On Windows 10 machines, the MpCmdRun.exe is available in C:\Program Files\Windows Defender folder. When executed, this command automatically creates a log file named as MpCmdRun.log in C:\Users\ username\AppData\Local\Temp folder. This log file records the commands that are executed using MpCmdRun.exe. Few of most commonly used command lines are listed below. For a complete l list of availa
Read more