Deploy Windows 8 Enterprise using Lite Touch Deployment Method

System Requirements:

Prepare Environment:

The following systems are already available in your organization.

Purpose NetBIOS Name Operating Systems
Domain Controller DC Windows Server 2012
WDS Server PrototypeSRV1 Windows Server 2012
Volume Activation Server PrototypeSRV2 Windows Server 2012
Client Client1 Windows 8

Download and copy desired applications such as Office 2013, Adobe Reader into a folder named “Staging Folder” in E: drive of WDS Server. Download Office 2013 Administrative Template and copy the content into x86 and x64 folders of office 2013.

Step1 : Install Volume Licensing Server PrototypeSRV2 and configure Active Directory Activation

Log on PrototypeSRV2 as an Administrator. Open Server Manager, Click Manage, Click Add Roles and Features, Click Next, Click Next, Select Server PrototypeSRV2, Click Next

VL Role

Select Volume Activation Services, Click Next, Follow the Screen. From the Server Manager, Click All Servers, Right Click on PrototypeSRV2,  Click Volume Activation Tools

VL Role2

On the Introduction Page, Click Next, Click Active Directory Based Activation, Provide Credentials, Click Next

VL Role3

On the Product Key Management Page, Type the KMS Product Key. KMS Key is available in Microsoft volume licensing web site. Log on the volume licensing site or contact Microsoft reseller/partner to obtain KMS Key.

VL Role4

Click Next to continue. Follow the screen to finish volume activation of Windows 8.

Step2: Download and install MDT 2012 and Windows 7 AIK on WDS Server

1

Step3: Configure Deployment Share in MDT for Windows 8 Enterprise

Hover mouse on right hand side top corner, Click Search, Type Deployment, Click Deployment Assistance,  Right Click MDT Deployment Share, Click New Deployment Share, Type the Location of Deployment Share where you want to store application, drivers and OS. Click Next, Click Next, Click Next

2

3

4

Check all the boxes as shown below, Click Next, Click Next, Click Finish.

5

6

7

8

Step4: Import Applications into Deployment Share

Right Click on Applications, Click Import new Applications. Check Application with source files, Click Next

9

Type application details shown below, Click Next

10

Browse and Point the location of source files, Click Next, Click Next

11

12

Type setup.exe, Click Next, Click Next, Click Finish.

13

14

15

Now expand Applications, Right Click on Office 2013, Click Property, Click Office Products Tab, Click Office Customization Tool, From Office Customization Tools, Provide Office CD Key, Suppress display, configure outlook profile. Click File, Click Save, Save the file into E:DeploymentShareApplicationsMicrosoft Office 2013Updatecustom.msp locations. Close Office Customization tools, Click Apply, Click Ok.

21

Follow the above steps, import Adobe Acrobat Reader, on the command details type msiexec /i AcroPro.msi /qn if you would like install Acrobat Pro otherwise AdbeRdr1000_en_US.msi

Step5: Import Windows 8 Enterprise Operating Systems into MDT

Right Click on Operating Systems, Click Import Operating System, Select Full set of Source Files, Click Next

16

On the Source Page, Select the Source Directory of Windows 8 Enterprise, Click Next, Click Next, Click Finish.

17

47

19

20

Step6: Import Out of Box Drivers into MDT 2012

Right Click Out-of_box Drivers, Click Import Drivers, Select the source of drivers, Click Next, Click Finish.

image

Step7: Create Standard Deployment Tasks

Right Click Task Sequence, Click New Task Sequence, Type the Name of the task sequence, Click Next

22

On the Select Template Page, Select Standard Client Task Sequence, Click Next

23

Select Windows 8 Enterprise Version, Click Next

image

On the Specify Product Key Page, Check Do not specify product key at this time, Click Next

image

On the OS Settings, Type Full Name, Organization, IE Home Page, Click Next

26

Type Local Admin Password Click Next

27

Click Finish.

28

Step8: Update Deployment Share

image

Right Click on MDT Deployment Share, Click Update Deployment Share, Click Next, Click Finish.

29

30

Step9: Import Lite Touch Boot Image into WDS Server

Click Server Manager, Click WDS, Right Click on WDS Server, Click Windows Deployment Services Management Console

image

Right Click on Boot Images, Click Add Boot Images,

image

Select Lite TouchPE_X64.wim image from E:DeploymentShareBoot, Click Next, Click Finish.

31

Step10: Create a Reference Computer

Boot a reference computer using F12 network boot. Select Lite Touch Windows PE boot image, press enter

44

Click Run the Deployment Wizard.

32

