- Windows deployment services 2012 r2 step by step pdf file
- How to deploy OS using WDS in Windows Server 2012 R2
- Utilizing Windows Deployment Services in Windows Server 2012 R2
- Windows Deployment Services Getting Started Guide for Windows Server 2012
- In this guide
- How to install and Configure WDS in Windows Server 2012 R2
- 07 – Windows Server 2012 – How to Install and Configure WDS Server
- Video Tutorial, Install WDS on Windows Server 2016
- How to Install and Configure WDS?
- Quick start checklist
Important : This guide leverages the proof of concept PoC environment configured using procedures in the following guide:.
Windows deployment services 2012 r2 step by step pdf file
Please complete all steps in the prerequisite guide before starting this guide. This guide requires about 5 hours to complete, but can require less time or more time depending on the speed of the Hyper-V host. After completing the current guide, also see the companion guide:.
This guide uses the Hyper-V server role. If you do not complete all steps in a single session, consider using checkpoints and saved states to pause, resume, or restart your work.
Topics and procedures in this guide are summarized in the following table. An estimate of the time required to complete each procedure is also provided.
Time required to complete procedures will vary depending on the resources available to the Hyper-V host and assigned to VMs, such as processor speed, memory allocation, disk speed, and network speed.
As of the writing of this guide, the latest version of MDT was The current version is the ADK for Windows 10, version Installation might require several minutes to acquire all components. The first step in creating a deployment share is to mount this file on SRV1. To open the deployment workbench, click Start , type deployment , and then click Deployment Workbench.
To enable quick access to the application, right-click Deployment Workbench on the taskbar and then click Pin this program to the taskbar.
How to deploy OS using WDS in Windows Server 2012 R2
Right-click the Operating Systems node, and then click New Folder. Name the new folder Windows Complete the wizard using default values and click Finish. Right-click the Windows 10 folder created in the previous step, and then click Import Operating System.
For purposes of this test lab, we will only add the prerequisite. NET Framework feature. Commerical applications ex: Microsoft Office will not be added to the deployment share. For information about adding applications, see the Add applications section of the Create a Windows 10 reference image topic in the TechNet library.
Utilizing Windows Deployment Services in Windows Server 2012 R2
The next step is to create a task sequence to reference the operating system that was imported. Use the following settings for the New Task Sequence Wizard:. To edit the task sequence, double-click Windows 10 Enterprise x64 Default Image that was created in the previous step. Click the Task Sequence tab. Click another location in the window to see the name change.
Under Select the roles and features that should be installed , select. NET Framework 3.
Windows Deployment Services Getting Started Guide for Windows Server 2012
NET 2. Enable Windows Update in the task sequence by clicking the Windows Update Post-Application Installation step, clicking the Options tab, and clearing the Disable this step checkbox.
Note: Since we are not installing applications in this test lab, there is no need to enable the Windows Update Pre-Application Installation step. However, you should enable this step if you are also installing applications.
The next step is to configure the MDT deployment share rules. Click Apply and then click Edit Bootstrap. Replace the contents of the Bootstrap. The update process will take 5 to 10 minutes. When it has completed, click Finish.
Accept the default values on the Capture Image page, and click Next. Operating system installation will complete after 5 to 10 minutes, and then the VM will reboot automatically.
In this guide
Allow the system to boot normally do not press a key. The process is fully automated. Additional system restarts will occur to complete updating and preparing the operating system. Setup will complete the following procedures:. This step requires from 30 minutes to 2 hours, depending on the speed of the Hyper-V host.
How to install and Configure WDS in Windows Server 2012 R2
After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep. Use the following values in the New Deployment Share Wizard:. Click Next , verify the new deployment share was added successfully, then click Finish. Name the new folder Windows 10 and complete the wizard using default values. On the Destination page, accept the default Destination directory name of REFW10X , click Next twice, wait for the import process to complete, and then click Finish.
See the following example:. Right-click the Windows 10 folder created in the previous step, and then click New Task Sequence.
Click the Rules tab and replace the rules with the following text don't click OK yet :.
07 – Windows Server 2012 – How to Install and Configure WDS Server
In this example a MachineObjectOU entry is not provided. Normally this entry describes the specific OU where new client computer objects are created in Active Directory. However, for the purposes of this test lab clients are added to the default computers OU, which requires that this parameter be unspecified.
If desired, edit the follow line to include or exclude other users when migrating settings. For example, to migrate all users on the computer, replace this line with the following:.
For more information, see ScanState Syntax.
Video Tutorial, Install WDS on Windows Server 2016
Use the default options for the Update Deployment Share Wizard. The update process requires 5 to 10 minutes to complete.
On the Monitoring tab, select the Enable monitoring for this deployment share checkbox, and then click OK. Click Finish to complete adding a boot image.
This is just an artifact of the lab environment. In a typical deployment environment WDS would not be installed on the default gateway. Note : Do not disable the internal network interface. Dynamic memory is configured on the VM to conserve resources. However, this can cause memory allocation to be reduced past what is required to install an operating system. If this happens, reset the VM and begin the OS installation task sequence immediately.
This ensures the VM memory allocation is not decreased too much while it is idle. This is needed so the client can use Windows Update after operating system installation is complete. To re-enable the external network interface, open an elevated Windows PowerShell prompt on SRV1 and type the following command:.
Right-click Monitoring and click Refresh if no data is displayed. OS installation requires about 10 minutes. When the installation is complete, the system will reboot automatically, configure devices, and install updates, requiring another minutes. When the new client computer is finished updating, click Finish. You will be automatically signed in to the local computer as administrator. This completes the demonstration of how to deploy a reference image to the network.
To conserve resources, turn off the PC2 VM before starting the next section. This section will demonstrate how to export user data from an existing client computer, wipe the computer, install a new operating system, and then restore user data and settings.
The scenario will use PC1, a computer that was cloned from a physical device to a VM, as described in Step by step guide: Deploy Windows 10 in a test lab. Switch back to the Hyper-V host and create a checkpoint for the PC1 VM so that it can easily be reverted to its current state for troubleshooting purposes and to perform additional scenarios.
Checkpoints are also known as snapshots. You must sign in with this account so that you have access to the deployment share.
How to Install and Configure WDS?
Note : Litetouch. You can review the progress of installation on SRV1 by clicking on the Monitoring node in the deployment workbench. When OS installation is complete, the computer will restart, set up devices, and configure settings.
Create another checkpoint for the PC1 VM so that you can review results of the computer refresh later. To create a checkpoint, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:. Restore the PC1 VM to it's previous state in preparation for the replace procedure.
Quick start checklist
To restore a checkpoint, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:. Right-click the Other folder and then click New Task Sequence. Use the following values in the wizard:. Accept defaults for the rest of the wizard and then click Finish. The replace task sequence will skip OS selection and settings.
Open the new task sequence that was created and review it. Note the type of capture and backup tasks that are present.
Click OK when you are finished reviewing the task sequence.