×![]()
×
×![]()
×
×
Frequently Asked Questions | OS Deployer
This page provides answers to frequently asked questions (FAQs) related to OS Deployer.
General
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.
For the complete list of ports used for OS Deployment refer to the this page.
OS Deployment
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.
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.
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.
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.
- 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.
Windows 10/Windows 11 Imaging
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:
- Enter BIOS setup using F2.
- Navigate to the Boot Menu.
- Uncheck Boot Network Devices Last.
- Enable UEFI PXE & iSCSI.
- Select Ethernet1 Boot or Ethernet2 Boot.
- Press F12 during POST to boot from LAN.
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:
The following Windows Server operating systems can be booted using the Windows bootable USB:
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
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 x86 and 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.
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.