Remove Features and Uninstall
After you have successfully completed installation of Windows Server AppFabric, you can remove AppFabric features or uninstall AppFabric as a whole by opening the AppFabric Setup Wizard. Executing the setup program after AppFabric has already been installed will display the Add or Remove Features page.
The uninstallation procedure removes a feature and removes its configuration from the root-level Web.config file. It will not remove configuration settings at the site, application, subdirectory, or service level. It will also not remove any databases that were created during the configuration process.
To remove features or uninstall
On a computer with AppFabric installed, click Start, click All Programs, click Windows Server AppFabric, and then click Add or remove Features.
Note
To uninstall the Caching Service, you must first stop the service, removing it from the cache cluster. See “Uninstalling the Caching Service Feature” below.
On the Add or Remove Features page of the AppFabric Setup Wizard, select Remove Features or Uninstall, and then click Next.
On the Customer Experience Improvement Program page, select Yes to join the Customer Experience Improvement program, or No not to participate, and then click Next.
Note
If you participate, this program helps Microsoft improve Windows Server AppFabric. Without interrupting you, it collects information about your computer hardware and how you use Windows Server AppFabric. The program also periodically downloads a file to collect information about problems you might have with Windows Server AppFabric. The information collected is not used to identify or contact you.
On the Feature Selection page, deselect any feature that you would like to remove, and then click Next. To uninstall all of AppFabric, deselect all features. Click Next.
Note
Only those features that were previously installed, and are deselected in this list, will be removed.
On the Confirm Removal Selections page, verify that the features that you want to remove are listed, and then click Remove.
On the Removal Progress page, verify that the removal process is proceeding successfully.
On the Removal Results page, click Finish.
Uninstalling the Caching Service Feature
To uninstall the Caching Service from a cache server, you must stop the service, removing it from a cache cluster. Depending on how the cache cluster was deployed and the number of cache hosts in the cluster, a running cache cluster may not be able to accommodate losing a cache host if it is a lead host that performs the cluster management role. For more information, see the “Lead Hosts and Cluster Management” topic in Windows Server AppFabric help (https://go.microsoft.com/fwlink/?LinkId=164929).
Click Start, point to Administrative Tools, and then click Windows PowerShell Modules.
Before the Caching Service can be uninstalled, use the Windows PowerShell-based Cache Administration tool to stop the service with the
Stop-CacheHostcommand. For example, if you want to uninstall the Caching Service on a computer named CacheServer1, and it was installed with the default values for the TCP/IP port numbers, you would use the following command to stop the server's Caching Service:Stop-CacheHost -HostName CacheServer1 -CachePort 22233. For more information about the Cache Administration commands available, see the “AppFabric Cache Administration with Windows PowerShell” topic in Windows Server AppFabric help (https://go.microsoft.com/fwlink/?LinkId=164929).If the
Stop-CacheHostcommand was not successful and returns the errorERRCAdmin013, "Cluster Quorum would be disturbed…", stop the cache cluster by using the commandStop-CacheCluster. This error is returned because there must always be a majority of cache hosts designated as lead hosts available for the cache cluster to remain running. This error also suggests that (after you uninstall this cache host) you will need to designate another cache host as a lead host before you can start the cache cluster. For more information about how to do that, see Set the Cluster Management Role and Lead Host Designations (Windows Server AppFabric Caching).Perform the Caching Service uninstallation by using the AppFabric Setup Wizard, using the Windows operating system program removal console, or using command-line parameters to perform an unattended uninstallation, as described below.
Uninstalling by using the AppFabric Setup Wizard: Click Start, click All Programs, click Windows Server AppFabric, and then click Add or remove Features. (See “To remove features or uninstall” section above.)
Windows uninstallation: Use the operating system's Add or Remove Programs or Programs and Feature console to remove the Caching Service feature of AppFabric.
Automated uninstallation: To perform an automated uninstallation, open the CMD.exe command-line tool and navigate to the folder that contains the installation program. Then, execute the installation program using the automated uninstallation parameters. For more information, see Automated Installation.
(optional) After any of the caching features of AppFabric have been uninstalled, review your firewall configuration.
Clustering Service Uninstallation Issues
After you uninstall the caching features from a distributed cache server, the AppFabric setup program will disable the “Windows Server AppFabric: AppFabric Caching Service” firewall rule group, removing it as an exception. Upon installation, the setup program creates this group and adds rules to it. However, the setup program will not disable the “Remote Service Management” firewall rule group. If you enable it during installation, the “Remote Service Management” group will not be disabled after uninstallation. You will have to disable it manually on each node of the cluster, if you choose to do so. After any of the caching features of AppFabric have been uninstalled, review your firewall configuration.
If you uninstall a node of a multiple-node cluster, and do not run the AppFabric configuration cmdlets to unconfigure the node, the cluster will still be configured for the node. To unconfigure it, run the Remove-CacheHost cmdlet on that node.