---
title: "HP ThinPro Agent Installation"
slug: "edge-dx-agent-installation-for-hp-thinpro"
tags: ["ControlUp for Desktops"]
updated: 2026-07-22T11:34:51Z
published: 2026-07-22T11:34:51Z
canonical: "support.controlup.com/edge-dx-agent-installation-for-hp-thinpro"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.controlup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HP ThinPro Agent Installation

Important

Before you deploy any Agents, read the [prerequisites for Agent deployment](/tim-reorg/docs/prerequisites-for-agent-deployment) and make sure that your environment is ready.

ControlUp for Desktops supports HP ThinPro versions 7.1, 7.2, 8.0, and 8.1.

## Before you begin

You'll need your ControlUp **tenant name** and **device registration code**. To get these, go to **Devices > Configuration > Agent Registration.![Agent Registration Settings](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/AccessAgentRegistrationSettings(1).png)**

## Agent installation

Select your HP ThinPro version below:

Versions 8.1, 8.0, 7.2Version 7.1

To install the Agent onto a device running HP ThinPro version 7.2, 8.0, or 8.1, run the following script. You must replace `<tenant url>` and `<registration code>` with the correct values for your organization.

```plaintext
curl https://downloads.sip.controlup.com/hptpinstallv2.sh | sudo bash -s <tenant url> <registration code>
```

**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=&lt;tenant url&gt; devregcode=&lt;reg code&gt; 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:

```plaintext
fsunlock
systemctl stop avaceesip
/usr/local/avacee/sipagent proxy=10.0.0.1:8888 store_settings_only=1
systemctl start avaceesip
fslock
```

**Update existing agent**

To update an existing Agent to the latest GA Agent version, run the following script:

```plaintext
fsunlock
service avaceesip stop
curl https://downloads.sip.controlup.com/avaceesipagent-linux.tar --output ./sipagent.tar
tar -xf ./sipagent.tar -C /usr/local/avacee/
chmod +x /usr/local/avacee/sipagent
chmod +x /usr/local/avacee/RCNotifications

chmod +x /usr/local/avacee/cu4dshell

fslock
service avaceesip start
fslock
```

**Additional information**

- 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 Agent onto a device running ThinPro 7.1, use the following command. Replace `&lt;tenant url&gt;` and `&lt;registration code&gt;` with the correct values for your organization.

```plaintext
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.

**Additional information**

The installation script does the following:

1. The device is put into a writable mode using fsunlock
2. 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.
3. The standard Linux Agent is downloaded into /usr/local/avacee and is marked as executable.
4. The settings needed for the Agent to communicate with the organization are created by running the Agent with the store_settings_only=1 flag.
5. 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:

1. If there is a proxy, check that it is configured.
2. Check that the device is able to connect to <tenantname>.sip.controlup.com on https.