Uninstalling configuration manager

Advice — From my experience, I see ConfigMgr admins are little impatient when they see management point related issues.

The first step they usually take is uninstall management point rather than actually troubleshooting the issue. Repairing management point has to be done after you have tried all the possible ways to fix that issue.

A management point is a site system role in Configuration Manager. The management point provides policy and service location information for clients and it also receives configuration data from clients. When you package and deploy an application to the client, the client sends a content request to a management point. The management point then sends a list of the preferred distribution points to the client.

The client uses one of the preferred distribution points as source location for content. If contents are not available on the preferred distribution point, the management point sends a list to the client with distribution points that have the content available.

You now can install more than one management point in the same site. The client automatically selects the best MP based on its capability and proximity. Because a site can have multiple management points , this increases the number of clients each site can support.

Having more than one MP also adds a layer of resiliency by providing a redundant site role. They will surely help you while troubleshooting the issues. Listing some of the important management point log files. This option is the default. Different from install content : The uninstall content is different from the install content. Uninstall content location : If you select the third option for content settings, specify the network path to the content that's used to uninstall the application.

Uninstall program : Specify the command line and any required parameters to uninstall the application. Uninstall start in : Optionally specify the folder that has the uninstall program for the deployment type.

This folder can be an absolute path on the client. It can also be a relative path on a distribution point of the folder with the package. Run installation and uninstall program as bit process on bit clients : Use the bit file and registry locations on Windows-based computers to run the uninstall program for the deployment type. Then deploy the application. On the Deployment Settings page of the wizard, select the deployment action to Uninstall. When you select a deployment action of Uninstall , the deployment purpose is automatically configured as Required.

Many customers have lots of collections because for every application they need at least two collections: one for install and another for uninstall. This practice adds overhead of managing more collections, and can reduce site performance for collection evaluation.

Starting in version , you can enable an application deployment to support implicit uninstall. If a resource is in a collection, the application installs. Then when you remove the resource from the collection, the application uninstalls. Starting in version , this behavior also supports application groups. When this article refers to an application , it also applies to app groups. In version and later, this behavior applies to deployments to device or user collections.

Both these options are self-explanatory. I would not check any of these options as I want to uninstall primary site completely. So on the confirmation box click Yes. Now the wizard begins to uninstall primary site. There are many steps involved while uninstalling SCCM primary site. In my lab setup the primary site got uninstalled in 14 minutes. The ConfigMgrSetup. Peeking into System Management container, there are no entries related to primary site server.

This means your primary site has been uninstalled cleanly. Hi I am getting error to uninstall CAS after failed installation attempt. Their is no primary site this is first cas server. Please help. I have removed and restarted.

I copied ccmsetup. Is there another way to cleanly remove it? Reconfigure boundaries before removing the site. Have you configured other content management options like peer caching?

You can't move or reassign a secondary site to another primary site. When you remove a secondary site from its direct parent site, choose whether to uninstall or delete it. Use this option to remove a functional secondary site that's accessible from the network. This option uninstalls Configuration Manager from the secondary site server. It then deletes all information about the site and its resources from the Configuration Manager site. This option deletes all information about the site and its resources from the Configuration Manager hierarchy, but doesn't make any changes on the site server.

For more information, see Hierarchy Maintenance Tool Preinst. The administrative user that runs Configuration Manager setup needs the following security rights:. If the primary site database server is remote from the primary site server, local Administrator rights on the remote site database server for the primary site.

Infrastructure Administrator or Full Administrator security role on the parent primary site. In the Configuration Manager console, go to the Administration workspace, expand Site Configuration , and then select the Sites node. Select the secondary site server that you want to remove.

In the ribbon, on the Home tab, in the Site group, select Delete. Before you uninstall a child primary site that uses distributed views for its replication link to the CAS, first turn off distributed views in your hierarchy. For more information, see Uninstall a primary site that is configured with distributed views.

Review boundaries, boundary groups, and fallback relationships. If you assign clients to a new site, but don't change the boundaries, they may be considered roaming. For more information, see Define site boundaries and boundary groups. Make sure all active clients are reassigned to another primary site in the hierarchy. Otherwise clients will be unmanaged after you uninstall the site. For more information, see How to assign clients to a site.

Make sure that you've properly sized the other site systems with this role in the other site. They will need to support your business requirements for performance and availability with the additional clients. If this site has lots of clients, reassign them in stages.