WIM2VHD: Converting WIM files to VHD files

MSDN Code Gallery just released a first version for a very promising tool: WIM2VHD. With this you can take a raw WIM file (like the ones included inside any Windows 7 or Windows 2008 R2) or a custom WIM (like a captured and customized image) and converted directly to a VHD that you can boot directly using Virtual PC, Virtual Server or Hyper-V. Take a look at this link: Windows(R) Image to Virtual Hard Disk (WIM2VHD) Converter Introduction The Windows(R) Image to Virtual Hard Disk (WIM2VHD) command-line tool allows you to create sysprepped VHD images from any Windows 7 installation source. VHDs created by WIM2VHD will boot directly to the Out Of Box Experience, ready for your first-use customizations. You can also automate the OOBE by supplying your own unattend.xml file, making the possibilities limitless. Fresh squeezed, organically grown, free-range VHDs – just like Mom used to make – that work with Virtual PC, Virtual Server, Microsoft Hyper-V, and Windows 7’s new Native VHD-Boot functionality! Requirements A computer running one of the following Windows operating systems: – Windows 7 – Windows Server 2008 R2 – Windows Server 2008 with Hyper-V RTM enabled (x64 only) The Windows 7 Beta Automated Installation Kit (AIK) or Windows OEM Pre-Installation Kit (OPK) installed. A Windows 7 or Windows Server 2008 R2 installation source, or another Windows image captured to a .WIM file. How to Use It Create a Windows Server 2008 R2 Server Standard […]

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 →

Windows Deployment Services (WDS): Unattended Installation Files Examples

After completing three posts about unattended deployment of full operating systems with WDS (Part I, Part II and Part III), I had pending this post about the examples of the unattended files. So here they are. Note: All of the data about the components and values used on these two XML files, are explained on Part III about WDS Deployment. WDSClientUnattend Download example here. (Change file extension from .doc to .xml to start using it or you can still open it as a Word file). Part of WDSClientUnattend.xml AutoAttend Download example here. (Change file extension from .doc to .xml to start using it or you can still open it as a Word file). Part of AutoAttend.xml Hope that you find it useful! Cheers! Installing and Configuring WDS (Windows Deployment Services): Full Images Deployment (Part I) Installing and Configuring WDS (Windows Deployment Services): Full Images Deployment (Part II) Installing and Configuring WDS (Windows Deployment Services): Full Images Deployment (Part III)

Read More →

Installing and Configuring WDS (Windows Deployment Services): Full Images Deployment (Part III)

At this point we’ve already installed and properly configured Windows Deployment Server on Windows 2003/Windows 2008 (Part I); and we created a full image (programs and features installed) on our Windows Vista and uploaded it to the server (Part II); the only thing missing is creating the answer files that will be used on the images to achieve the full unattended installation of our operating system. For those using Windows Server 2003 SP1, we reviewed that among the requirements for WDS installation there was installing Windows Automated Installation Kit. This kit also gives us an important tool for the unattended files creation, the Windows System Image Manager. So, it’s recommended for any other platform used on WDS to download this kit and install the System Image Manager. This tool it’s not a requirement for creating the unattended files. Installing WAIK Preparing the Files Using System Image Manager System Image Manager provides us the way to, using the .wim (or .clg) file for an installation, select the components that are necessary within the answer files. This way we can be sure that the answer options selected are used on the right place at the right time: Open System Image Manager for Start Menu. Click on File and click on Select Windows Image. Select the .wim file that we previously created or just use the file from the installation media (install.wim). You can also select the catalog files (.clg): these are the […]

Read More →

Installing and Configuring WDS (Windows Deployment Services): Full Images Deployment (Part II)

Ok then, after completing the first configurations made on the Part I of this guide we can perform a clean but attended network installation of Windows Vista. There are two main steps to take and complete a full image and unattended deployment: 1. Creating the base image to deploy: OS, programs and other special configurations + uploading it to the WDS server. 2. Making an unattended file to be used with that image. Creating the Base Image Note: On this series of posts we are only considering to deploy Windows Vista or Windows Server 2008 images. The files used on WDS Native mode as unattended files are only valid to those operating systems, if you want to make unattended deployment with Windows XP or 2003 OS; you will need to use RIS or WDS Legacy Mode. The first step it’s pretty simple, it consists on installing the operating system with all the features, programs and configurations that you want. But there are some considerations first: After you complete the image, there’s a process where you release all the specific data involving the computer where it’s installed, like the Security Identifier (SID), computer name, etc. Here are some of the things that the image won’t keep after the release process: · Computer name· Owner and Company name· SID· Domain or workgroup membership· TCP/IP Settings· Regional and keyboard settings· Specific hardware drivers. This refers to specific computer hardware, like video or audio […]

Read More →