Creating and Maintaining a Windows 7 Image using Virtual PC on Windows 7

[patris1]

http://lynnlunik.net/2010/03/creating-and-maintaining-a-windows-7-image-using-virtual-pc-on-windows-7-part-1-of-3-step-by-step/

Part 1 of 3



One method of making available a Windows 7 Workstation Image is using Virtualization Software to provide such an Image.
Once generated, this Windows 7 Image can be used for Application Testing, addition to a Domain for Group Policy Testing
and many other uses. I have created many Windows Operating Systems Images over the years and wanted to share with
you one method to create, modify, maintain and re-use a Windows 7 Image using Virtual PC from Microsoft. The key to this
endeavor is understanding that generating the initial Windows 7 Image in Virtual PC is a straightforward process. The Virtual
PC method of mounting an .ISO Image of the Windows 7 Source Media files from the Host Workstation CD/DVD Drive within
the image, and then using the mounted .ISO File (of Windows 7 Source Media) for the Virtualized Guest Operating System
Installation provides an effecting method to creating the initial Image. Once the Virtualized Guest Partition running Windows 7
Entprise is installed, my hope is to offer a manual method to ‘maintain’ the Windows 7 Image for future updates, while, at the
same time creating a copy of the Image and then sealing the Image using the defined Sysprep Process from Microsoft. The usefulness of having a Windows 7 Image readily available for use in Virtual PC is endless. The fact that you will always have a ‘current’ Windows 7 Image in your Virtual PC Library is invaluable. Over and above this usefulness I will review a method to duplicate the VHD File prior to using Sysprep for ’sealing’ and then maintaining the ‘unsealed’ VHD File for use in subsequent months when Security Updates or additional Application are required within the Image.
Of course, the method I review is very manual. There are plenty of points along the way where scripting or use of specific utilities or tools would be appropriate. My goal is to offer a framework for the process whereby you can apply any nuances, scripting or any other activities you feel appropriate. Again, this is a multi-part Blog entry. Here’s how each part lays out.

1. In this Blog entry Part 1 of 3 I will generate a Windows 7 Enterprise Image on a Windows 7 Workstation running Virtual PC. Typically this is termed ‘provisioning an image’ as we are starting in Virtual PC with nothing and finishing with Windows 7 Enterprise running as a Virtual Guest Partition within Virtual PC on a Windows 7 Host.
2. In Part 2 of 3 I will use a process to ’seal’ a copy of the Virtual Hard Disk (VHD File Format) using Sysprep that can then be used as a ‘current’ Windows 7 Image.
3. Finally, in Part 3 of 3 I will review a method to maintain an ‘unsealed’ copy of the Virtual Hard Disk, update the Image with Security Updates, duplicate the VHD then ’seal’ the ‘new current’ Windows 7 Image to be made the ‘most up to date’ and ‘fresh’ Windows 7 Enterprise Image when the need arises for its use.

Figure 1 – Launch Virtual PC on the Windows 7 Enterprise Host to begin creation of the Windows 7 Enterprise Guest Partition.
On the Windows 7 Enterprise Host Workstation I begin by opening Virtual PC using the ‘Manage Virtual Machines’ Task. I have several Virtual Guest Partitions already on this Host as you can see by the blurred Guest Partition Names under ‘Recent Virtual Machines. Use of the ‘Manage Virtual Machine’ Task is required to create a new Guest Partition (our Windows 7 Enterprise Image).

Figure 2 – Select ‘Create Virtual Machine’ to begin the creation process for the Guet Partition.
The ‘Create Virtual Machine’ Task initiates the Wizard that generates the Windows 7 Enterprise Image.

Figure 3 – Selection of a Folder named ‘Win7×86-Sealed’ to store the Virtual PC Guest Partition files.
I have created a Folder on the Volume titled ‘Win7×86-Sealed’ as the location for the files generated by Virtual PC when creating a Guest Partition. I select this precise name as it is a reminder that when completed this Image of Windows 7 Enterprise will need to be ’sealed’ using the Sysprep process prior to use.

Figure 4 – The ‘Create a Virtual Machine’ Wizard begins where both a ‘Name’ and a ‘Location’ are specified.



Figure 5 – Next the amount of ‘Memory’ and ‘Networking’ parameters are defined. I select to ‘Use Computer Network Connections’ which ‘bridges’ the Guest Partition across the Host Network Interface (NIC).



