Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part II

  See also: Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part I After reviewing Post I about installing and configuring Windows Deployment Services, we’ve also review the process of capturing a customized Windows 7 image and upload it to WDS. To image is already available and we can use it to deploy on workstations from a PXE […]

Read More →

Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part I

  See also: Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part II  We had a good look about the possibilities about Windows deployment; regarding Windows 7 we’ve completed a guide using Microsoft Deployment Toolkit 2010 (MDT 2010 beta) to capture and deploy unattended installations of Windows 7 with Office 2007 (Post I, Post II and Post III). […]

Read More →

Step-by-Step: Adding Hyper-V Integration Components to Windows PE using WAIK 2.0 Tools

For those that have been using Windows Automated Installation Kit (WAIK) 2.0 released recently (download link here) or using Microsoft Deployment Toolkit 2010 Beta 1, that works only with WAIK 2.0 (check these articles of mine about MDT 2010: Post I, Post II and Post III); maybe you’ve noticed that the management tools that were included with WAIK 1.1 (and 1.0) disappeared in this new version. These tools were consolidated by one command-line: DISM.exe (more info on Post I about MDT 2010). Meaning that the Windows PE management (like customizing, adding drivers or inserting Hyper-V integration components to those images) that you executed on previous versions of WAIK, has significant changes. On this post we’ll be reviewing how to add the Hyper-V Integration Components to a Windows Preinstallation Environment (Windows PE) image, including the new Windows PE 3.0. Why should I need to add the Hyper-V Integration Components to Windows PE? The Integration Components of Hyper-V are a set of drivers that are a significant performance change that you can apply to virtual machines for them to be able to install synthetic devices instead of emulated devices. Some of the drivers that are installed using the Integration Components are: Video driver, network driver (with this you avoid using Hyper-V’s Legacy Network adapter), storage driver, VMBUS (transport for synthetic devices), time sync (time synchronization with the host), etc. Adding Hyper-V Integration Components  As I mentioned before, I prepared a set of […]

Read More →

Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture customized Windows 7 Images – Part III

IMPORTANT: Updated versions from this series using Windows 7 + Microsoft Office 2010 in automated deployment with MDT 2010 can be found here: Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III   This is going to be the last part (at least for now) for this step-by-step guide for customizing and deploying Windows 7 images with MDT 2010. On the previous posts we’ve learned how to run the firsts configurations on MDT, adding operating system files and creating a task sequence for the reference image (Part I); and also adding Office 2007 to the reference image and making it a silent installation (Part II). The third post it’s going to be just to deploy the reference and customized image, and then capture it into a .wim file, that we can later deploy using MDT or add it to Windows Deployment Services (WDS). Deploying Reference Image Since we already have our boot environments, ISO and WIM files; and that we have the Windows Deployment Services role installed, I’ll start using it: I’m going to add the LTI boot image to WDS that will let me create and capture the reference image. Note: You can also use the ISO file too boot from a CD […]

Read More →

Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture customized Windows 7 Images – Part II

IMPORTANT: Updated versions from this series using Windows 7 + Microsoft Office 2010 in automated deployment with MDT 2010 can be found here: Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III On the first post of this series, we’ve managed to install MDT 2010 and its requirements, prepare distribution share and task sequence, add Windows 7 image to use it as reference and create the deployment point. We are now going to add Office 2007 as an application to be deployed included in the OS image and complete the environment to generate the reference image. The process of adding an application like Office 2007 it is quite simple, the only trick is to get the application to install silently (or unattended) without requiring for user intervention , we’ll see how that works. Adding Applications to MDT 2010: Office 2007 We’ll add the application using also a simple wizard, but the interesting part comes when you get the chance to modify default settings on the Office 2007 package: 1. “Deployment Workbench” > “Distribution Share” > “Applications” > “New”. 2. Select “Application with source files”. 3. Complete the data about the application. 4. Select the “Source Directory”. Since I have it on the hard drive, […]

Read More →

Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture customized Windows 7 Images – Part I

IMPORTANT: Updated versions from this series using Windows 7 + Microsoft Office 2010 in automated deployment with MDT 2010 can be found here: Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III Microsoft Deployment Toolkit team released the first beta of their next version: Microsoft Deployment Toolkit 2010 Beta 1 (you can access to the Beta program from Microsoft Connect and download the build). This new version includes several improvements, but perhaps the most important ones are related to Windows 7 and Windows Server 2008 R2 compatibility. Some of the New Features Support for deploying: Windows 7 and Windows Server 2008 R2 Hard Link Migrations using USMT 4 (User Migration Toolkit). Integration with new Windows Automated Installation Kit (WAIK) 2.0 toolset such as BCDBOOT and Windows PE 3.0. DISM tool (Dism.exe) included with WAIK 2.0 replace three other tools on previous version: Pkgmgr.exe (Package Manager), Intlcfg.exe (Internal Settings Configuration Tool) and PEimg.exe (WindowsPE Command Line tool ). If you are planning to implement Windows 7 on your environment (check this link about the review I made about Windows 7 functionality) or you want to start to get to know Microsoft Deployment Toolkit in this new version; I’ve prepared this step-by-step guides that will cover […]

Read More →

Troubleshooting WDS: Event ID 257 – 258 – 266 – 513

Windows Deployment Services depends and works directly with Active Directory and DHCP, meaning that if any of those two servers are significantly modified, then probably you will not be able to start the WDS service and get the events ID: Event Viewer from WDS Server Event 257: An error occurred trying to start the Windows Deployment Services server. Event 258: An error occurred trying to start the Windows Deployment Services image server. Event 266: An error occurred while to refreshing settings. Event 513: An error occurred trying to initialize provider WDSImgSrv from C:\Windows\system32\WdsImgSrv.dll. Windows Deployment Services server will be shutdown. Disclaimer Please note that the following possible reasons, are related when all those events appear simultaneously and with the same descriptions. Event ID 513 can also appear regarding to a PXE provider error: “An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown”. This particular error could happen for several reasons, like installing on the same server a System Center Configuration Manager PXE provider that replaces the WDS. Possible Reasons Those particular errors appeared when there were changes on Active Directory that did not were performed smoothly: – Changing a Global Catalog from Domain Controller. – Shutting down an active Domain Controller. Solution To solve this, you need to insert manually the FQDN of the domain controller working as a Global Catalog. 1 – Open the WDS snap-in and access server properties. […]

Read More →