---
name: satellite-ts-host-not-attaching
title: Why aren't my hosts attaching to my location?
description: Resolve issues where hosts aren't attaching to your Satellite location when the hosts are cloned virtual machines.
last-updated: 2026-08-17
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/satellite?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why aren't my hosts attaching to my location?
{: #host-not-attaching}

Resolve issues where hosts aren't attaching to your Satellite location when the hosts are cloned virtual machines.
{: shortdesc}


When you run your host attach script, some hosts are not attaching to your location, but you do not receive an error message. Your host machines are virtual machine clones.
{: tsSymptoms}

Network identities of virtual machines that are attached to the same location must be unique. If you are using cloned virtual machines, these clones can lack a unique network identity and Satellite cannot attach them all to the location. To verify that the network identities are not unique, SSH into the host and run the following commands.
{: tsCauses}

```sh
cat /etc/machine-id
cat /var/lib/dbus/machine-id
```
{: pre}

If the IDs match a host's IDs that are already attached, then you must take steps to resolve this issue.

To resolve this issue, follow these steps.
{: tsResolve}

1. Remove all hosts from the location.
2. Reload your operating systems on each host.
3. SSH into each host and run the following commands.

    ```sh
    rm -f /etc/machine-id
    dbus-uuidgen --ensure=/etc/machine-id
    rm -f /var/lib/dbus/machine-id
    dbus-uuidgen --ensure
    ```
    {: pre}

4. Reattach your hosts.