The ConnectionStrings.config file on your ALM/LPM server can be used to change the database or database credentials your ALM Server is pointed to, or simply to check and see what database your ALM is pointed at. If you need to change credentials on the database you will need to change them in this file. In order to view the file you must first decrypt the file. Detailed, manual instructions can be found here. The utility attached to this document will decrypt and allow you to view/edit this file, as well as re-encypting it and restarting the services required.
1) Run the file as admin and follow the instructions. If it does not open your ConnectionStrings.config file for you, you probably have installed Service Management somewhere not expected. The file can be opened manually with notepad once the utility has decrypted it. It's path should be something like;
...\LANDesk\Service Management\Web\bin\ConnectionStrings.config
2) Ensure that IIS and the LANDesk Service Management service were restarted.
***This utility is offered as is, and may not work as designed in your environment. It has been tested in multiple environments and has worked appropriately. The use or change of this utility is not supported. This is not a LANDesk tool. It was designed to make the changing of the credentials or DB easier. If you have any problems with this utility, use the manual steps to accomplish the same task found here. or contact me to let me know what is happening, and I would be more than happy to see if I can make any adjustments that might make it work, or at the very least, help you understand what the utility does so that you can adjust it for your environment.***
NOTE: An updated version of this utility for ALM/LPM 6 is now attached to this document. This version is for a NEW installation of ALM/LPM 6 and not upgraded existing installation. New installations of ALM/LPM 6 install in the "Program Files" folder instead of the "Program Files (x86)" folder as previous versions however and upgraded installation of ALM/LPM 6 will remain in "Program Files (x86)" and shouldn't experience any issues with the original utility.