HP ThinPro Agent Installation
This article covers how to install the Edge DX Agent onto HP ThinPro OS devices.
The following OS versions are supported:
- HP ThinPro 7.1
- HP ThinPro 7.2
Before You Begin
You'll need your tenant URL and device registration code. You can find these on the Downloads page.
ThinPro devices use the Linux Agent. The instructions in this article install the latest GA version of the Linux Agent. You can see the latest version on the Downloads page.
Select your ThinPro OS version below.
To install the Edge DX Agent onto a device running ThinPro 7.2, use the following script. Replace
<tenant url> and
<reg code> with the correct values for your organization.
fsunlock mkdir -p /writable/controlup/avacee ln -s /writable/controlup/avacee /usr/local curl -o /usr/local/avacee/sipagent https://downloads.sip.controlup.com/avaceesipagent-linux chmod +x /usr/local/avacee/sipagent curl -o /usr/local/avacee/RCNotifications https://downloads.sip.controlup.com/RCNotifications chmod +x /usr/local/avacee/RCNotifications /usr/local/avacee/sipagent tenant=<tenant url> devregcode=<reg code> store_settings_only=1 cat <<EOF > /writable/etc/systemd/system/avaceesip.service [Unit] Description=ControlUp Edge DX Service [Service] ExecStart=/usr/local/avacee/sipagent WorkingDirectory=/usr/local/avacee/ [Install] WantedBy=multi-user.target EOF systemctl daemon-reload systemctl enable avaceesip systemctl start avaceesip fslock
Set up a Proxy Server Connection
To set up a proxy server connection at the time of installation, add a
proxy parameter to the following line before running the installation script above, and enter your proxy IP address and port number. For example:
/usr/local/avacee/sipagent tenant=<tenant url> devregcode=<reg code> proxy=10.0.0.1:8080 store_settings_only=1
To set up a proxy server connection for an existing Agent, use the following script and enter your proxy IP address and port number:
fsunlock service avaceesip stop /usr/local/avacee/sipagent proxy=10.0.0.1:8888 store_settings_only=1 fslock service avaceesip start
Update Existing Agent
To update an existing Agent to the latest GA Agent version, run the following script:
fsunlock service avaceesip stop curl https://downloads.sip.controlup.com/avaceesipagent-linux --output /usr/local/avacee/sipagent chmod +x /usr/local/avacee/sipagent fslock service avaceesip start
- The ThinPro 7.2 Agent uses a systemd service to auto-start the Agent.
- A writeable area is created through a symbolic link.
- A service file is created.
To install the Edge DX Agent onto a device running ThinPro 7.1, use the following command. Replace
<tenant url> and
<registration code> with the correct values for your organization.
curl https://downloads.sip.controlup.com/hptpinstall.sh | bash -s <tenant url> <registration code>
Running the script above installs the Agent but doesn't start the Agent. The Agent starts and registers the device in your organization only after the device reboots.
If you are creating an image with the Agent, you must create the image before the device reboots and the Agent registers in your organization. This allows the Agent to store unique information about the device the image is installed on, and not the device used to create the image.
Update Existing Agent
To update an existing Agent to the latest GA Agent version, run the installation script again.
The installation script does the following:
- The device is put into a writable mode using fsunlock
- A folder is created on the writable area (/writable/controlup) and is symbolic linked to the non-writable file system (/usr/local/avacee). This allows the Agent to write to /usr/local/avacee and for the content written there to be preserved.
- The standard Linux Agent is downloaded into /usr/local/avacee and is marked as executable.
- The settings needed for the Agent to communicate with the organization are created by running the Agent with the store_settings_only=1 flag.
- The initialization configuration file /etc/init/controlup-edge.conf is created. This file is needed to start the Agent when the device is rebooted.
The steps above allow the Agent to register the device in the organization. Once the device is rebooted, it might take a minute before the Agent becomes active. If it takes longer than 2 or 3 minutes, something has likely gone wrong. In that case, check to see if you have installed the Agent correctly. If the Agent still does connect to your organization, perform the following troubleshooting steps:
- If there is a proxy, check that it is configured.
- Check that the device is able to connect to <tenantname>.sip.controlup.com on https.