Update services.conf file for EAPowerTools after Qlik Sense Service Dispatcher update

##Introduction

When a customer updates Qlik Sense, the services.conf file used by the Qlik Sense Service Dispatcher is overwritten, This overwrite breaks EA PowerTools running through the service dispatcher. To overcome this hurdle, we have developed a PowerShell script you can run to update the services.conf after performing an upgrade. The script will add the powertool configuration information to the services.conf file and restart the service dispatcher. Follow the instructions below to run the script.

---

##Prerequisites

• Running unsigned PowerShell scripts from remote computers requires changing the execution policy for PowerShell. To determine the current execution policy setting, launch a PowerShell window and at the prompt enter get-executionpolicy -list to identify the current execution policy setting.

---

##Instructions

1. Launch a Windows PowerShell window run as an administrator.

2. Navigate to the location of the EAPowerTools directory on the server where the PowerTools and Qlik Sense Service Dispatcher are installed.
   

3. Update the PowerShell execution policy on the system to allow the script to run. In the PowerShell window, enter set-executionpolicy unrestricted. The system will prompt to confirm the change. Enter the letter Y or press the enter key to change the execution policy setting.
   
   PowerShell's execution policy settings dictate what PowerShell scripts can be run on a Windows system. To run the ServicesConfBuilder script, the execution policy needs to be changed.

4. Run the PowerShell script ServicesConfBuilder.ps1 located in the EAPowerTools folder. PowerShell requires specifying a path with the script in order to run. If the PowerShell window is in the current directory of the script _._ can be used for specifying the current path. Assuming the PowerShell window is in the directory where ServicesConfBuilder.ps1, enter .\ServicesConfBuilder.ps1 to run the script.
   

5. Press any key to begin the update.
   

6. Set the execution policy back to the value it was before running the script using the set-executionpolicy commandlet.
   

7. And you're done!