Installing OpManager agent on devices using Startup script

Windows GPO can be used to install the OpManager agent in multiple devices, even when other methods of installation fail. Various reasons behind agent installation failure are as follows:

• Access denied
• Network path not found
• Unknown username or password
• No network provider accepted the given network path
• Not enough storage available to install agent

Note: Ensure that the network has a domain-based setup and not a workgroup-based setup. You can even map the script to include the entire domain even if you have the OpManager agent installed only in a few devices, as the agent will be installed only in devices that don't have the agent installed already.

1. In the OpManager web console, go to Settings → Discovery → Deploy Agent.
2. Click on the "Download" button to get the OpManager Agent zip file. Extract the zip file and paste the extracted OpManagerAgent.msi and OPMAgentServerInfo.json files in the local directory.
3. Identify the parent domain server(s) for the client computers, and copy the extracted OpManagerAgent.msi and OPMAgentServerInfo.json files to that domain server(s).
4. In the AD server, click on Start → Run
5. Enter gpmc.msc and click Okay.
6. Right-click on the domain, and select Create and link a GPO here.

1. Specify a name for the GPO.
2. Select the GPO.

1. Right-click the GPO and click on "Edit".
2. For executing VBScript, follow these steps (refer this image):
   • Expand Computer Configuration → Policies → Windows Settings → Scripts
   • Right-click Startup, and click Properties.
   • Click Show Files.
   • Drag and drop the InstallOPMAgent.vbs (download the .txt file and rename it as .vbs) and the extracted OpManagerAgent.msi and OPMServerInfo.json files to this location. Copy the path of this location (\\Domain name\SysVol\Domain name\Policies\{ID}\Machine\Scripts\Startup) and close the window.
   • In the Startup Properties dialog box, click Add.
   • Browse and navigate to the location, and copy the browsed path (\\Domain name\SysVol\Domain name\Policies\{ID}\Machine\Scripts\Startup).
   • Select InstallOPMAgent.vbs script.Then specify the path (copied location) and the script as mentioned below:

     (\\Domain name\SysVol\Domain name\Policies\{ID}\Machine\Scripts\Startup)\InstallOPMAgent.vbs

   • Specify the script parameter as mentioned below:
     OpManagerAgent.msi
3. As an alternative to VBscript, you can also execute PowerShell script for agent installation using GPO. For executing PowerShell scripts, follow these steps and refer this image):
   • Ensure if PowerShell is enabled in all the client computers before execution of this script.
   • Expand Computer Configuration → Policies → Windows Settings → PowerShell scripts.
   • Right-click Startup, and click Properties.
   • Click Show Files.
   • Drag and drop the psinstallopmagent.ps1 (download the .txt file and rename it as .ps1) and the extracted OpManagerAgent.msi and OPMAgentServerInfo.json files to this location. Copy the path of this location (\\Domain name\SysVol\Domain name\Policies\{ID}\Machine\Scripts\Startup) and close the window.
   • In the Startup Properties dialog box, click Add.
   • Browse and navigate to the location, and copy the browsed path (\\Domain name\SysVol\Domain name\Policies\{ID}\Machine\Scripts\Startup).
   • Select the psinstallopmagent.ps1 script.Then specify the path (copied location) and the script as mentioned below:

     (\\Domain name\SysVol\Domain name\Policies\{ID}\Machine\Scripts\Startup)\psinstallopmagent.ps1

   • Specify the script parameters as mentioned below:
     OpManagerAgent.msi
4. Click "Okay" to close the Add a Script dialog box and the Startup Properties dialog box, and close both the Group Policy Object Editor and the Group Policy Management dialog boxes too.

This script will be executed on the next reboot of the client computers after the deployment. Once this script is executed successfully, the OpManager agent will be installed in all the client computers. You can check these newly added devices under the Inventory page in OpManager.