OS Imaging and Deployment Software
What's New in OS Deployer 4?
New: Support for UEFI
ManageEngine OS Deployer 4 supports imaging and deployment for machines based on the UEFI architecture as well as BIOS machines. See Deploying BIOS-based systems to UEFI-based and vice versa for details of deploying BIOS-based machines to UEFI and vice versa.
New: Support for Windows 8 and Windows Server 2012
ManageEngine OS Deployer 4 supports Windows 8 (all editions except for RT edition) and Windows Server 2012 operating systems. You can install ManageEngine OS Deployer 4 on Windows 8 and Windows 2012, create and deploy master images of Windows 8 and Windows 2012 operating systems.
New: List of machines
ManageEngine OS Deployer 4 provides the Machines view. This view contains a list of all machines that you added for deployment or that have ever been deployed.
In this view, you can:
New: List of deployment tasks
Centralized deployment is performed by a deployment task. ManageEngine OS Deployer 4 provides a list of deployment tasks in the Deployment tasks view.
In this view, you can:
New: Per-deployment licensing
In addition to per-machine licensing, ManageEngine OS Deployer 4 supports per-deployment licensing.
A deployment license enables you a single successful deployment to a particular machine. A machine license enables you an unlimited number of deployments to a particular machine.
You provision machines to end users by deploying the operating system with the necessary software to a machine and then shipping the machine to the end user. Because you are planning to perform deployment to each machine only once, you want a cheaper license for the machine.
You buy a number of deployment licenses based on the number of machines that you want to provision. A deployment license becomes used only if the deployment to the corresponding machine has been successful.
New: Support for the VHD format
In addition to using its own format for an image, ManageEngine OS Deployer 4 can perform deployment from a Virtual Hard Disk (VHD) file. Such file stores contents of one or more disks. It can be created in Windows Server 2008 and Windows 7.
You saved the disks of one of your machines to a VHD file by using the Windows Backup program. Now you want to deploy that machine to other machines.
When setting up the deployment, you specify the VHD file as you would specify an image file created by ManageEngine OS Deployer 4. When performing the deployment, the software can change the settings for the machines being deployed.
New: Graphical user interface in WinPE
A bootable media based on Windows Preinstallation Environment (WinPE) now provides a graphical user interface (GUI) similar to that in a ManageEngine bootable media.
By using the GUI, you can take a master image and perform deployment.
You may want to use a WinPE-based media if the ManageEngine media cannot recognize a specific device, such as an exotic storage device.
A WinPE-based bootable media also provides a command-line utility for performing imaging and deployment.
New: Support for multiple network adapters
A machine license is bound to the machine’s network adapter (also known as network interface card, NIC).
If the machine has more than one network adapter, ManageEngine OS Deployer 4 ensures that only one license is assigned to the machine. No extra license will be consumed if you add or remove a network adapter.
To make sure that only one license is assigned to the machine, do not remove all network adapters at once.
When using the Wake-on-LAN functionality for the machine, the software sends a special packet, called the magic packet, to all network adapters of the machine.
Multicast TTL and network bandwidth throttling
Deployment configuration has a parameter that specifies time to live (TTL) for multicast packets. By using this setting, you can limit the distribution of multicast packets via gateways.
By setting the permitted bandwidth, you can limit the network usage during deployment.
New: Falling back to unicast
To make deployment to multiple machines faster, ManageEngine OS Deployer 4 multicasts the contents of the master image (the deployment stream) across the network. This way, deployment can run simultaneously on all machines even though the deployment stream is sent only once.
If the network restricts multicasting, ManageEngine OS Deployer 4 can automatically switch to the use of unicast instead.
When using unicast, ManageEngine OS Deployer 4 sends a copy of the deployment stream to each machine. This way, the network becomes more loaded, so the deployment process may take longer.
Components of ManageEngine OS Deployer 4 communicate to each other by using the Secure Sockets Layer (SSL) cryptographic protocol. Encryption starts on the first (earliest) stage of the connection attempt, so all data transferred in the next steps (including data required for client authentication) is encrypted.
After the components of ManageEngine OS Deployer 4 are installed, encrypted communication between the components is enabled automatically.
The contents of the master image are transferred unencrypted.