×
×
×
×

Frequently Asked Questions | OS Deployer

Last Updated On 03 Mar 2026 |
35 minutes read |

This page provides answers to frequently asked questions (FAQs) related to OS Deployer.

General

What are the Operating Systems supported by OS Deployer?
OS Deployer supports a wide range of Windows desktop and server operating systems. For the complete list of supported operating systems, refer to the System Requirements page.
What are the ports used by OS Deployer?
For the complete list of ports used for OS Deployment refer to the this page.

OS Deployment

Does OS Deployment support Windows Surface Pro?
Yes, OS imaging and deployment is supported on Windows Surface Pro machines.
Why is WinPE media required?
WinPE media is required to boot the machines in to Windows Pre-installation environment to perform deployment and offline imaging.
How is OS Deployment Licensed?
OS Deployment supports machine based licensing, that is the number of workstation and server machines on which you want to perform deployment. Here the licenses are tied to the machine's MAC address and once you purchase a license for a machine, you can perform any number of deployments on that machine. Depending on the operating system, you need to have either a workstation or a server license. E.g., to perform deployment on 100 workstation machines, you need to purchase 100 workstation licenses.
We have Dell and HP machines in our organisation. Does OS deployment support deployment of image on dissimilar hardware?
Yes, you can deploy images on dissimilar hardware as hardware-independent imaging is supported in OS deployment.
How to delete a driver repository?
A driver repository is used to store the drivers which are collected during image creation process. You can delete the repository from the product console itself. However, the repository will get deleted only in the UI and the drivers in the network share has to be manually deleted by the user. It is always required to have at least one configured driver repository to store the automatically collected drivers.
When will the driver repositories get synced?
All driver repositories will get synced every 4 hours.
Where will the applications be replicated for remote office deployments?
The applications required for remote office deployment will be replicated automatically to the Endpoint Central Distribution Server installed location (<DesktopCentral_DistributionServer installed location>\replication\osdrepository) in the Distribution Server computer.
Where will the drivers be replicated for remote office deployments?
The drivers required for remote office deployment will be replicated automatically to the driver repository available in the remote office.
How to copy an image from one image repository to another?
Currently, the image has to be manually copied from one repository to another. After copying the image to a new repository, you have to modify the repository path in the image details. To modify the repository, select the image and view the image details. Here, near the image repository, select the edit icon to modify the repository path.
How does OS Deployer activate the Windows license?
  • OEM license: If the Windows OS version of the image is the same as the OEM license, then the license will be automatically activated.
  • Volume-based license: Let us assume you've created an image by imaging a machine with a volume-based license. Depending on the availability of the license, if you deploy it to another machine the license will be automatically activated.
How to resolve insufficient space for creating image?

To resolve the “Insufficient space for creating image” issue, please increase the available free space in the existing image repository. Alternatively, you can create a new image repository at a different location with sufficient free space and use that repository to create the new image.

How to resolve the error "The specified path cannot be found" during USMT backup?
  • Navigate to the server installed directory: Server Installed Directory\webapps\DesktopCentral\agent
  • Locate the zip file named "USMTComponents.zip". If the size of the file is 1kb, it indicates that its empty.
  • Delete the USMTComponents.zip file and initiate USMT again. The zip must be recreated with required files.
Note
Make sure the Windows ADK is installed properly on the server machine.
How to resolve Inaccessible Boot device?
  • Download the target machine's model specific rapid storage driver. Extract the driver files and add them to your driver repository.
  • Once drivers were added, do a scan for the driver repository and try deployment.
  • Alternatively access the BIOS settings of one of the target machines affected by the BSOD.
  • Change the SATA configuration to AHCI or AHCI to RAID mode vice versa and attempt to boot the machine into Windows.
  • Verify whether the system successfully boots into Windows.

If the issue persists, kindly contact support.

Windows 10/Windows 11 Imaging

