Was it something we said? We are sad to see you go and we hope you'll come back, but for now let us help you uninstall our products.
Before we get started, there are a few things you should do to make sure the uninstall process does not cause any disruptions to your environment.
Putting Things Back
You need to remove all references to Emgage assets before you uninstall, otherwise your SharePoint environment might experience some issues.
- Remove References to Master Pages
Navigate to Site Settings > Master page and switch both the Site Master Page and System Master Page to seattle (SharePoint 2013/2016), or v4.master (SharePoint 2010). Select the "Reset all subsites to inherit this site master page setting" checkbox and click OK.
Note: You will have to do this for every Site Collection (i.e. Team Sites, Publishing Sites, My Sites...) where Prime was deployed and activated.
- Remove Reference to Page Layouts
Go to all of your Publishing Sites and check to see which pages utilize Emgage Page Layouts (HINT: All Emgage Page Layouts begin with "Prime", "ap-", "Atera Prime", or "Emgage").
An effective way to do this is to go to the Pages Library and check the Page Layout column to see which layouts are being utilized, then change the ones that begin with "Prime", "ap-", "Atera Prime" or "Emgage" to use one of the default SharePoint page layouts.
- Remove Emgage Web Parts from all pages
This might be a bit tedious, especially if you've added a lot of web parts to pages. But like with most things in life there is a short cut to find Emgage Web Parts :).
Once you find these web parts you need to Delete them from each page. (IMPORTANT: 'Closing' a web part is not the same as 'Deleting' a web part from a page. 'Closing' will simply hide the web part but will still keep all references on the page. So please make sure you 'Delete' them.)
- Running the (Un)Installer
|IMPORTANT: Performing the steps in this section will cause your SharePoint IIS Application Pools to restart, and thus cause downtime on your environment.|
The installer that was used to install the Emgage products must be run again to uninstall the products. We know this sounds backwards, however there is a remove feature in the installer!
- Locate the Setup.exe file located in the extracted Product Installer package provided by Emgage support.
- Run the Setup.exe file as Administrator (right click on Setup.exe file and click the Run as Administrator option).
- The installer will launch. Proceed through the "Welcome" and "Prerequisites Check" screens until you reach the "Install Options" screen. Now select the Remove option and run the (un)installer.
- Removing Connection Strings for Web.Config Files
|IMPORTANT: Performing the steps below will cause your SharePoint IIS Application Pools to restart, and thus cause downtime on your environment.|
Open every web.config file for each of your SharePoint server Web Apps and perform the following steps:
- Search for 'AteraSettings' and remove the connection string. Note the database name as you will need this in the next section.
- Search for 'PrimeSettings' and remove the connection string. Note the database name as you will need this in the next section.
- Search for 'TurboBuilder' and remove the connection string. Note the database name as you will need this in the next section.
- Removing Emgage Databases and Corresponding Accounts
When you installed your Emgage Products you also deployed multiple databases to your SQL Environment. These databases also need to be removed. By default, these databases have the following names, if you opted to use different names, they'll be the ones you made not of in the previous section.
Moreover, you may also like to remove the following SQL Authentication accounts, or similar accounts you created exclusively for Emgage product use.
|WARNING: Please make sure that these accounts are not used for any other purpose prior to deleting them. Doing so could negatively impact other applications or services that might be using these accounts.|
Removing Emgage Assets
Sometimes there will be certain Emgage assets that are left behind after the Retract process, and you would need to manually remove them. These assets might include:
Navigate to Site Contents and delete any lists or libraries with an "Atera Prime" or "Emgage" prefix (ex: "Atera Prime | Feedback List").
- List Templates
To remove navigate to System Settings > List templates and delete any undesired template files with an "Atera Prime" or "Emgage" prefix (ex: "EmgagePrimeStylizerThemes").
- Master Pages and Page Layouts
Certain items such as master pages and page layouts are automatically ghosted by SharePoint. To completely remove these file navigate to Site Settings > Master pages and page layouts and delete all files with an "ap-", "Emgage", "Atera Prime" or "Prime" prefix (ex: "ap-PRIME-2010.master")
- Style Library Emgage Folder
Navigate to Site Contents > Style Library and delete the Emgage folder.
Navigate to Site Setting > People and groups, select the More... link at the bottom of the Groups section in the side navigation, and delete the following groups:
WARNING: Please make sure that these accounts are not used for any other purpose prior to deleting them. Doing so could negatively impact other applications or services that might be using these accounts.
- Prime Alerts Administrators
- Prime Global Navigation Administrators
- Prime Navigation Administrators
- Prime News Manager
- Prime Stylizer Administrators
- TURBO App Creator
- TURBO Builder Admin
- Empty Your Recycle Bin
Please empty the contents of your Recycling Bin. If the Theme library template is still in the recycle bin, then the library will deploy with the wrong name and Prime will not work (just in case you choose to reinstall one day).
IMPORTANT: Emptying your recycling bin will remove all other contents in there that you might need to recover. Be selective.