On the Deployment Share Page, Type \prototypesrv1deploymentshare$, Click Next

33

Provide Domain Credentials, Click Ok

34

Select the Task, Click Next

35

Select Join a Workgroup, Click Next, Follow the screen

image

37

38

39

Select the Apps you want to install, Click Next

40

Provide Local Admin Password, Click Next

41

Click Capture an image of this reference computer, Click Next

image

Click Begin.

42

43

45

image

image

Step11: Create an Answer File for Win8 Image for future

Deployment Share, Click Operating Systems, Right Click on Windows 8 Enterprise Image, Click Property, Click OS Info Tab, Click Edit Unattend.xml

image

Once the process complete, unattended.xml will be opened using Windows AIK, Now modify the Edit Unattend.xml file, provide domain details, Click File, Click Save as, Save the file as Win8EntUnattend.xml into E:RemoteInstallWdsClientUnattend folder.

Step12: Import Captured Image into WDS Server

Open WDS Server Console, Right Install Image, Click Install new Image, Select the image you captured using lite touch from E:DeploymentShareCapturesWin8Ent.wim file. Click Next, Click Finish.

image

Right Click on Win8Ent Image, Click Property, Check Allow image to install unattend mode, browse and select the file win8entunattend.xml from E:RemoteInstallWdsClientUnattend folder. Click Apply, Click Ok.

image

Step13: Deploy the Image to Target Computer.

Open WDS Server, Click Boot Image, Click Add Boot Image, Browse Windows 8 Ent DVD, Select Boot.wim file from Sources folder, Click Next, Type the name of the image as Deploy Image (x64), Click Next, Click Finish.

image

Boot a target computer using F12, Select Deploy Image X64, Press Enter, Select Windows 8 Ent Image, Follow the screen.

44

Now Lite Touch Deployment is completed successfully.

Windows Server 2012 Step by Step Book

Windows Server 2012 Step by Step

This is my first book published on December 2 2012. The following is the chapters available in detailed in the book titled “Windows Server 2012 Step by Step”

Chapter 1: Introduction to windows server 2012

Chapter 2: Installing and navigating windows server 2012

Chapter 3: Server Roles and Features

Chapter 4: Active Directory Domain Services

Chapter 5: Active Directory Certificate Services

Chapter 6: Active Directory Federation Services

Chapter 7: Active Directory Rights Management Services

Chapter 8: Networking Infrastructure

Chapter 9: Failover Clustering

Chapter 10: Remote Desktop Services

Chapter 11: Security, Protection and protection

Chapter 12: Building Private Cloud with Hyper-V

Chapter 13: Web Server (IIS)

Chapter 14: BranchCache Server configuration

Chapter 15: Routing and Remote Access Server Configuration

Chapter 16: Windows Deployment Services

Chapter 17: Windows Server Update Services

Chapter 18: Volume Activation

Chapter 19: File and Storage Services

Chapter 20: Print and Document Services

Chapter 21: Network Policy and Access Server

Chapter 22: Group Policy Object

Chapter 23: Migrating from Server 2008 to Server 2012

Chapter 24: Supporting Windows Server 2012

 

How to set computer naming policy in Windows Deployment Services (WDS)

In old remote installation services, you have the options to customize computer name or select automatic installation while running RIS on a client. similarly, new Windows deployment services has the option for you to set naming policy in Windows Deployment Services server. In WDS server, by default naming policy set to %Username%# that means WDS will create computer name using username who logged on when running remote installation process and # is the number 1,2,3..up to 999 will be added after username. To Set naming policy and  default organisational unit in Active Directory. Log on to WDS server using domain admin credentials.

Start menu>Administrative Tools>Windows Deployment Services>Expand Servers>Right click on WDS server>Property>Directory Services Tab

Set Automated name add the string you want and browse and point the OU in Active Directory you want to place computers.

01 

03   

To set custom name and approval process for WDS client. Click PXE Response settings Tab. Check For unknown clients, notify administrator and respond after approval then apply and ok.

Warning! Apply this may result all unknown computers and manually added computers (computer didn’t use WDS for windows installation) in Active Directory will auto boot up to WDS services without pressing F12.

  02

Now boot an unknown client i.e. new client in the network. Client will  automatically boot using WDS. Log on to WDS server and go to pending devices as shown here. Select and right click the computer that’s waiting for approval, click name and approve. Type Name and Approve this pending device. If you want to place this computer in a specific OU in Active Directory then click location and place in that OU.

2 3

4

