Walid Hegazy

How To Do :) IT


Leave a comment

WDS client may hang up after loading the boot.wim file if you import the Windows 8 x86 boot image only the WDS server

enter image description here

Consider the following scenario. You have a Windows Server 2008 R2 WDS (Windows Deployment Service) server and you plan to use it to deploy Windows 8 or Windows Server 2012 operating systems. If you import a Windows 8 x86 boot image only on this WDS server and then if you try to boot up a WDS client from this WDS server, you may find that the system hangs up after loading the \Boot\x86\Images\boot.wim file.

Reade the full KB on Microsoft

Advertisements


2 Comments

Windows 8 Migration & Deployment Using MDT 2012 update 1

 

Before we begin, let’s cover some basics. In short, there are three possible ways for Windows 8 deployment:

  1. Manual deployment
  2. Semi-automated deployment, aka Light Touch Installation or LTI
  3. Fully-automated deployment, aka Zero Touch Installation or ZTI

Manual Deployment: A manual deployment is something that could happen in homes and really small-to-medium business environments. This approach involves taking a backup of the data, reinstalling the PC by starting a manual setup of Windows 8 (DVD, ISO, etc.), and restoring the user data. This is rather time-consuming, and I personally think it is a bit outdated. Even so, this is still a very good solution for all PC environments with less than ten machines.

Light Touch Installation (LTI): Light Touch Installation means you will use a semi-automated approach for Windows 8 deployment. In short, this involves using a deployment tool, creating an image, and reproducing/deploying the same image to multiple clients by booting from a deployment medium (typically a bootable USB-stick).

Zero Touch Installation (ZTI): By using a Zero Touch deployment mechanism, you basically give the option to the end-user to (re)deploy the machine completely by himself or herself. In short, this starts with the configuration of the deployment tool, creating an image, and automatically

What is the Microsoft Deployment Toolkit 2012 (MDT 2012)?

MDT 2012 is the newest version of the Microsoft Deployment Toolkit (MDT), a Solution Accelerator for operating system and application deployment. MDT 2012 Update 1 supports deployment of Windows 8, Windows 7, Office 2010 and 365, Windows Server 2012, and Windows Server 2008 R2, in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP.

 

Let Us Start

Configuring MDT 2012 Update 1 to deploy Windows 8 for the 8650w machines is done in nine easy steps:

clip_image003[394]       Create a deployment share

clip_image003[395]       Import the Windows 8 operating system

clip_image003[396]       Import the drivers

clip_image003[397]       Add the application

clip_image003[398]       Create a task sequence

clip_image003[399]       Configure the deployment share settings

clip_image003[400]       Update the deployment share

clip_image003[401]       Add the MDT 2012 Update 1 boot image to WDS

clip_image003[402]       Deploy the Windows 8 image

System Requirements

clip_image003[403]      A member server named MDT01 running Windows Server 2008 R2 or Windows Server 2012 with the following software installed:

clip_image003[404]       Windows Deployment Services

clip_image003[405]       ADK

clip_image003[406]       .NET Framework 3.5.1

clip_image003[407]       MDT 2012 Update 1

Continue reading