Pre-Install Checklist

Todd Chessum -

In addition to the standard SharePoint requirements, you will also need to ensure that the following steps are completed in order for the installation to begin. 

 General 

1) Firewall Access and Certificate Trust for Licensing URL

Please make sure the URL https://license.ateraprime.com is accessible from your SharePoint Web Front End and Application server(s). This needs to be allowed permanently as our products perform a license validation every 3 days. You will also need to setup a certificate trust for this domain. If you need instructions on how to do this, please click here.

To test if the URL is accessible please open the URL in your browser. If you see a white/blank screen then it is working. If you see "Page Not Found" then your firewall is likely blocking access. You will need to resolve this issue before proceeding. 

2) Permissions to Install and Deploy SharePoint Solutions

Make sure you have Farm administrator rights and also site collection administrators right to install and deploy SharePoint solutions.

3) Windows SharePoint Services Administration Service must be running

Follow these steps to ensure the SharePoint Administration service is running:

  1. Press Windows key + R. This will open the "RUN" command dialog.
  2. Type 'services.msc' and press "OK". This will open up services window.
  3. Look for SharePoint Administration Service; for SharePoint 2010 it will be SharePoint 2010 Administration and for SharePoint 2013 it will be SharePoint Administration.
  4. Right-click on the service and click on "Start".
  5. Repeat the above steps for every Web Front End/Application Servers in the Farm.

4) Windows SharePoint Services Timer Service must be started

Follow these steps to ensure the SharePoint Timer service is started:

  1. Press Window key + R. This will open the "RUN" command dialog.
  2. Type 'services.msc' and press "OK". This will open up services window.
  3. Look for SharePoint Timer Service; for SharePoint 2010 it will be SharePoint 2010 Timer and for SharePoint 2013 it will be SharePoint Timer Service.
  4. Right-click on the service and click on "Start".
  5. Repeat above steps for every Web Front End/Application Servers in the Farm. 

5) You must be a member of the Farm Administrators group

Follow these steps to check whether your user is in a Farm Administrator's group:

  1. Open Central Administration site with Run As Administrator.
  2. Under Security section, click on Manage the farm administrators group.
  3. If you are not a member of the farm administrators group, then click on New button.
  4. Add your username and then click "OK".

6) Microsoft SQL Server Mixed Mode authentication 

Emgage products require that you utilize Mixed Mode Authentication on SQL Server.

Follow these steps to ensure Mixed Mode Authentication is enabled:

  1. Open Microsoft SQL Management Studio on the server you are installing the Emgage products on.
  2. Right-click on the server name and select Properties.
  3. From the navigation panel on the left side, choose the Security tab.
  4. Under Server authentication, select 'SQL Server and Windows Authentication"
  5. Click 'Ok' to apply  

7) You must have a SQL Account that has "dbcreator" and "securityadmin" roles: 

You will be asked for this account and password during installation. Please follow these steps to create and ensure the account has sufficient privileges:

  1. Open Microsoft SQL Management Studio for the server you will use for Emgage products.
  2. Expand the server name and go to Logins. 
  3. Double click on the SQL Account. IMPORTANT: This must be a SQL Authentication User. Windows Account is currently not supported. If you need to create/configure a SQL Authentication User please go here.
  4. Select "Server Roles" and make sure that 'dbcreator' and "securtityadmin' are checked. 
  5. Click 'OK' until you are back on the initial screen of Microsoft SQL Management Studio. 

Alternatively, you may use the below SQL commands to create the required login:

CREATE LOGIN [USERNAME]WITH PASSWORD = '[PASSWORD]';
GO

EXEC master..sp_addsrvrolemember @loginame = N'adminuser', @rolename = N'sysadmin'
GO

Replace [USERNAME] and [PASSWORD] as per your requirements.

8) You must have a "SharePoint_Shell_Access" role membership on the SharePoint Admin Content and SharePoint Configuration Databases

Please follow these steps to assign SharePoint_Shell_Access role membership to your user:

  1. Open Microsoft SQL Management Studio for the server you will use for Emgage products.
  2. Expand the server name and go to Logins. 
  3. Double click on the SQL Account.
  4. Select "User Mapping" from the left pane.
  5. Check the checkbox for the SharePoint Admin Content database from the list.
  6. From the list displayed for the Database Membership, Select SharePoint_Shell_Access.
  7. Follow the step 5 and 6 for the SharePoint Config Database.
  8. Click 'OK'. 

9) Setup Web Service Access for Web Parts (Prime only)

This step is for the Prime product only. It allows for third-party services, such as weather, stocks, and other services so the web parts that use those services will function correctly. Please go here to complete the configuration. 

SharePoint 2010 Only

10) SharePoint 2010 with Service Pack 2 is required 

You need to have SharePoint 2010 Foundation, Standard or Enterprise with Service Pack 2 running in order to install any of the Emgage products.

To check what version of SharePoint you are running you may run a simple PowerShell command in SharePoint Management Shell: "(Get-SPFarm).BuildVersion"

This will produce four numbers: Major, Minor, Build and Revision. (typically stated as Major.Minor.Build.Revision)

SharePoint 2010 Service Pack 2 has Build Version of 14.0.7015.1000

If your Build number is lower than 7015 then you will need to download and install a more current release. This SharePoint 2010 builds list is a great reference for determining which build you currently have installed and to which build you'd like to update.

SharePoint 2013 Only

10) SharePoint 2013 with March 2013 Public Update or higher is required

You need to have SharePoint 2013 Foundation, Standard or Enterprise with the March 2013 Public Update running in order to install any of the Emgage products.

To check what version of SharePoint you are running you may run a simple PowerShell command in SharePoint Management Shell: "(Get-SPFarm).BuildVersion"

This will produce four numbers: Major, Minor, Build and Revision. (typically stated as Major.Minor.Build.Revision)

The March 2013 Public Update has Build Version of 15.0.4481.1005

If your Build number is lower than 4481 then you will need to download and install a more current release. This SharePoint 2013 builds list is a great reference for determining which build you currently have installed and to which build you'd like to update.

SharePoint 2016 Only

10) SharePoint 2016 with June 2016 Patch or higher is required

You need to have SharePoint 2016 Standard or Enterprise with the June 2016 Patch running in order to install any of the Emgage products.

To check what version of SharePoint you are running:

  1. Launch SharePoint 2016 Central Administration
  2. Select "Mange servers in this farm" from under the "System Settings" heading
  3. Take note of the "Configuration database version." It needs to be 16.0.4393.XXXX or greater

or

  1. Open SharePoint 2016 Management Shell
  2. run the command: Get-SPFarm | Select BuildVersion
  3. Take note of the "BuildVersion." It needs to be 16.0.4393.XXXX or greater

If your Build number is lower than 16.0.4393.XXXX then you will need download and install a more current release. This SharePoint 2016 builds list is a great reference for determining which build you currently have installed and to which build you'd like to update.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk