Deploying Kaseya VSA agents to provisioned workstations and servers from a standard image can be a challenge. Using the typical methods result in duplicate GUID’s due to the nature of the technology making it impossible to accurately monitor and report on these types of machines.
The following procedure has been tried a tested (successfully) numerous times on Citrix VDI/SBC environments leveraging Provisioning Server and Machine Creation Services. That being said, the process should work on other systems that are non-persistent providing they have a persistent volume where the application files can be placed.
The term ‘Target Devices’ used throughout this process is what provisioned desktops and servers are called in Citrix Provisioning server. If you are not familiar with Citrix Provisioning server, think of these as being your non-persistent machines that the image is being delivered to.
- The first thing we want to do is create an Organisational Unit (OU) where your update / maintenance target device(s) will live.
- Apply a GPO to the maintenance Organisational Unit (OU) which will stop Kaseya communicating with the master server.
- Create a new agent package configured to install the agent on the persistent drive, typically, the ‘writecache’.
- Create a new version and open the master image / vDisk in maintenance mode (read/write)
- Manually install the package onto the new version making sure the GPO is working which prevents communication with Kaseya (Stopping the agent from connecting to the Kaseya master server which in turn updates the KaseyaD.ini file)
- Once installed, go into the install location on the persistent drive and scoop out a copy of the folder labelled with the agent ID, this is typically found inside ‘Program Files (x86)\Kaseya’ (You will need this for later)
- Stop the Kaseya services.
- Delete the following 3 registry keys:
- Perform typical cleanup tasks and shutdown the machine.
- Promote new version to Test/Production.
- Place the folder that was copied in step 3 into the persistent drive on all target devices that are provisioned from the master image / vDisk (This should be placed in the directory Kaseya expects to find it as configured in step 1 (Regedit can be used to confirm this)
- Reboot your target devices.
That’s it… you’re done. Provisioned / non-persistent machines should now report into the Kaseya master server with a unique GUID as do standard machines.
If Kaseya services fail to start on target devices it’s likely due to the application files being in the wrong path on the persistent drive. Confirm the application files are where the should be according to the registry.
Very keen to hear how you go. Feedback welcome, thanks
Leave a Reply