Figure 6 – The next selection in the ‘Create a Virtual Machine’ Wizard is specific to the ‘type’ and ’size’ of the Virtual Hard Disk.



Figure 7 – Note that (a quick aside ) to view the contents of the ‘Win7×86_Sealed’ Folder where the Virtual PC Guest Partition Files for this Windows 7 Enterprise Image are held includes 2 files at this point. File 1 is the ‘Virtual Machine Hard Drive Image’ file while File 2 is the ‘Virtual Machine Settings File’.



Figure 8 – Now that the ‘Create a Virtual Machine’ Wizard is completed status of the Guest Partition (the Windows 7 Enterprise Image) is visible located on the ‘E:’ Drive. Next, I will focus on the ‘CD/DVD’ Setting for the Guest Partition in order to ‘Boot’ this Bare Metal Guest Partition to an Operating System it is necessary to place the Windows 7 Source Media (DVD) in the form of an .ISO Image. This .ISO Image Virtual PC can read and used as Boot Media for the Virtualized Guest Partition Operating System installation.



Figure 9 – Upon selecting the Windows 7 Enterprise Image it is possible to modify the ‘Settings’ for this Guest Partition.



Figure 10 – Upon selecting the ‘Settings’ Option for this Guest Partition the ‘Windows Virtual PC Settings’ Dialogue Window is visible. The focus is on the ‘DVD Drive’ named ‘D:\’.



Figure 11 – Here is the key to creating this Windows 7 Enterprise Image (also called a ‘Guest Partition’) – selecting an .ISO File with the Windows 7 Enterprise Source Media (MSDN, Select or Volume Licensing) for the initial ‘Boot Process’ to create the Operating System Install. Since the ‘DVD Drive’ is pointed to the .ISO File of Windows 7 Enterprise Source Media I now move to ‘Boot’ the Guest Partition for the first time.



Figure 12 – Using the ‘Open’ Menu Option ’starts’ the Windows 7 Enterprise Guest Partition for the first time. Remember here, this Guest Partition should use the .ISO File of Windows 7 Enterprise Source Media and initiate the ‘Installation Process’ for Windows 7 Enterprise.



Figure 13 – Here the WinPE Environment from the Windows 7 Enterprise Source Media is Booting correctly. Now the initial Installation is underway a normal sequence of selecting IP Settings, Workgroup Mode, etc. occurs.



Figure 14 – The standard Mini-Boot Sequence for Windows 7 Enterprise is underway. Again, this is a Virtualized Guest Partition running on a Windows 7 Enterprise Host. Once this Guest Partition is complete with selected Security Updates and Applications I will duplicate the Virtual Hard Disk storing one ‘unsealed’ version for future Updates and using the second by ’sealing’ using the Sysprep Process as the ‘master’ for duplicating as many times as required based on the need for a Windows 7 Enterprise Image.



Figure 15 – One of the Features of a Virtual PC Configuration running on a Windows 7 Enterprise Host is the requirement to Install the ‘Virtual PC Integration Components’ to achieve real usability. Upon initially attempting to select the ‘Next’ Button from Figure 14 above, a Popup like this appears. Do note the ‘Ctrl+Alt+Left Arrow’ requirement to ‘release’ the mouse point prior to installing the Virtual PC Integration Components. Once the VPC Integration Components are installed (Requires a Reboot) this Key Sequence is no longer necessary.



Figure 16 – The Guest Partition is ready to installation of Windows 7.

Figure 17 – The Windows 7 Install Process requires Acceptance of the License Terms to advance.



Figure 18 – The Default allocation for a Dynamically Expanding Virtual Hard Disk Size is ‘127 GB’. This information correlates to Figure 6 above.



Figure 19 – Succesful selection of a Partition advances the Installation Process to begin the exchange of files from the Windows 7 Source Media to the Guest Partition.



Figure 20 – The cycles of the Windows 7 Installation near a close. Again, once we build this Windows 7 Image once I will review using it successfully over and over.



Figure 21 – After a successful Reboot the ‘Set Up Windows’ Dialogue Windows offers the ability to configure the ‘first Administrator’ and the ‘Computer Name’.



Figure 22 – Since the ‘first Administrator’ controls the Workstation the Wizard advances the requirement for Password Confirmation and a ‘Password Hint’ field.



