Install Spread and Endur Services

Once the binaries exist on the Endur application servers, we can install and configure the application components.

Linqpad script

For speed, we provide a script to generate all of the relevant commands needed to install the services on the servers as defined in emdash.

Note: This scripts is provided for ease of use, but it is important that the user checks the output and does not execute it without gaining confidence themselves that it is correct. If the contents of the script is incorrect it could install services with incorrect parameters. Not the end of the world, but could cause delays with troubleshooting issues later.

To execute the script:

1. Log on to the emdash server e.g. ABCEMDASH01.
2. Launch Linqpad.exe from C:\Linqpad
3. Open the following file using the File -> Open menus
• \\lopwvemdash01\f$\Repository\Main\EnvMgmt\LinqPad Scripts\03 emdash data scripts\03 NewEnv_Install_Endur_Services.linq
4. Check where the script is going to output the command file it generates:
• var scriptPath = @"C:\EMSecure\emdash";
• Note: We write this file to the ‘EMSecure’ directory as the output file will contain usernames and passwords. ‘EMSecure’ is set up so that only members of the Environment Management Team AD Group are able to access the folder.
5. Run the script using the green triangle at the top left of the main Linqpad screen

When the script executes, you will be prompted 3 times for information:

1. The Environment Name (e.g. FT32). This will be entered as though it is a password (with *****). This is a workaround as this is the only function available for Linqpad to accept input from a user. Don’t worry about this – but type carefully! If this is incorrect the script will throw errors if it cannot find a matching environment name in the emdash database
2. The Appserver Password. This is the password that the Endur Users should enter. We configure this to be the same password across all runsites.
3. The Service Account Password. This is the password for the Service Account that will run the Endur services.

Once the script has executed you will see some output to the console and a statement that execution has finished. Now you can check the output file that was written to the folder specified above.

Script Output

The script will have the following commands for each of the services it is going to install:

1. Uninstall the service. This will run even if the service doesn’t already exist, and will throw an error. Don’t worry about that the first time you run it.
2. Install the service.
3. Change the service account that will run the service.

The script is a batch file that kicks off ‘psexec.exe’ commands to execute them on the remote computer. The script is set up so you can run it multiple times if needed.

Before running the script, do a sanity check of the values in the commands. Do the server names referenced look correct? Have the users been substituted correctly? Do they have the right passwords allocated to them? 

Double-clicking the file from file explorer will execute it. There is a ‘pause’ statement between each line which will expect the user to press any key to continue. This is so you can check the error code from each statement.

Once the script has run, log onto the servers and check the Services screen. You should now:

• Spread Olf_Spread_Daemon
• OpenLink_EndurX (as should be mapped to the server according to emdash)