This article provides step-by-step instruction on how to remove all versions of Prime. It is intended for all Prime release versions prior to the July 2015 release. In mid 2015 we introduced an Installer for Prime, which incorporates a Remove option that automates most of these steps.
To uninstall Prime, you will basically be follow the installation manual backwards (available for download at the end of this article). Below are the steps required to completely uninstall Prime from your farm.
Prime Uninstall Steps
- Navigate to Site Settings > Master page and switch both the Site Master Page and System Master Page from ap-PRIME-2010.master to v4.master (SharePoint 2010) or from ap-Prime2013 to seattle (SharePoint 2013).
- Navigate to Site Settings > Site collection features and deactivate all features with the "Emgage" prefix in their name (ex: "Emgage | Asset Manager").
Note: Only the above step are required to deactivate Prime on a Site Collection. If that's all you desired, please stop here.
- Open Central Administration (run and Administrator), navigate to System Settings > Manage farm solutions and Retract / Remove all solutions with an "atera", "ateraprime", or "emgage" prefix (ex: "ateraprime.assetmanager.wsp").
- Certain items such as master pages and page layouts are automatically ghosted by SharePoint. To completely remove these files, first make certain they are not in use on any page or site on your farm. Then navigate to Site Settings > Master pages and page layouts and delete all files with an "ap-" prefix (ex: "ap-PRIME-2010.master").
Note: If you're planning on reinstalling Prime, and just desire a clean install of its various features, then we would recommend stopping here. The following steps will result in data loss.
- Depending on which Prime solutions were activated, there may be Lists, Libraries and list templates which can now be removed. Navigate to System Settings > List templates and delete any undesired template files with an "Emgage" prefix (ex: "EmgagePrimeStylizerThemes"). Next navigate to Site Contents and feel free to delete any undesired lists or libraries with an "Atera Prime |" or "Emgage |" prefix (ex: "Atera Prime | Feedback List").
- You can then remove the AteraSettings connection string from the web.config of all WFE's on which Prime was installed, and delete both the Atera Settings database (named PrimeSettings_SP by default) and associated user (named primeSettinsUser by default) from SQL. If you are unsure how to perform these actions, please contact you Database Administrator.
- Once finished, restart IIS by launching Windows PowerShell and entering the command iisreset.