In this article

Network administrators use this article to move iOS Roaming Client deployments from one Site to another using a mobile device management (MDM) platform. This is the recommended approach for large-scale fleet migrations.

For moving individual devices or Windows and macOS agents, reassign the Roaming Client from the dashboard instead.

How it works

Starting with iOS Roaming Client v1.4.4, the agent continuously validates the Site Key in the installed MDM configuration profile. When an updated profile containing a new Site Key is pushed to a device, the agent detects the change and re-registers automatically—no reinstall, user action, or dashboard intervention required.

When the Site Key change is detected, the agent:

1. Unregisters from the current Site
2. Registers with the new Site
3. Applies the filtering policy associated with the new Site immediately
4. Fires the uninstall notification email for the old Site, if configured
5. Assigns a new admin PIN based on the new Site's settings

Prerequisites

• iOS Roaming Client v1.4.4 or higher on all target devices
• Devices enrolled in an MDM platform with a .mobileconfig profile containing the site_key key
• Permission to update and push configuration profiles via the MDM provider

Move devices to a new Site

Step 1: Get the new Site Key

1. From the DNSFilter dashboard, navigate to Deployments and select Roaming Clients
2. Select Install Roaming Client
3. Select the destination Site and copy the Site Key

Step 2: Update the MDM configuration profile

1. Open the existing .mobileconfig profile in the MDM platform
2. Replace the site_key value with the new Site Key copied in Step 1
3. Save the updated profile

Step 3: Push the updated profile to devices

Deploy the updated profile to the target devices via the MDM platform. Once a device receives the profile, the agent detects the Site Key change and re-registers automatically.

Devices appear in the new Site in the DNSFilter dashboard within the next sync cycle.

What to expect in the dashboard

• Devices disappear from the old Site's Roaming Client list and appear under the new Site
• If an uninstall notification email is configured on the old Site, it fires when each device unregisters—this is expected and does not indicate an issue
• The new Site's filtering policy applies as soon as registration completes on each device

Related content

• Reassign a Roaming Client to a different Site or Organization
• iOS Roaming Client deployment guide