What is Windows 10/Windows 11 image?
A Windows 10/Windows 11 image file is an exact copy of a hard drive that contains the Windows 10/Windows 11 operating system, executables, drivers, and other files.
What does imaging Windows 10/Windows 11 mean?
Windows 10/Windows 11 imaging is the process of creating an image of a Windows 10/Windows 11 computer that includes the OS, files, settings, and the required applications.
How do I create a Windows 10/Windows 11 image?
Prepare a machine with Windows 10/Windows 11 OS and the data to be included in the image. You can then image the prepared machine using a Windows 10/Windows 11 imaging tool like OS Deployer.
Can I add relevant applications to my Windows 10/Windows 11 image before deployment?
Yes, using the Add Applications feature under the deployment template, you can include all the required applications in your Windows 10/Windows 11 image. These applications will be automatically installed after all post-deployment activities are completed.
Can I create a Windows 10/Windows 11 image offline?
Yes, you can create an image of a Windows 10 or Windows 11 computer even when it is shut down using the offline image creation process.
Can I download Windows 10/Windows 11 ISO?
Yes, using OS Deployer, you can download Windows 10 or Windows 11 ISO files and deploy them through USB, CD, DVD, or virtual machines.

PXE Boot Server

What does PXE boot stand for?
PXE boot stands for Preboot Execution Environment — a network booting process using a DHCP or TFTP server that enables computers to boot via network-based software instead of local drives.
What does PXE mean?
PXE (Preboot Execution Environment) is a client-server interface that allows computers to boot over a network.
How to ensure clients from other subnets can boot using PXE?
If the OS Deployer server, DHCP server, and client are on the same network, PXE booting can be extended to other subnets using DHCP relay or IP helper configurations.
How to PXE boot computers over LAN?
Configure DHCP Option 66 with the OS Deployer server IP and Option 67 with the appropriate boot file (Legacy or UEFI). Then boot clients through the LAN.
What is a PXE server?
The PXE server in OS Deployer operates as a Windows service alongside the Central Server, enabling OS image deployment across networks.
What is PXE boot in Windows?
PXE boot in Windows allows network-based OS deployment across multiple devices simultaneously using a DHCP and TFTP-based process.
How do I run a PXE boot?
Configure your DHCP server with the appropriate options and initiate boot from LAN on target devices. PXE will automatically fetch OS deployment data.
How to enable PXE on a server?
To enable PXE on an Intel NUC:

  1. Enter BIOS setup using F2.
  2. Navigate to the Boot Menu.
  3. Uncheck Boot Network Devices Last.
  4. Enable UEFI PXE & iSCSI.
  5. Select Ethernet1 Boot or Ethernet2 Boot.
  6. Press F12 during POST to boot from LAN.
Refer to Intel’s official guide for more details.

Boot Windows via USB Media

Can we boot Windows from USB using OS Deployer?
Workstation OS
The following operating systems are supported for booting Windows from USB using OS Deployer:
  • Windows 10
  • Windows 8.1
  • Windows 8
  • Windows 7
  • Windows Vista
  • Windows XP
Server OS
The following Windows Server operating systems can be booted using the Windows bootable USB:
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2
  • Windows Server 2008
  • Windows Server 2003 R2
  • Windows Server 2003
Why is WinPE media required?
WinPE media is required to boot the machines into the Windows Pre-installation Environment to perform deployment and offline imaging.
Which versions of WinPE media are supported for OS Imaging and Deployment?
  • Windows PE 10.0 Media - Windows 10, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012
  • Windows PE 5.0 Media - Windows 10, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012
  • Windows PE 4.0 Media - Windows 10, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008
  • Windows PE 3.0 Media - Windows 7, Windows Server 2008 R2, Windows Vista, and Windows Server 2008
  • Windows PE 2.0 Media - Windows Vista, Windows Server 2008, Windows XP, Windows Server 2003
