Problem:
We don’t use .MSI packages because the installation is normally done when the computer is restarted, which is not always possible for servers.
Solution:
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.
XEOX_agent_install.bat
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.
- /T for Token, you need this in order for the installation to work
if exist "%ProgramFiles(x86)%\xeox\version.txt" goto nothing
if exist "%ProgramFiles%\xeox\version.txt" goto nothing
echo Installing XEOX Agent
%~dp0XEOX_Agent_GENERIC_2_1_0_57.exe /S /U /T=[Token*]
echo Install Finished
exit
:nothing
echo XEOX is already installed, doing nothing
Adopt the LINE XEOX_Agent_GENERIC_2_1_0_57.exe /S /U /T=[Token*]
with the .exe file you got in Step 1 (make sure that the %~dp0
and the /S /U
is not touched).
* Adopt the token, with the connection key you get while downloading the agent. Copy:
![Notion image](https://www.notion.so/image/https%3A%2F%2Fprod-files-secure.s3.us-west-2.amazonaws.com%2F38d43367-6be1-4655-9d6e-b7461519c23c%2F996e8b3f-ec1d-4db0-8c21-546c650fa78c%2Fscreely-1719842400996.png?table=block&id=1e62751f-9739-43ba-985a-093b8d10fcfa&cache=v2)
Full command example:
%~dp0XEOX_Agent_GENERIC_2_1_0_57.exe /S /U /T=EJCRUL5MQZKW72OLHYVX3DUPGTN1IBNFXWRQZTL72YBKMTHZDPIF8KGLR9AX5NQLNV7O3YJSWTQ9BHJZKF2IXGMP1ARW2EVXTXMQBY8TPFSQ7F4YJ3WPEFJLQAT3BHCYMLT2YCV5HBUNJQFIE9MWBCTO43N2ZKDGS8JXLM4NY3DCQBW57H5TUYZ29WFJAKT8RPBSKXDJYUC6MNQUHV35SOYE7W2G6PIUTXB4LFJZM9HDYKRXBE2IP56WS47NQFTHC8MUAJFLRKPZSQN5WTJ84DHEJPKV6IS4X3GOQZ2HMYTWPAKJHURQ3ZXBCP5ELTUKY2NEH5XMWDZVL4ONQYTR3FC58VUBY7JGQTA3JKZLYWX4BEVI9URQ38MFYL6XE5PTNZ2RVM7DSW8QCYJ3GZLKA8X9BPFM45RECHYWJGPKVTU4Q6DYM7WLZFXHPBQNEUTGV3RNY98U6JBDZH24CSOL3QMVX5K7HPI2BXEGWFTYNLV9DRU7FZ4JHTXPA3LGJKB6IYU95Q2W8DMXAVZK4LTSHWQY73FJRYCNXU9PLTEBV2HG53UMKQ
The final folder structure should look like this (the .exe filename will be different):
![Notion image](https://www.notion.so/image/https%3A%2F%2Fprod-files-secure.s3.us-west-2.amazonaws.com%2F38d43367-6be1-4655-9d6e-b7461519c23c%2F8c6021ea-2396-4bbc-b74e-8399005c1453%2Fscreely-1719837475677.png?table=block&id=cd4144e2-d5bf-4862-9348-b9746034d1de&cache=v2)
Create a new GPO object with a scheduled task
- Logon with a domain admins to a domain controller.
- Open the Group Policy Management Console.
- Create a new Group Policy Object (https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/create-a-group-policy-object).
- Name it XEOX Cloud Agent Rollout.
![Notion image](https://www.notion.so/image/https%3A%2F%2Fprod-files-secure.s3.us-west-2.amazonaws.com%2F38d43367-6be1-4655-9d6e-b7461519c23c%2F59cc423e-212b-4533-aa90-b2dc5e48cb87%2Fscreely-1719839655476.png?table=block&id=72313e1d-a455-4418-9d19-057fc1a5323c&cache=v2)
- 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](https://www.notion.so/image/https%3A%2F%2Fprod-files-secure.s3.us-west-2.amazonaws.com%2F38d43367-6be1-4655-9d6e-b7461519c23c%2F7838ac25-e600-4498-98ab-1446e86dc3ae%2Fscreely-1719841940900.png?table=block&id=dea51bd2-54c5-475a-95ef-a873950b6edb&cache=v2)
- Tab Trigger
click on New... and change the properties
![Notion image](https://www.notion.so/image/https%3A%2F%2Fprod-files-secure.s3.us-west-2.amazonaws.com%2F38d43367-6be1-4655-9d6e-b7461519c23c%2Fbc40bfb9-a99c-4738-b83e-d9a39ef38add%2Fscreely-1719842009211.png?table=block&id=7276362e-0177-4394-8fd1-797e360de298&cache=v2)
- 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](https://www.notion.so/image/https%3A%2F%2Fprod-files-secure.s3.us-west-2.amazonaws.com%2F38d43367-6be1-4655-9d6e-b7461519c23c%2F7f4fa66d-ff13-474a-9157-d6ffb4a1b4e8%2Fscreely-1719842105628.png?table=block&id=07cbf15d-8334-40cf-90a8-999e86430d6c&cache=v2)
- 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 (https://login.xeox.com). Please configure your local firewall to allow port 443 from all windows client machines to login.xeox.com.
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](https://www.notion.so/image/https%3A%2F%2Fprod-files-secure.s3.us-west-2.amazonaws.com%2F38d43367-6be1-4655-9d6e-b7461519c23c%2F120794f4-c7a8-432e-ae99-6c156683f81b%2Fscreely-1719842315038.png?table=block&id=0b3f4705-41d4-480b-994c-f814a99b5be7&cache=v2)
- Login to XEOX Cloud Console and navigate to XEOX / Hardware List
![Notion image](https://www.notion.so/image/https%3A%2F%2Fprod-files-secure.s3.us-west-2.amazonaws.com%2F38d43367-6be1-4655-9d6e-b7461519c23c%2Fe8715a23-d5cb-499f-b3ba-6861afea76f7%2Fscreely-1719837275261.png?table=block&id=2a1be53f-cc0a-499f-8013-78639a191ba3&cache=v2)
- The computers should show up here.