How does OpManager MSP deploy the agent in the remote machines when it is triggered from the webclient?

When using the Deploy Agent feature from the OpManager MSP webclient, these are the steps that are executed in the background:

• For deploying the agent in a device, Windows credentials will be used. This credential needs to have administrator privileges in order for the installation to run without any issues.
• OpManager MSP initiates a network connection to the remote machine using the provided credential, and if successful, transfers the agent files to the remote machine's Temp directory.
• Then using the Windows credentials of that device, OpManager MSP tries to initiate the installation of the agent using WMI protocol. If the credentials are passed successfully and OpManager MSP is able to connect to the device, it then triggers the remote installation of the agent.
• If the device could not be contacted via WMI, OpManager MSP then uses the OPMAgentInstallerSvc deployment file to remotely install the agent in the device.

Note: If your organization has restrictions regarding the usage of third-party executables in your network, feel free to flag/remove the OPMAgentInstaller and OPMAgentInstallerSvc executable file from the OpManager_MSP_Probe bin directory. This will NOT affect the remote agent deployment in any way.