Pre-staging an approval of a client:

  1. To open Active Directory Users and Computers

  2. In the console tree, right-click the organizational unit that will contain the new client computer.

  3. Click New, and then click Computer.

  4. Type the client computer name, click Next, and then click This is a managed computer.

  5. In the text entry field, type the client computer’s globally unique identifier (GUID/UUID) and then click Next.

  6. Click one of the following options to specify which server or servers will support this client computer. Check The following remote installation server and Type WDS server’s FQDN

  7. Click Next, and then click Finish.

Important! The term GUID usually refers to Microsoft‘s implementation of the Universally Unique Identifier (UUID) standard. A UUID is a 16-byte (128-bit) number. The number of theoretically possible UUIDs is therefore about 3 × 1038. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens). For example:

24bdba81-4a3f-11cb-8abf-bed9eae25fcf

Screen Shots for further help:

 5 6 7

Note: Typed without ‘-‘ (hyphen)

 8

9

Now this re-image this computer by pressing F12 while booting.

To find UUID:

1. Log on to Windows XP Machine. Open Command Prompt>Change directory to  C:\Windows\system32\wbem  Type wbemtest.exe hit enter.
2. Click Connect. Change root\default to root\cimv2 >hit connect.
3. Click Enum Classes button>choose Recursive>Click ok.
4. A Query Result will appear, scroll down, select Win32_ComputerSystemProduct then Double click it then Object editor for win32 will appear
5. In the Properties box scroll down, choose UUID and click Instances button. In the Query Result, Select Win32_ComputerSystemsProduct double click on it and another Object Editor will appear and  it contains desired UUID for the computer.

It’s painful process but you may find UUID in some computer and laptop’s bios. For example, on IBM R61 laptop I got UUID in bois. 

Relevant Article on Windows Deployment Services 

Share this on  Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

Windows Deployment Services:How to resolve “uploading image to WDS Server The System Cannot find the file specified”

I was stuck for hours and scratching my head to find out a solution of this problem. I googled heaps but outcome is zero. Here, I will show you how to resolve this issue.

Issue: When you uploading image in windows deployment services, it start uploading however in few seconds it stops with error “ The System Cannot find the file specified”

Why it happens? This is an weird problem I have ever seen. What it says in error practically not that case. You will not find any event log for this error in event viewer. It happens for WDS mixed-mode  server. It shows that error for several reasons.

Disk Space in system partition and drive:Remoteinstall aren’t enough

Disk space for TEMP /TMP folder in %userprofile%usernameLocal SettingsTEMP aren’t enough

Mixed-Mode WDS not configured properly

Resolution:

As I said this is a weird error though I have enough space in both partition still I got that error.  However, I did followings to resolve my problem.

Must have more then enough space in C: drive and Remoteinstall partition. Remember Microsoft Windows needs extra disk space for Pagefile, shared memory for RAM,  temp folder and on top of that disk space for WDS WIM file in TEMP folder of system partition. Also you need enough disk space for Drive:remoteinstalltemp folder.

Empty temp folder as shown below

1

Check Temp folder configuration. System Property>Environment variables. You must point TEMP folder to %Windir%Documents and Settings%USERPROFILE%Local SettingsTEMP.

2 3

You must see these four .bcd files in remoteinstalltemp folder after you add boot.wim and winpe.wim image otherwise WDS will not work properly. DO NOT DELETE THESE FILES.

4

Type WDSUTIL /set-server /DefaultX86X64ImageType:both on command prompt to set WDS boot and read x64 and x86 format image.

Add separate image group for the image you are loading.

5  

Install Windows 7 AIK in WDS Server and copy drvstore.dll , cmiv2.dll and xmllite.dll files from %windir%Program filesWindows AIKToolsServicing to %windir%system32

Patch up WDS server from http://update.microsoft.com site or WSUS

Now reboot server and you are laughing.

Windows Deployment Services:How to resolve “uploading image to WDS Server The System Cannot find the file specified”

I was stuck for hours and scratching my head to find out a solution of this problem. I googled heaps but outcome is zero. Here, I will show you how to resolve this issue.

Issue: When you uploading image in windows deployment services, it start uploading however in few seconds it stops with error “ The System Cannot find the file specified”

Why it happens? This is an weird problem I have ever seen. What it says in error practically not that case. You will not find any event log for this error in event viewer. It happens for WDS mixed-mode  server. It shows that error for several reasons.

Disk Space in system partition and drive:\Remoteinstall aren’t enough

Disk space for TEMP /TMP folder in %userprofile%\username\Local Settings\TEMP aren’t enough

Mixed-Mode WDS not configured properly

Resolution:

