To install a Robot to a Windows system with ADE, the automated_deployment_engine (ADE) must be installed on a Windows OS. The recommended solution is that ADE be installed on a Windows hub that the robot reports to.
To use ADE from UMP USM portlet, ADE must installed on the remote hub that the robot will be reporting to.
***Note that If the target machine is a Windows box, then the hub MUST be a Windows HUB as well.***
If ADE is installed on a Windows robot you can use the xml file on the ADE server to deploy to Windows servers.
Please review the help documentation below: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/9-0-2/installing/deploy-robots/bulk-robot-deployment-with-an-xml-file.html
The ADE probe on the Primary hub sends the jobs to the remote ADE. The remote ADE keeps track of the job status, and also the primary ADE keeps track of the job status as well. The status is kept in the automated_deployment_engine.h2.db file on each ADE.
If the Primary ADE's h2.db files become corrupted and the ADE probe was not properly recording the status of the job, this may cause USM to get stuck on ~50% deployment even though robot could be getting deployed.
To try and resolve this the steps are:
1. Stop the ADE probe on the remote hub and also the primary hub.
2. Open RDP sessions to the remote hub and also the primary hub.
3. Delete the following files -- some of them may not exist and that is OK but please delete all the ones which exist.
\Program Files(x86)\Nimsoft\probes\service\automated_deployment_engine\automated_deployment_engine.h2.db (robot)
After deleting all the files, start up the ADE probes and try the deployment again.