OS Deployment FAQ
Common questions about OS Deployment in ServiceOps, for IT Admins and Technicians.
What is the difference between the Manual and Passcode-Based deployment methods?
A: Manual deployment requires a technician to enter valid ServiceOps credentials on each target machine, then manually select the image from the list before the deployment begins. Passcode-Based deployment uses a 6-digit code that any authorized person can enter, with no ServiceOps credentials needed. Once the passcode is authenticated, the deployment starts automatically without any further selection. Use Manual for small or high-security deployments where a technician is present. Use Passcode-Based for large rollouts where machines are distributed or unattended.
Do I need a dedicated machine for the MotadataPXE server?
A: Yes. The MotadataPXE server requires a dedicated Windows machine with the Windows Poller (Poller_V87500.msi) installed on it. The Poller is required for the TFTP service in the MotadataPXE package to communicate with ServiceOps. The machine must remain on and reachable on the network throughout every deployment window, and tftpd64.exe must be running as Administrator at all times during deployment. Running other network-intensive services on the same machine can slow or interrupt image transfers.
Can I use Wi-Fi for MotadataPXE boot?
A: No. MotadataPXE boot requires a wired Ethernet connection. Both the MotadataPXE host and all target machines must be connected via wired LAN during setup and deployment.
Can I run both the tftpd64 DHCP and my network DHCP server at the same time?
A: No. Running two DHCP servers on the same subnet causes IP conflicts and unpredictable MotadataPXE responses. Use one or the other. Either enable the built-in DHCP in tftpd64.exe and leave your network DHCP server unconfigured for that subnet, or use your own network DHCP server and configure Option 66 (MotadataPXE host IP) and Option 67 (bootx64.efi) on the scope covering your target machines, keeping the built-in DHCP in tftpd64.exe disabled.
How large are captured OS image files?
A: Image size depends on the OS version, installed applications, and how much data is on the captured drive. A typical Windows 11 image with standard applications is 10 GB to 20 GB. Ensure your image storage share has sufficient free space before starting a capture.
Where should I store the captured image file?
A: Store images on a dedicated network share (UNC path) that both the ServiceOps Poller and all target machines can reach. The share must be on a separate machine or drive that is not being captured. Do not save the image to the same drive selected for capture, as this causes errors.
Can I power on the golden machine after running Sysprep?
A: No. Once Sysprep shuts the machine down, capture the image immediately. If you power it on again, Windows re-specializes the OS and assigns a new machine identity. Any image captured after that carries this identity, causing SID conflicts and duplicate device names on every machine you deploy it to.
How many times can I run Sysprep on a golden machine?
A: Windows allows a maximum of three Sysprep rearm operations per installation. Check the remaining count with slmgr /dlv before running Sysprep. If the rearm count is 0, rebuild the golden machine from a fresh Windows installation.
Can I include domain join in the golden image?
A: No. Do not join the golden machine to a domain before capture. A domain-joined machine embeds a unique computer account in Active Directory. Every machine deployed from that image would share the same account and cause conflicts. Join the domain after deployment as a post-deployment task.
Can I deploy to multiple machines simultaneously?
A: Yes. A single active deployment task covers all machines that MotadataPXE boot during the active window. For Passcode-Based deployments, any machine that boots and enters the correct passcode during the active window receives the image. There is no per-machine limit in the task itself, but only one active deployment task can run per Poller at a time.
Can I change the passcode after creating a deployment task?
A: No. The passcode is generated by ServiceOps and cannot be manually set or changed on an existing task. If the passcode is compromised, create a new deployment task, which generates a new passcode, and expire or delete the original task.
What happens if a deployment task expires mid-campaign?
A: Machines that have already received the image are unaffected. Machines that have not yet booted and authenticated cannot start deployment after the expiry date. Edit the expiry date on the task to extend the window, or create a new task if the original has already been deleted.
Does OS Deployment support Linux or macOS targets?
A: No. OS Deployment in ServiceOps supports Windows target machines only.
Where can I find deployment history and audit records?
A: Go to Reports > OS Deployment and generate a Tabular report. This produces a row-by-row log of every deployment, filterable by image, Poller, date range, and deployment type. See Reports and KPIs for details.