As I said this is a weird error though I have enough space in both partition still I got that error.  However, I did followings to resolve my problem.

Must have more then enough space in C:\ drive and Remoteinstall partition. Remember Microsoft Windows needs extra disk space for Pagefile, shared memory for RAM,  temp folder and on top of that disk space for WDS WIM file in TEMP folder of system partition. Also you need enough disk space for Drive:\remoteinstall\temp folder.

Empty temp folder as shown below

1

Check Temp folder configuration. System Property>Environment variables. You must point TEMP folder to %Windir%\Documents and Settings\%USERPROFILE%\Local Settings\TEMP.

2 3

You must see these four .bcd files in remoteinstall\temp folder after you add boot.wim and winpe.wim image otherwise WDS will not work properly. DO NOT DELETE THESE FILES.

4

Type WDSUTIL /set-server /DefaultX86X64ImageType:both on command prompt to set WDS boot and read x64 and x86 format image.

Add separate image group for the image you are loading.

5  

Install Windows 7 AIK in WDS Server and copy drvstore.dll , cmiv2.dll and xmllite.dll files from %windir%\Program files\Windows AIK\Tools\Servicing to %windir%\system32

Patch up WDS server from http://update.microsoft.com site or WSUS

Now reboot server and you are laughing.

Riprep Image to WDS WIM conversion error

I found an error while converting  Riprep Image to WDS WIM file. If you are having same trouble doing conversion. Here is a little solutions for you.

Error:

An error occurred while trying to execute the command.
Error Code: 0xC103014B
Error Description: Wdsmgmt could not load a required library.  If this is a version of Windows prior to Vista, please install the OPK/WAIK toolkit and ensure that drvstore.dll and cmiv2.dll are in the path.

Why it happens? WDSUTIL looks for drvstore.dll , cmiv2.dll and xmllite.dll file in %windir%\system32 folder. When it fails to locate these files it gives an error code:0xC103014B even though Windows AIK is installed in WDS server.

Resolution:

You must install Windows AIK and Copy drvstore.dll , cmiv2.dll and xmllite.dll files from %windir%\Program files\Windows AIK\Tools\Servicing to %windir%\system32

Now open command prompt and run  wdsutil /convert-RiprepImage /filepath:SourcePath\riprep.sif /destinationimage /filepath:destination path\FileName.wim 

Screenshot: Before copying those files to %windir%\system32

1

Screenshot: after resolving issue

2

Windows Deployment Services: Create and deploy multicast images

I would like to explain a bit about IP Multicast before I start with WDS multicast image distribution because not all the organisation have existing multicast infrastructure. Still, I reckon it would be worthy to know bits and pieces of a technology while working on it.  So what is IP Multicast? Multicast is a technique for one-to-many communication over an IP infrastructure in a network. It scales to a larger receiver population by not requiring prior knowledge of whom or how many receivers there are. Multicast uses network infrastructure efficiently by requiring the source to send a packet only once, even if it needs to be delivered to a large number of receivers resulting bandwidth savings. The nodes in the network take care of replicating the packet to reach multiple receivers only when necessary. The most common low-level protocol to use multicast addressing is User Datagram Protocol (UDP). IP addresses from 224.0.0.0 to 239.255.255.255 are designated as multicast addresses. This range was formerly called “Class D.” The sender sends a single datagram to the multicast address and the intermediary routers take care of making copies and sending them to all receivers that have registered their interest in data from that sender. Multicast IP ranges assigned through DHCP scope. In any case, range 224.0.0.0 through 224.0.0.255 is reserved for local purposes (as administrative and maintenance tasks) and datagram’s destined to them are never forwarded by multicast routers. Similarly, the range 239.0.0.0 to 239.255.255.255 has been reserved for administrative scoping.

WDS Multicast Image Creating multicast images in WDS server is easy and straightforward if you have a functioning multicast infrastructure. For multicast imaging to work properly, the network devices that connect the WDS multicast clients to the WDS server providing the multicast transmission must support and allow multicast traffic as mentioned above. If the WDS server already contains tested boot and install images. One important point to note about multicasting is that only the Windows Server 2008 boot.WIM boot image file contains a WDS multicast client. In WDS server, you have to add Windows Server 2008 boot.WIM file into boot image. Now follow the screenshots bellow to distributive multicast image. Delete Multicast image when distribution no longer required.

Log on to WDS server using Admin Privilege. Go to Administrative Tools>WDS>Servers>Expand WDS Server>Right click on Multicast Transmission>Click Create Multicast Transmission.

1

2 3 4

Here, you can schedule transmission if bandwidth and distribution time are criteria.

5 6