1. Click the Database Server tab on the main form
   
2. Enter the following information at the top of the form:
   
1. Server Address: the name or IP address of the DB server. If the DB server is not the same as the App server, make sure you can PING the server from the command line. Refer to Tips/Troubleshooting for examples.
   
2. Username: the username for a valid system admin user. This user needs access to create databases and users on the server
   
3. Password: The PW for the above username
   
3. Check all options that need to apply in the middle section. If this is a new server, check all settings.
   
4. If migrating from Cloud to Enterprise, add the cloud export file under the Import Files section, and check the necessary DBs to run the file on.
   
5. Click Submit when ready. If any issues are encountered, refer to the Troubleshooting/Tips section below
   

To ensure you can connect to the DB server form the App server, the first thing you need to check is that you can ping the DB server form the App server, either by name or IP address.

1. Open a command prompt (Start -> cmd)
   
2. Type the following, replacing “{server name here}” with the appropriate value:
   
1. ping {server name here}
   
2. Example: ping 10.0.0.5
   

Sometimes, the username and password entered above is not a sysadmin account, so it fails when trying to create a DB. The best way to test this is to try it manually through SQL Server Management Studio (SSMS).

1. Open SSMS on the DB server if you have access, or App Server if you don’t. If you have to run it on the App Server, you likely will need to install it first.
   
2. On the Connect to Server window, enter the server name/address and the login credentials given to you.
   
1. If the login works, the window will close and open a navigation tree on the left.
   
3. Right-click the Databases folder and try adding a “test” database
   
1. If this process fails, you do not have sufficient permissions, and will need to contact IT.
   
4. Right-click the Security folder and try adding a “test” Login
   
1. If this process fails, you do not have sufficient permissions, and will need to contact IT.
   

1. Click the App Server tab on the main form
   
2. Check the necessary options on the top half of the form. If this is a new server, check all options
   
1. Prerequisites
   
1. Disable ESC – Disabled Enhanced Security Configuration in IE for admins. This prevents a lot of issues when trying to download files.
   
2. Add Firewall Rules – Opens the necessary ports to allow remote access
   
2. Windows Features
   
1. IIS – Enables the Web Server component
   
2. .NET 4 – Enables .NET 4.5 on the server
   
3. .NET 3.5 – Enables .NET 2-3.5 on the server
   
4. ASP.Net – Enables .NET web applications
   
5. WCF – Additional Web Server items
   
3. Download/Install
   
1. TeamViewer – do not check if we use the customer’s remote access
   
2. Google Chrome – recommended browser
   
3. Openfire – The chat server component that links the Merchant app to the Website
   
4. Notepad++ - Text editor that is useful for modifying code files or debugging logs
   
5. FileZilla Client – Used to pull down updates from the ARE staging FTP site. Do not install if the server is hosted by us.
   
6. Crystal Reports – Reporting engine
   
4. Folders
   
1. Files – Update settings if needed
   
2. Websites
   
1. Creation Mode – controls how the sites are to be configured
   
1. Default – Adds the site(s) under the Default Website option in IIS
   
2. Virtual Directory – Adds the site(s) under a Virtual Directory named SHIPSTORE on the Default Website
   
3. Independent – Adds each site as its own Website in IIS
   
3. Click Submit when ready. If any issues are encountered, refer to the Troubleshooting/Tips section below
   

Sometimes we will want to configure a full URL for the website (i.e. http://shipstore.customer.com). The Setup App does not cover this currently, so you will need to perform these steps in IIS:

1. Click the necessary site in IIS
   
2. Click Bindings on the right-hand pane
   
3. Click the http binding, and click Edit
   
4. Set the Host Name to the full domain name, excluding the “http://”
   
5. Press OK
   
6. If HTTPS is desired:
   
1. Click the Add button on the Bindings window and follow step 4 using https as the Type
   
2. Select the SSL certificate from the drop down. If one is not on the server, you will need to work with the customer to get a certificate on the server. Follow the instructions here  ignoring step 1.9.
   
7. Click OK
   

Not all Windows features enabled

Sometimes enabling features on the server may require a restart to allow you to add other features. Simply restart the server, and re-run the Windows Features installs again.

Installer does not download/install

This can happen from time to time if the installer gets updated by the vendor. Inform SS Support of this so we can look into the update.

Now that the site and database has been set up, you need to configure your admin account and the roles within the system

1. Go to the following URL to register our system admin user:
   
1. {site URL}/account/register?key=33C58548-C9BE-40E3-9B39-FE010FD3F52F&e=support@shipstoresoftware.com&p=1
   
2. You will likely receive an error in this step indicating that the roles could not be added to this user. Go to the following URL to create the user roles:
   
1. {site URL}/Account/Manage
   
3. Once there, go to the Roles tab and create the following roles:
   
1. System_Admin
   
2. Client_Admin
   
3. Shipper
   
4. Order_Entry
   
5. Reporting
   
4. After the roles are created, go back to the Users tab and assign the areadmin user the System_Admin role by clicking the checkbox, and click Save.
   
5. Log out, then back in to load the changes. The site should load without error this time.