Header Ads


New functions and changes Windows Deployment Services (WDS) in Windows Server 2012.

WDS is part of server role that allow you to deploy Windows OS remotely. Network-based installation and configuration on new servers/desktop no need any direct media like CD, USB drive, or DVD.
To use WDS pre-requisite are DHCP, DNS, AD-DS and Preboot eXecution Environment.

Windows Server 2012
Operating systems deployed
Windows Server 2003
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Windows XP
Windows Vista SP1
Windows 7
Windows 8
Windows 8.1
Image types deployed
.wim and .vhd images are both supported similar to Windows Server 2008 R2.
.vhd images can now be managed via the WDS management snap-in in addition to the command-line.
In addition, .vhdx files (a new file format available in Windows Server 2012) are supported directly and over multicast.
The .vhdx format supports a sparse, dynamic representation of a disk, which produces a relatively small disk image file (compared to directly storing the full contents of the disk). The .vhdx format is supported for VDH boot scenarios in addition to direct application to system volumes (similar to .wim deployments).
Boot environment
Windows PE
Administration experience
MMC snap-in and WDSUTIL. Windows PowerShell cmdlets added in Windows Server 2012 R2.
Provides support for TFTP and multicasting over IPv6 and DHCPv6.
Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
Applying the install.wim file concurrently with the multicast download decreases overall deployment time, offers higher disk write throughput, and requires less space on the client system.
Reduced default block size fits within an Ethernet MTU and works on customer hardware that does not support IP fragmentation.
Driver provisioning
Extends filters for driver groups to support manufacturer Model Number and Device Groups. Driver import automatically detects and prevents duplicate driver packages from being added to the driver store.
Supports custom PXE providers.
Supports transmitting data and images by using multicasting on a stand-alone server (Transport Server). Includes a PXE provider to boot clients.
Supports custom multicast providers.

Extensible Firmware Interface (EFI)
Support x86 clients (32-bit processors) with Unified Extensible Firmware Interface (UEFI) to network boot and complete an end-to-end deployment by using WDS.
PowerShell cmdlet scripting
Supported on Windows Server 2012 R2 only
A WDS server running Windows Server 2012 R2 can be managed by using the Windows PowerShell cmdlets for WDS. By using Windows PowerShell cmdlets, you can add driver packages, add client images, enable and disable boot and install images, and perform many other common WDS tasks. For a full reference, see Windows Deployment Services in Windows PowerShell.

No comments:

Systemadminworld. Powered by Blogger.