What are the WinPE architectures supported by OS Deployer?
OS Deployer supports only x64 WinPE architectures.
What are the supported operating systems?
OS Deployer supports creating bootable USBs from ISO for all client-based and server-based Windows operating systems, including Windows XP through Windows 11.
Can I automate WinPE installation while booting from ISO?
Yes. OS Deployer automatically downloads and installs the WinPE tool on its server. You can include WinPE while creating the ISO bootable media, which can then be converted to USB.
What drivers are included while booting from ISO?
The ISO bootable media includes essential network, hard disk, keyboard, and mouse drivers.
Does OS Deployer support UEFI boot?
Yes. OS Deployer supports both Legacy and UEFI boot modes.
Can I boot Windows machines using USB?
Yes. OS Deployer supports booting Windows computers using USB bootable media as well as PXE boot.
Can I extract Windows ISO to USB?
Yes. You can extract the Windows ISO to a USB or CD/DVD depending on your requirements.

Boot Windows via ISO Media

What are the supported operating systems?
OS Deployer supports creating bootable USBs from ISO for all client-based and server-based Windows operating systems, including Windows XP through Windows 11.
Can I automate WinPE installation while booting from ISO?
Yes. OS Deployer automatically downloads and installs the WinPE tool on its server. You can include WinPE while creating the ISO bootable media, which can then be converted to USB.
What drivers are included while booting from ISO?
The ISO bootable media includes essential network, hard disk, keyboard, and mouse drivers.
Does OS Deployer support UEFI boot?
Yes. OS Deployer supports both Legacy and UEFI boot modes.
Can I boot Windows machines using USB?
Yes. OS Deployer supports booting Windows computers using USB bootable media as well as PXE boot.
Can I extract Windows ISO to USB?
Yes. You can extract the Windows ISO to a USB or CD/DVD depending on your requirements.
How do I transfer Windows ISO to USB?
You can use tools like Rufus, UltraISO, or YUMI to burn the ISO file to a USB drive of your choice.
Can I automate the booting process?
Yes. Using OS Deployer’s Zero-touch deployment, you can completely automate the booting and image deployment process, allowing multiple computers to be deployed remotely.

Windows ISO Download and Creation

Can I get Windows 10 ISO for free?
Yes, Microsoft allows free ISO downloads for licensed users from their official website.
Is Windows 10 ISO bootable?
Yes. The ISO file can be mounted on a USB or DVD to create installation media. For mass deployment, explore OS Deployer’s capabilities.
How do I download Windows 10 ISO 64-bit?
Download the Media Creation Tool from Microsoft’s website. Choose Create installation media to generate a 64-bit ISO file. To learn more about downloading Windows 10 ISO file and creating installation media, refer to this document.
How many GB is Windows 10 64-bit ISO?
The Windows 10 Enterprise 64-bit ISO is approximately 5.2 GB, and the Media Creation Tool is about 18.6 MB.
Is Windows 11 ISO free?
Yes, download it for free from the Microsoft website.

Microsoft Windows Deployment Toolkit

What is Microsoft Deployment Toolkit (MDT) used for?
The Windows deployment tool is used for automating the deployment of Windows-based operating systems starting from Windows 7. This includes both client-based and server-based operating systems.
Is Microsoft Deployment Toolkit free?
Yes, the Windows deployment toolkit is a free tool developed by Microsoft. The Microsoft Deployment Toolkit (MDT) can be downloaded from the Microsoft official website.
What is the difference between Microsoft Deployment Toolkit (MDT) and SCCM?
SCCM (now officially known as Microsoft Configuration Manager) is an endpoint management tool that assists users in app management, patch management, analytics, OS deployment, etc. Microsoft Deployment Toolkit is primarily an OS deployment solution that automates the deployment of Windows operating systems.
How do I install Microsoft Deployment Toolkit?
Using OS Deployer, you can completely automate the installation process of the Windows Deployment Toolkit. You can also manually download and install the Microsoft deployment tool if necessary.
How can I leverage MDT using OS Deployer?
OS Deployer accelerates the deployment process by automating the download, installation, and deployment of Microsoft deployment tool that includes Windows Assessment and Deployment Kit (ADK) and Windows Pre-installation Environment (Windows PE) tool. You can also leverage the Assessment and Deployment Kit by manually downloading the deployment tool.

Service Tag Based Target Identification

How will this update affect my existing OSD licenses?

Your existing OSD licenses are MAC Address-based. After this update, the system will automatically create a Service Tag association for each MAC license using details from the last successful deployment. No manual action is required — existing licenses remain valid.

