Step 1 - Download your DSM Management Suite version
Step 2 - Install the PowerShell Extensions
Step 3 - Install the DSM Management Suite backend
So that we can connect all of our components to the DSM Management Suite, we first need the backend (Web API) and a server. The DSM Management Suite backend is identical for all editions. It's up to you if you self-host or a backend or if you want me to host it for you. The backend can run on both w Windows and a Linux server, you can install the application directory on your BLS if you want. If you decide to have your own server, I highly recommend using Docker. I the past there was a prebuilt virtual appliance. I will not support virtual appliances anymore because it is not worth the effort.
- How to install the Backend on Ubuntu Server 18.04
- How to install the Backend on a Windows Server 2016
Step 4 - Connect Settings Manager
The settings manager manages the connection information between your DSM environment and the DSM Management Suite. This information is stored in encrypted form. Both the Client Sync Script, the Visio Addon, and the Windows Dashboard use this information to connect to the backend. The Settings Manager is an installed directory with the Windows Dashboard and you should already have received a desktop icon. If you don't have a desktop, you can find the Settings Manager under:
C:\Program Files (x86)\DSM Management Suite\DSM Patch Reporting Settings.exe
- Important: Start the application with administrator rights.
4.1 BLS connection
Enter your BLS server under "BLS address and port". For example:
For user name and password, enter a user who has access rights to the organization of your DSM environment. This user must be able to see all computer objects and their security vulnerabilities. Under Context, enter an OU that the client sync script should monitor. This gives you the option of synchronizing several locations individually. Leave the context at the default value if you want the synchronize your entire DSM environment. Look for the wildcard sign behind the context path!
emdb:\rootDSE\Managed Users & Computers\*
If all login information is correct and the PowerShell Extensions are working properly, you can now click on "Test Settings Connection". The connection to the API still fails, but the connection to the BLS should not cause an error.
4.2 Connection to the DSM Management Suite API
For API Url, enter the name of your DSM Management Suite backend server including port and protocol, followed by /api
Step 5 - Set up Client Sync Script
It is recommended to install the Client Sync Script on the same server as the BLS and the Windows Dashboard. For the client sync script to work, both the config file and some DLLs from the Windows dashboard must be available. The PSX PowerShell Extensions are also required. Go to Scheduled Tasks on your BLS and create a new task with any name. Place a checkmark next to "Execute if no user is logged on". As a trigger, I recommend a weekly execution at a time of your choice. Enter as action like "Execute program".
-file "C:\Program Files (x86)\DSM Management Suite\ClientSync.ps1"