The OCS Inventory NG Agent Deployment Tool allows network administrators to remotely push the OCS Inventory NG Agent installation to multiple networked computers simultaneously. By automating this rollout, you eliminate the need to manually install the client software on every individual machine. Prerequisites for Remote Deployment
Before using the tool, ensure your environment meets the following requirements: Network & Security Requirements
Administrative Credentials: You must possess local or domain administrator rights for all target computers.
Administrative Shares: Target Windows machines must have administrative shares enabled (e.g., C\(</code>, <code>ADMIN\)). Simple file sharing must be disabled. Necessary Utilities
For Windows Targets: Download the free Microsoft SysInternals PsExec tool.
For Unix Targets: Download the free PuTTY SSH and PSCP command-line utilities. Step 1: Install the Deployment Tool
Navigate to the official OCS Inventory Releases page and download the latest zip archive (e.g., OCSNG-Agent-Deploy-Tool.zip).
Extract the contents of the zip file onto a Windows technician workstation. Execute the OCS-NG-Agent-Deployment-Tool-Setup.exe file.
Accept the license agreement, select your destination directory, and complete the installation wizard. Step 2: Configure the Installation Package Launch the OCS Inventory NG Agent Deployment Tool.
Select the type of operating system you are targeting (Windows or Unix).
Provide the paths to your required third-party utilities (PsExec.exe for Windows or putty.exe/pscp.exe for Unix).
Browse and select your standard OcsAgentSetup.exe installer file.
Input your OCS Inventory Communication Server URL (e.g., http://your_server_ip/ocsinventory).
(Optional) Add any specific command-line switches like /S to trigger a silent background installation. Step 3: Target Selection and Execution
[Technician Workstation] │ ├─► (Checks Windows OS & Active Status) ├─► (Copies files over Administrative Shares: C$) └─► (Triggers Remote Execution via PsExec) ──► [Target Computers]
Specify Targets: Input the target hosts. You can manually type IP addresses, provide a subnet range, or import a text/CSV file containing a list of computer names.
Provide Credentials: Enter the administrator username and password that has rights across the target machines.
Run Deployment: Click the Send or Deploy button to initiate the push. Step 4: Monitor and Save Logs
The utility will test if each remote host is active, copy the installer over the admin share, and execute it using PsExec.
Real-time Monitoring: Monitor the live status of each machine inside the application’s built-in log viewer.
Error Handling: If an entry fails due to network issues or an access denied error, the tool will let you export the failed machines into a separate CSV file.
Export Data: Click Save Logs once the entire process finishes to archive the setup history for audit purposes.
If you need further help setting up your asset management platform, tell me:
Are you deploying to an Active Directory Domain or a Workgroup?
Leave a Reply