Figure 23 – The ‘Automatic Update Settings’ near the final step to a successful Login to this Windows 7 Enterprise Virtualized Guest Partition.



Figure 24 – After a selection of the ‘Time Zone’ and a validation of the correct Time I proceed.



Figure 25 – Finally, the Windows Firewall Settings correlate to selection of the ‘Computers Current Location’. I select ‘Public Network’ as the most restrictive Windows Firewall Settings are included.



Figure 26 – Success! Upon viewing the Windows 7 Enterprise Desktop I begin the process of installing the ‘Virtual PC Integration Components’. Again, these components allow interaction between the Virtual Environment and the Host Workstation in a fluent way.



Figure 27 – The Virtual PC Integration Components display as being ‘inserted’ into the Guest Partition CD/DVD. I select ‘Run Setup.exe’ from the ‘Autoplay’ dialogue windows.



Figure 28 – The ‘Virtual PC Integration Components’ use a typical .MSI Installation paradigm.

Figure 29 – The ‘VPC Integration Components’ install a variety of Drivers to ’shim’ between the Hardware Assisted Virtualization and Hardware Components on the Host Workstation.

Figure 30 – In this capture the ‘VPC Integration Components’ installation is complete pending a Reboot. Observe the Error Balloons offered carefully. Further investigation of this Error Balloon will occur following the Reboot.



Figure 31 – The pending Reboot moves this Installation closer to visiting Microsoft Update for Security, Critical and Important Updates.



Figure 32 – After a successful Reboot I login as the ‘first Administrator’ configured previously. I will begin the ‘patching process’ next. Additionally, I will add any Applications appropriate for this Image.



Figure 33 – The ‘Virtual PC Integration Components’ installed successfully as demonstrated by the availability of the ‘USB’ Drop Down Menu that includes integrating the ability to ‘Attach’ to the Host Workstation ‘ Desktop’.



Figure 34 – After a quick switch of the ‘Default Picture’ I am ready to begin next steps. These steps include 1) applying Security Updates and 2) installing Applications. Applications for consideration are any used in the Image that would require time and effort in the future when provisioning this Virtualized Image for usage. Time spent once is gained back triple if carefully installed.



Figure 35 – A clean, working Desktop is available in this Virtualized Guest Partition running Windows 7 Enterprise. Control of this Image is available through the Host Workstation. I will begin adding appropriate Security, Critical and Important Updates from Microsoft Update.



Figure 36 – Upon selecting ‘Control Panel’, then ‘Check for Updates’ from the ‘Windows Update System and Security Center’ I begin to mature this Image to full health. Remember, I selected ‘Public’ as the ‘Network Connection’ which provides well defined Windows Firewall settings.



Figure 37 – After selecting and installing a varity of Security Updates a Reboot is in order. I will ‘complete’ this Image by adding additional Applications for productivity.

Figure 38 – Success! Again, this is the first sequence of steps to mature this Image for additional use.
Summary: In this Blog entry focused on creating and maintaining a Windows 7 Image using Virtual PC on Windows 7 I initiated the creation of a Virtual Guest Partition running Windows 7 Enterprise Edition. this Virtual Guest Partition running Windows 7 Enterprise Edition will be used in subsequent Blog entries where both ’sealed’ and ‘non-sealed’ Images will be preserved.
Lynn Lunik

---

موضوعات مشابه:

• Step by Step Creating and Maintaining a Windows 7 Image using Virtual PC on Windows 7
• what is Windows SIM and how can I use it ? Windows System Image Manager
• Creating a Sysprep Image Library for Virtual PC
• Creating, Attaching, and Mounting VHD Files in Windows 7 and Windows 2008 R2
• Microsoft Windows Virtual PC Windows XP Mode For Windows 7

---

[patris1]

http://lynnlunik.net/2010/03/creating-and-maintaining-a-windows-7-image-using-virtual-pc-on-windows-7-part-2-of-3-step-by-step/

Part 2 of 3


