Before we start with the DSM Management Suite guide: Thank you for choosing my software. A lot of time and love was put into the software and I very much hope that you can successfully integrate and use the application in your company. If you encounter any problems, you can contact me by Patreon and get help directly from me. This direct Contact Option is reserved exclusively for Patreon Edition users.
Step 1 - Download your DSM Management Suite version
If you are a Community Edition user, you can simply download your DSM management application from my server. Install the setup file on your server (BLS). The installation is very simple and you only have to click on next.
Step 2 - Install the PowerShell Extensions
The DSM Management Suite uses the PowerShell Extensions from NWC-Services GmbH to carry out all SOAP requests. If you have not yet owned the PSX PowerShell Extensions, you must first obtain and license them from the manufacturer.
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 and can also be retained when changing editions. The backend can run on both a Windows and a Linux server. If you did not want to install the backend on your own server, you can install the application directly on your BLS. If you decide to have your own server, you have the option of using a Linux server, which offers you performance advantages. As an enterprise user, you also have the option of downloading a pre-installed VM. However, the decision is yours. Click on the respective blog post to get the installation instructions for the respective operating system.
Since Juni 2020 there is also the option to install the backend and web dashboard with docker
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 installed directly with the Windows Dashboard and you should already have received a desktop icon. If you don’t have a desktop icon, 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 to 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.
The username and password immediately after the new installation are:
It is of course recommended that you change the password after completing the installation.
You can enter the location of your current company headquarters as the location. Just leave the value at DefaultLocation if you don’t have multiple locations.
If everything is configured correctly, you should now be able to establish a connection via “Settings-> Test connection”. If the connection is working, click on “Settings-> Save”
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 z. B. DSM MS Sync.
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”.
As a program path we take the Powershell:
Als Parameter geben wir -file und den Pfad zu unserer ClientSync Powershell Datei an.
-file "C:\Program Files (x86)\DSM Management Suite\ClientSync.ps1"
Run the PowerShell file manually for the test. If configured correctly, the script should be able to log in to the API and BLS. As soon as you see that patches are synchronized (with the text: Success), both the backend and the client sync script work.