# Remote Office Movement Managing the devices of the sales and marketing teams is a challenging task for an IT administrator. This is because people in these teams tend to be traveling around the country and even the globe to other branch offices or to an event. Tracking their devices and maintaining compliance in situations like this can be a tricky process. However, using Remote Office movement capabilities supported in Endpoint Central, those computers can be tracked and managed efficiently under the appropriate Remote Offices. ## Moving Endpoints Between Remote Offices There are two ways to move a device (endpoint) from one remote office to another: manually, or automatically based on IP scopes. **Note** Moving a device to a different remote office can change the Remote Office-specific settings and resources (such as the Distribution Server) that apply to it. Review the configurations currently targeted to the source and destination remote offices under **Reports → Configuration Reports** before making the change. Configuration Reports can be broken down by user, computer, or type, but not by remote office, so cross-check the affected computers individually. ### Manual Movement 1. Navigate to **Agent → Computers**. 2. Select the computer(s) you want to move. 3. Click **Move to** and choose the desired remote office from the drop-down menu. 4. The selected computer(s) will now be moved to the specified remote office. ![Move to option for moving selected computers to a remote office](https://www.manageengine.com/products/desktop-central/images/add_ro13.png) Moving selected computers to a remote office using **Move to**. **Note** - The WAN agent must be live when the remote office movement is initiated. - If **Move to** does not complete even though the agent shows as online, check that the agent is running the latest version (**Agent → Computers**, or the [Agent Troubleshooting Tool](https://www.manageengine.com/products/desktop-central/help/device-onboarding/agent-troubleshooting-tool.html)). An outdated agent version can also prevent manual movement from completing; reinstalling the latest agent from the console resolves this. ## Automatic Movement ### Users who move between remote offices Different IP scopes for various remote offices can be defined. This way, whenever a device is moving from a local office to a remote location, a new IP address is automatically assigned to it by the DHCP server in the remote office network. On the next refresh policy, the agent determines whether the newly assigned IP address is within the IP range of the new remote office. When a change is detected, the respective device is automatically associated with the corresponding remote office based on the new IP. **Prerequisites** Each Remote Office should have a unique range and not overlap with another Remote Office or IP scope. **Note** This uniqueness requirement is enforced by design and cannot be disabled. If your remote sites legitimately reuse the same private IP range (for example, identical subnets across ships or franchise locations), use a dedicated Remote Office agent package per site instead of relying on IP scope-based automatic movement. Follow the steps below to add an IP scope: 1. Navigate to **Agent → Settings → IP Scope**. 2. Click **Add Scope**. 3. In the **Select Remote Office** list, select the required remote office name. 4. Select either of the following types of IP scope: - **IP Address Range**: Enter the start and end IP addresses. - **Subnet**: Enter the subnet mask and subnet IP address. 5. Click **Save**. ![IP Scope settings page with the Add Scope option](https://www.manageengine.com/products/desktop-central/images/ipscope1.png) IP Scope settings page. ![Add Scope dialog for selecting a remote office and defining an IP Address Range or Subnet](https://www.manageengine.com/products/desktop-central/images/ipscope2.png) Defining an IP Address Range or Subnet for a remote office. You have successfully configured the IP scope. #### Modifying an existing IP scope To update an existing remote office's IP Address Range or Subnet details (for example, to add new IP segments), you do not need to delete and recreate the scope: 1. Navigate to **Agent → Settings → IP Scope**. 2. Locate the remote office's existing IP scope entry. 3. Under **Actions**, click **Modify**. 4. Update the IP Address Range or Subnet details as required and click **Save**. Devices affected by the change will move to the remote office based on the updated scope on the next refresh policy. #### Excluding a single IP from a scope IP scope does not support a single-IP entry (a /32 range or identical start and end IP). To reserve one IP address out of an existing range for a different remote office, split the existing range into two non-overlapping IP Address Range scopes so that the reserved IP falls into its own range, mapped to the other remote office. **Note** - Once an IP scope is configured, automatic movement based on that IP scope takes over and overrides manual movement for matching devices. Manual movement (**Move to**) still works as long as the target device's agent is live; it does not complete if the agent or its Distribution Server is unreachable. - A device manually moved to another remote office will revert to its IP scope-assigned remote office on the next refresh policy. There is currently no option to exclude a specific device from a configured IP scope. ### Users who access Endpoint Central server via internet In situations where users move away from the local office but not to a remote office, the product is accessed via the internet. For cases like this, a default remote office can be configured, so that whenever a user does not fall under the IP scope of any remote office, they are automatically assigned to this default remote office. When **Enable Default Remote Office** is selected, this assignment also applies when no IP scope is defined, so a computer that you move manually to another remote office is returned to the default remote office. To keep a manual move, clear **Enable Default Remote Office** (**Agent → Settings → IP Scope → Configure Default Remote Office**), click **Save**, and then move the computers again using **Move to**. **Note** The remote office selected as the Default Remote Office must be configured for Direct Communication (not a remote office associated with a Distribution Server). Otherwise, configurations for out-of-scope devices may still not apply, since they would depend on Distribution Server connectivity the device no longer has. Follow the steps below to configure the Default Remote Office: 1. Navigate to **Agent → Settings → IP Scope**. 2. Click **Configure Default Remote Office**. 3. Select the **Enable Default Remote Office** checkbox. 4. From the drop-down, select the remote office or local office to be set as the default. 5. Click **Save** to save the changes. ![Configure Default Remote Office dialog with the Enable Default Remote Office checkbox and remote office drop-down](https://www.manageengine.com/products/desktop-central/images/ipscope3.png) Configure Default Remote Office dialog. **Note** - Once IP scopes are configured, automatic movement based on those IP scopes (including the Default Remote Office fallback) takes over and overrides manual movement for matching devices. Manual movement still works whenever the target device's agent is live. - Disabling **Enable Default Remote Office** and saving does not automatically move computers that were previously auto-assigned to the default remote office back to their original remote office. You must move them manually: navigate to **Agent → Computers**, select the computer(s), and click **Move to**. - A change to the Default Remote Office is not reflected instantly; it takes effect at the next Distribution Server replication interval. Once applied, the Default Remote Office designation is also visible as a tag against the corresponding entry in the Remote Offices summary grid, in addition to the IP Scope configuration dialog. - Devices assigned to the Default Remote Office connect directly to the Endpoint Central cloud server for patch metadata, and download patch binaries directly from the respective vendor's site during the deployment window. See [Cloud Architecture](https://www.manageengine.com/patch-management/help/cloud-architecture.html) for details on this communication flow. ## Conclusion This guide covers how to move devices between remote offices either manually or automatically. Automating the process with IP scopes simplifies network management by ensuring that the correct WAN agent is deployed when devices move between locations.