Skip to main content

OS Deployment in ServiceOps

OS Deployment automates operating system provisioning across your IT environment. It uses MotadataPXE (Preboot Execution Environment) boot technology to load a deployment agent onto target machines over the network, then applies a captured OS image. You manage images and deployments entirely from the ServiceOps Admin panel, and technicians can initiate deployments remotely using a manual server login or a time-limited passcode. OS Deployment is available for on-premise deployments only.

How OS Deployment Works​

OS Deployment five-stage process diagramFive stages: Setup, Image, Network, Boot, and Deploy shown as chevron banners with icons and descriptions.STAGE 1 · SETUPComponent setupInstall poller & MotadataPXE.msiSTAGE 2 · IMAGECreate & registerBuild, export & registerimage path in ServiceOpsSTAGE 3 · NETWORKConfigure networkPoint router to theTFTP server for DHCPSTAGE 4 · BOOTBoot & authenticateBlank PC boots, launchesOSD.exe & validates credsSTAGE 5 · DEPLOYDeploy & logDeployment task runs;history reported via poller
  1. Setup: Install the poller and MotadataPXE utility on the designated machines.
  2. Image: Build the golden OS image using Image Creator and register its storage path in ServiceOps.
  3. Network: Configure your router or DHCP (Dynamic Host Configuration Protocol) server to point MotadataPXE (Preboot Execution Environment) boot requests to the TFTP server.
  4. Boot: The blank target machine boots over the network, launches OSDApp.exe, and validates credentials or a passcode.
  5. Deploy: ServiceOps runs the deployment task, applies the image, and reports installation history through the poller.

Business Use Cases​

Use CaseScenario
New employee onboardingImage machines before new hires arrive. One deployment task covers the entire batch.
Branch office rolloutDeploy a standard build to 20-200 machines without sending a technician on-site.
Security incident responseRe-image compromised endpoints with a known-good image to cut recovery time from days to hours.
Hardware refreshDeploy a current golden image to all replacement machines in a single batch.
Post-merger standardizationBring newly acquired endpoints to your approved OS build in one campaign.

How This Documentation Is Organized​

The OS Deployment section covers the full end-to-end workflow, not just the ServiceOps UI screens. Some steps happen outside the Admin panel entirely.

PageWhere the work happensWhat it covers
SetupMotadataPXE host machine, DHCP serverInstall MotadataPXE, configure TFTP, set DHCP options
Golden Machine PreparationReference workstationClean, configure, and Sysprep the machine before capture
ImageServiceOps Admin panelCapture the image with OSDApp, register it in ServiceOps
DeploymentServiceOps Admin panelCreate deployment tasks, execute deployments on target machines
Reports and KPIsServiceOps ReportsMonitor deployment activity and audit completed campaigns

Start with Setup if you are configuring OS Deployment for the first time. If your MotadataPXE server and DHCP are already configured, start with Golden Machine Preparation.

Prerequisites​

Before configuring OS Deployment, confirm the following:

  • You have Admin access to ServiceOps.
  • Your account has an active OS Deployment license. Contact your Motadata account manager to enable it.
  • The Discovery and Agents section is visible in your Admin panel.
  • You have a Windows machine available to install the MotadataPXE Utility (MotadataPXE.msi) and the Windows Poller (Poller_V87500.msi).
  • Your DHCP server allows configuration of Option 66 and Option 67 on the scope covering your target machines.
  • You have a golden machine (a fully configured reference workstation or server) to capture the OS image from. Remove all non-essential or additional applications from the golden machine before capturing the image. Every application present on the golden machine is replicated to all target machines during deployment.
  • A shared network path (UNC format, for example \fileserver\images) is available and accessible to all machines, including the golden machine and all target machines.
  • The OS Deployment Manager role is assigned to any technician who will manage images and deployments.

Roles and Permissions​

OS Deployment uses a dedicated permission set under the Manage OS Deployment permission group.

PermissionWhat It Allows
ViewRead-only access to OS Deployment. The user sees the Image and Deployment sections but cannot make changes.
Manage ImageCreate, edit, and delete OS images in the Image section. Requires View.
Manage DeploymentCreate, edit, and cancel deployment tasks in the Deployment section. Requires View.

The out-of-the-box OS Deployment Manager role includes all three permissions. To assign the role, go to Admin > Users > Roles.

Known Limitations​

  • OS Deployment is available for on-premise deployments only. Cloud-hosted ServiceOps instances do not support this feature.
  • OS Deployment supports Windows target machines only. Linux and macOS targets are not supported.
  • Only offline images are supported. Live or online imaging of a running machine is not supported.
  • The MotadataPXE.msi (TFTP service) must be installed on a Windows machine.
  • Only one active deployment task can run per Poller at a time. Plan sequential deployment windows if you need to deploy different images through the same Poller.
  • The 6-digit passcode is generated by ServiceOps and cannot be manually set.
  • Image files are stored externally and must be accessible to both the golden machine during capture and the target machine during deployment. Common configurations include a shared network path (UNC), a separate drive not selected at image creation time, or a file server on another machine. ServiceOps does not manage image storage, replication, or backup.
  • Machines that are already running cannot be targeted remotely. The machine must reboot and boot via MotadataPXE to receive a deployment.