I am using several steps to demonstrate how to create, use and maintain a Windows 7 Image using Virtual PC on Windows 7 Enterprise. Part 1 of 3 is available here. It is important to view Part 1 of 3 in advance of reviewing this Blog entry as it includes the fundementals of creating a Windows 7 Image using Virtual PC. This is Part 2 of 3 that addresses creation of a ’sealed’ Windows 7 Enterprise x86 Image.
Here’s some reference vocabulary for this endeavor:
Sealed - the process of using Microsoft Sysprep to ’seal’ a Workstation Image for duplication. The ’sealing’ process applies to either Physical or Virtual Machine Images.
Unsealed – the process of updating a Virtual Machine Image and then retaining the Image without ’sealing’ for future updates.
Again, because in Virtual PC a series of Files comprise a Virtual Machine it is this fact I capitalize upon to retain both a ’sealed’ and ‘unsealed’ Virtual Machine Image.

Figure 1 – As I begin, here’s a quick refresher of the items constructed in Step 1 of 3. In a Folder titled ‘Win7×86_Sealed’ I have created a Virtual Machine Hard Drive Image (VHD) titled ‘Win7×86_3-2-2010. This VHD will become a ’sealed’ VHD with updates and Applications through 3-2-2010. Also note the ’supporting files’ such as the ‘Virtual Machine Settings File’ and the ‘VPC Backup File’ in the folder.
The concept of ’sealing’ a VHD includes using the Microsoft Sysprep Process to remove any uniquely distinguising characteristics from the Image. Examples of characteristics include 1) Domain Membership and 2) Machine SID (among others).

Figure 2 – Next, I create a new Folder titled ‘Win7×86_Unsealed’. This folder will ’store’ the unsealed version of the VHD for future modification. In summary, because this VHD is not ’sealed’ using the Sysprep Process it can be ‘re-opened’, then modified and maintained in the future. I copy the VHD from the ‘Win7×86_Sealed’ Folder PRIOR TO SEALING THE VHD FILE! (This is important as the naming convention for the folder can be confusing initially!)

Figure 3 – The ‘unsealed’ VHD is copied (a manual file copy) from the ’sealed’ folder to the ‘unsealed’ folder titled ‘Winx86_Unsealed’. Again, the ‘unsealed’ VHD is for storage and future useage.

Figure 4 – After moving a copy of the VHD into the ‘unsealed’ folder for safe keeping – I ‘Open’ the VHD to begin the Sysprep Process.

Figure 5 – The Windows 7 Enterprise Workstation Image opens without issue. I have added the Sysinternals BGInfo 4.16 application to provide the details displayed as the Desktop Background.

Figure 6 – A quick enumeration of the ‘Start Menu’ indicates installation of only basic Applications within this Windows 7 Enterprise Image. Next, I will begin the Sysprep Process to ’seal’ this Image.

Figure 7 – An ‘Administrative Command Prompt’ is required to run the Sysprep Process.

Figure 8 – The Sysprep Process is initiated.
The commands required from an Administrative Command Prompt for Sysprep include:
cd \windows\system32\sysprep sysprep

Figure 9 – The Sysprep Tool v.3.1.4 opens within this Windows 7 Enterprise Image. It is important to select ‘Enter System Out-of-Box Experience (OOBE)’ from the ‘System Cleanup Action’ Drop Down, and ‘Shutdown’ from the ‘Shutdown Options’ Drop Down Menu.
Upon completion of this step (when successful) a fully ’sealed’ version of a Windows 7 Enterprise Virtual Machine is stored within the Virtual Machine Hard Drive Image file. This VHD is ‘current’ with Updates and installed Applications through the creation date (3-2-2010). I can now duplicate this ’sealed’ VHD for creation of any Windows 7 Enterprise x86 Virtual Machines required for Testing.

Figure 10 – Observing the ‘Win7×86_Sealed’ Folder denotes the 3 Files that comprise the Windows 7 Enterprise Virtual Machine just ’sealed’ by the Sysprep Process.
Creating a Workstation Image from the ‘Sealed’ Windows 7 Enterprise x86 Sysprep Image


Figure 11 – I create a Folder Hierarchy of ‘E:\VMs_in_Use\WS_1_Win7×86′ for storage of Virtual Machines for Testing. If you observe the Folder Names it should be clear my intent is to make a Windows 7 Enterprise x86 Virtual PC Image with a Host Name of ‘WS-1′. I will copy the ’sealed’ VPC Hard Disk to the ‘\WS_1_Win7×86′ Folder.

