# Remote OS Deployment for Branch Offices and Distributed IT Environments

Organizations with more than one office location eventually run into the same problem: someone has to get a standard, properly configured operating system onto every computer, at every site, without flying an IT technician to each one. That task is remote OS deployment, and it gets harder as the number of locations grows.

## What is remote OS deployment?

Remote OS deployment is the process of deploying OSs to computers located outside the organization's network; like endpoints in branch offices and travelling or work-from-home employees. For organizations with multiple branch offices and a distributed workforce, installing an OS is just part of the challenge. IT teams also need to maintain a standard OS configuration across branch offices, while managing network bandwidth, different hardware, and deployment requirements at each office.

OS Deployer lets administrators manage these deployments centrally. An existing OS image can be replicated to a remote office through a Distribution Server and used to deploy OSs at that location. This allows IT teams to maintain a standard configuration across offices without creating a separate master image for every location.

## What Makes OS Deployment Across Multiple Offices Difficult for IT teams?

Deploying OSs at one office is fairly straightforward. Doing it across dozens of locations introduces a different set of challenges.

### Bandwidth constraints

A Windows image can be several gigabytes in size. Sending that image from headquarters to every computer at a branch can put significant strain on WAN links, particularly when several computers need to be deployed.

### Standardization drifts over time

When branches handle their own installations, small differences start to creep in. A technician may install an application, change a setting, or configure a computer differently to meet a local requirement. Over time, computers that were meant to follow the same standard can end up with different configurations.

### Hardware varies by site

Branch offices do not always purchase computers at the same time or from the same vendor as headquarters. Different locations may have different laptop and desktop models, making it difficult to maintain a separate image for every hardware configuration.

### Limited visibility

When deployment is handled independently at each branch, the central IT team has less visibility into what has been deployed, what is still pending, and where something has failed.

### New offices mean starting over

Opening a new office should not mean rebuilding the entire imaging process. Without a reusable image and deployment setup, every new location becomes another project for IT.

## How Remote OS Deployment Works in OS Deployer

OS Deployer handles remote OS deployment through a distribution server set up at each remote office. This is how it works:

1. Capture the golden image at the local office.
2. Set up the remote office and its distribution server from the Admin tab.
3. Replicate the OS image to the distribution server on a schedule and data transfer rate you control.
4. Deploy locally at the remote site via PXE, USB, or ISO, with drivers injected automatically for that site's hardware.
5. Post-deployment configuration runs automatically: naming, domain or OU join, profile migration, and app installs.

It becomes difficult to create and maintain a separate OS image for every branch office or remote endpoint. OS Deployer enables administrators to replicate an existing image to a remote office instead. The Distribution Server at the remote location acts as the local point for image and driver replication. Once the required image is available there, it can be used to deploy OSs to computers at that location.

For more details, refer to ManageEngine's [OS Deployer's network architecture guide.](https://www.manageengine.com/products/os-deployer/help/architectures/osd-architecture.html?utm_source=deploy-os-anywhere)

## How to replicate OS images while keeping bandwidth usage low?

Large OS images can put pressure on WAN connections when they are transferred between offices. OS Deployer allows administrators to configure replication policies to control data transfer rate, replication interval, days, and time schedule. For example, an organization can schedule replication outside peak working hours or limit the transfer rate to avoid affecting other network traffic. Once the image has reached the remote office, it is available through the Distribution Server for deployment at that location. This gives IT teams more control over when and how large image transfers take place instead of repeatedly sending the image from headquarters to individual computers.

## How does OS Deployer deploy OSs to remote offices with varied hardware models?

Computers purchased for different offices are rarely identical. One location may use Dell laptops, another may have HP desktops, while another may use a mixture of models. Maintaining a separate image for every hardware type adds another layer of work for IT teams. OS Deployer's Hardware Independent Deployment allows a common OS image to be deployed across different hardware models. The required drivers can be injected as part of the deployment process. This allows IT teams to use a single deployment template across different hardware models while accounting for hardware differences at each location.

Learn more about [Hardware Independent Deployment](https://www.manageengine.com/products/os-deployer/hardware-independent-deployment.html?utm_source=deploy-os-anywhere)

## Frequently Asked Questions

![faq](https://www.manageengine.com/ems/images/icon/box-icon-v5-7.svg)

### 1. What is remote OS deployment?

Remote OS deployment is the process of deploying an operating system to computers at another location without requiring the IT administrator to physically configure each computer.