How can we help? 👋

Agent Rollout via Active Directory Policy

We are not using .MSI packages since the installation is normally just done when the computer is restarted, which is not always possible for servers.


We don’t use .MSI packages because the installation is normally done when the computer is restarted, which is not always possible for servers.


Set up a public distribution share (SMB) to store installation files

We suggest utilizing the Active Directory NETLOGON share because:

  • it is generally accessible across all sites
  • it is automatically replicated throughout the domain sites

Alternatively, you may utilize other publicly available network shares (Access Level: Read/Execute for Everyone). Please adjust the following steps to match your domain configuration and distribution share choice.

  • Log in as the domain administrator on the domain controller.
  • Locate the NETLOGON share (usually the FQDN of your Active Directory).
  • For example, FQDN: hs2n.local → Netlogon Share: \hs2n.local\NETLOGON
  • Create a folder named XEOX_Agent.
  • Copy the .exe file downloaded in step 1 to the folder.
  • Create a batch file named XEOX_agent_install.bat.
  • Open the new file XEOX_agent_install.bat with Notepad and enter the following CODE.
  • Version 1 (simple; only verifies if at least one agent is installed and installs if none are installed) - Future agent updates will be done over the internet.


This BAT file checks if the Agent is already installed (Program Files contains the XEOX folder). If not, it will execute the installer with

  • /S for silent installation
  • /U do not overwrite later versions Upgrades to later versions will be done via XEOX.
if exist "%ProgramFiles(x86)%\xeox\version.txt" goto nothing
if exist "%ProgramFiles%\xeox\version.txt" goto nothing
echo Installing XEOX Agent
%~dp0XEOX_Agent_for_hs2n-1_4_4_18.exe /S /U
echo Install Finished

echo XEOX is already installed, doing nothing

Version 2 (more sophisticated, you can also do updates by creating an additional Batch File called serverversion.bat)


If you prefer to roll out Agent Upgrades via Group Policy too (less network load), you have to check the installed version via BAT file:

rem load installed version
if exist "%ProgramFiles(x86)%\xeox\version.bat" call "%ProgramFiles(x86)%\xeox\version.bat"
if exist "%ProgramFiles%\xeox\version.bat" call "%ProgramFiles%\xeox\version.bat"

rem load version from setup file
call %~dp0setupversion.bat

rem if versions are not equal
if "%xeoxversion%"=="%setupversion%" goto nothing

rem Install XEOX Agent
%~dp0XEOX_Agent_for_hs2n-1_4_4_18.exe /S /U

rem echo Install Finished

rem Xeox is already installed, doing nothing

setupversion.bat Insert the version from your downloaded agent. In case of an Agent Upgrade, download new Setup and update the version in setupversion.bat.

set setupversion=

Adopt the LINE XEOX_Agent_for_hs2n-1_4_4_18.exe /S /U with the .exe file you got in Step 1 (make sure that the %~dp0 and the /S /U is not touched).

The final folder structure should look like this (the .exe filename will be different):

Notion image

Create a new GPO object with a scheduled task

  • Logon with a domain admins to a domain controller.
  • Open the Group Policy Management Console.
  • Name it XEOX Cloud Agent Rollout.
Notion image
  • Right-click this newly created GPO and then click Edit.
  • Expand computer or user configuration and then go to the following path:
    • Preferences -> Control Panel Settings -> Scheduled Tasks
  • Right-click on scheduled tasks and then click New -> Scheduled Task (Windows Vista and Later)
  • Change the following properties in the tab General
Notion image
  • Tab Trigger

click on New... and change the properties

Notion image
  • Tab Actions
    • click on New... and then Browse... and select the .bat file that we have created in step 2 on the NETLOGON Share e.g.

Notion image
  • Make sure that you are using an UNC Path. Do not use the name of the specific domain controller, but always use the domain FQDN.
    • e.g. \\hs2n.local\netlogon\XEOX_Cloud_Agent\XEOX_cloud_agent_install.bat
  • Click OK and Apply.
  • Link the GPO Object to a test OU (organisational unit).
  • Wait a few minutes until the GPO objects and links are replicated.
  • Execute the update on a computer and check if the scheduled task was created.
  • Wait until its executed automatically and manually check if the XEOX Cloud Agent Folders are created on the machine.

Firewall exceptions

The XEOX Cloud Agent is communicating via https (port 443) to the XEOX Cloud Server ( Please configure your local firewall to allow port 443 from all windows client machines to

Verify installation

  • Verify that the GP Update is working
  • Verify that the scheduled task is created by the GPO
  • Verify that XEOX Cloud Agent is created
Notion image
  • Login to XEOX Cloud Console and navigate to XEOX / Hardware List
Notion image
  • The computers should show up here.
Did this answer your question?