Figure 12 – Upon completion of copying the ’sealed’ Windows 7 Enterprise x86 VHD into the destination folder where the VPC Workstation Image files will reside, I then ‘rename’ the VHD File. This renaming process allows for orderly storage, reference and usage when numerous Virtual Machines are involved.
The next step will entail creating a new Virtual Machine using Virtual PC and the referenced Virtual Machine Hard Disk.

Figure 13 – After renaming the Virtual Machine Hard Disk to match the naming criteria of the Testing Workstation (WS-1), I can begin to ‘Create’ the Virtual Machine using the Virtual PC Console.

Figure 14 – I begin creation of the new Virtual Machine using the ’sealed’ Windows 7 Enterprise x86 Virtual Hard Disk Image by selecting ‘Manage Virtual Machines’ from the ‘Windows Virtual PC’ Application.

Figure 15 – Upon opening the ‘Windows Virtual PC’ Application I select ‘Create Virtual Machine’ from the menu choices.

Figure 16 – The ‘Create a Virtual Machine’ Wizard provides the ability to name the Virtual Machine and define the File Path. Note the File Path to the Virtual Machine Hard Disk Image previously ’sealed’ using the Sysprep Process.

Figure 17 – Next, the amount of Memory and desired Network Interface Connection type are selected.

Figure 18 – Here’s the important step in using a ’sealed’ Sysprep Image in Virtual PC – BE SURE TO SELECT THE VHD PREVIOUSLY COPIED INTO THE VIRTUAL MACHINE FOLDER. Again, I previously copied the ’sealed’ Windows 7 Enterprise x86 VHD named ‘WS_1_VHD1.VHD’ into this folder for useage.

Figure 19 – Upon completion of the ‘Windows Virtual PC’ Wizard for creating a Virtual Machine I move to the Folder where the new Virtual Machine is stored. Upon selecting the Virtual Machine, I then select ‘Open’ from the menu options.

Figure 20 – The new Virtual Machine running Windows 7 Enterprise x86 initiates for the first use. The Sysprep Options selected in Figure 9 above yield starting of the System-Out-of-Box Wizard.

Figure 21 – This Windows 7 Enterprise x86 Image is starting correctly. Again, this is a ’sealed’ Image created using the Sysprep Process.

Figure 22 – The initial steps in the ‘Set Up Windows’ Wizard include 1) naming the Computer and 2) identifying the initial Administrator for the Workstation Image.

Figure 23 – Upon inputting a Password for the initial Administrator, along with a Password Hint, I proceed to the next step in the ‘Set Up Windows’ Wizard for this Windows 7 Enterprise x86 Virtual Machine.

Figure 24 – I select Acceptance of the License Terms next.

Figure 25 – I select the Recommended Settings for Automatic Updates.

Figure 26 – I select the appropriate Time Zone and Time.

Figure 27 – Finally, I select the Network Connection matched to the Computers Current Location.

Figure 28 – Upon completing of the ‘System Out-of-Box’ Wizard, a very usable Windows 7 Enterprise x86 Virtual Machine is available. This Virtual Machine is Updated through the Date of creation and includes any Applications I have included in the original ’sealed’ Image.
In creating a prepared Windows 7 Enterprise x86 Virtual Machine Image I have the flexibility to create as many Virtual Machines as required for the Testing or usage Scenarios I address. If another Windows 7 Enterprise x86 Virtual Machine Image were necessary I would simply follow the process again beginning at Figure 11 above through Figure 28. Of course each of these Virtual Machines require additional System Resources which can be allocated as available.
In Part 3 of 3 I will demonstrate how to ‘maintain’ the Windows 7 Enterprise x86 Virtual Machine Image that is ‘unsealed’. Specifically, when additional Security Updates are made available I will apply them to the ‘unsealed’ Virtual Machine Image and then update the ’sealed’ Image using the ‘fresh’ Virtual Machine Hard Disk Image. Take a look at Part 3 of 3 when you have interest.
Summary: In this Blog entry I focus on ’sealing’ a Windows 7 Enterprise x86 Image created using Virtual PC and then using the Sysprep Process. I also demonstrated the required steps to separately maintain an ‘unsealed’ version of the Windows 7 Enterprise x86 Image stored in a separate Folder. This Blog entry is Step 2 of 3 in a 3 part series. In the Part 3 of 3 I will demonstrate how to ‘update’ the ‘unsealed’ version of the Windows 7 Enteprise x86 Image stored in Part 2 of 3 for future useage.
Lynn Lunik