Will my machines be identified by Service Tag going forward?

Yes. Going forward, each license will be identified by the deployed machine's Service Tag. MAC Address will only be used in cases where the Service Tag is found to be invalid.

How does this update change how I add deployment targets?

Previously, deployment targets could only be added using a MAC Address. This update introduces a field that accepts either a MAC Address or a Service Tag, giving you more flexibility when configuring deployment targets.

Will my existing deployment task targets still work?

Yes. Existing deployment task targets are not modified by this update and will continue to function as before. You do not need to reconfigure them.

How does this update affect target configuration in Standalone Tasks?

Previously, MAC Address was mandatory when adding a target in a Standalone Task, while the Service Tag was optional. With this update, the form now accepts either a Service Tag or a MAC Address — MAC Address is no longer mandatory. We recommend providing the Service Tag as the primary target identifier, since modern machines often do not have a built-in Ethernet MAC address.

What happens to existing Standalone Task targets after the update?

Existing targets will remain in place and continue to work. However, the behavior depends on how the target was originally configured:

  • Target configured with a Service Tag: After the update, the Service Tag will be prioritized and only the Service Tag will be displayed for that target.
  • Target configured without a Service Tag: No change occurs. The MAC Address-based target will still be shown and function as intended.
How does this update affect the Computer Specific Settings form?

Previously, MAC Address was mandatory when adding computer settings, while the Service Tag was optional. With this update, the form now accepts either a Service Tag or a MAC Address — MAC Address is no longer mandatory.

We recommend providing the Service Tag, as modern machines often do not have a built-in Ethernet MAC address.

Will my existing Computer Specific Settings still work after the update?

Yes. Existing computer settings will remain in place and continue to work. However, the behavior depends on how the setting was originally configured:

  • Computer Setting configured with a Service Tag: After the update, the Service Tag will be prioritized over the MAC Address and only the Service Tag will be shown for that Computer Setting.
  • Computer Setting configured without a Service Tag: No change occurs. The MAC Address-based Computer Setting will still be shown and function as intended.
How does this update affect the Deployment Status view?

Previously, the hyperlink for accessing deployment details was only available for MAC Address entries. After this update, the hyperlink will also be shown for Serial Number (Service Tag) entries, making it easier to navigate to deployment details for machines identified by Service Tag.

Note
If you had previously personalized the column layout in the Deployment Status view, this update may have repositioned the MAC Address and Service Tag columns to the end of the list. Use the column selector to rearrange them to your preferred order.
How does this update affect licensing in the UEM or Security edition?

In the UEM/Security edition, OSD licensing is integrated with the Endpoint Central. Previously, the overlap between OSD and EC was determined by MAC addresses, which frequently caused licensing inconsistencies when external network adapters were linked to multiple managed agents.

This issue has been resolved by switching to Service Tag verification. A machine that is both Deployed and Managed will now be counted as a single license, regardless of its MAC address associations.

What happens if the Service Tag is invalid in a UEM/Security environment?

If the Service Tag is found to be invalid, the system will automatically revert to MAC address-based verification to ensure the machine is still accounted for correctly.

Mail Server Settings

Which mail servers support OAuth?
OAuth authentication is tested with Microsoft Outlook (Office365) and Gmail (Gsuite).
Can I configure OAuth for an existing mail account?
Yes, OAuth authentication can be configured for an existing mail account.
Why should I switch to OAuth2.0?
Google and Microsoft deprecated basic authentication for mail servers on May 30, 2022, and October 1, 2022, respectively.To ensure secure and uninterrupted mail communication, it is recommended to use OAuth authentication.
What is a Redirect URL, and where should I configure it?
A Redirect URL (Reply URL) is where the Authorization Server sends response data. Copy and paste the Redirect URL into the application details in the Authorization Server settings.
Why do I get an error stating "Redirect URL invalid/mismatch" when saving settings?
Ensure that the Redirect URL is added to the authorization server’s list of allowed Redirect URLs and that the settings are saved correctly.
What happens when my access token expires?
When the access token expires, a new token is automatically generated using the refresh token.
Was this document helpful?
Yes
No