Upgrading and deploying Windows 7
Download as PPTX, PDF0 likes1,399 views
The document outlines various deployment tools for Windows 7, including the Microsoft Assessment and Planning Toolkit, Application Compatibility Toolkit, and Microsoft Deployment Toolkit, detailing their functionalities and benefits for assessing and deploying applications. It also discusses the Native VHD Boot feature, its benefits and limitations, and provides a guide for configuring VHDs in Windows. Links to additional resources are provided throughout the document for further information.
Upgrading and deploying Windows 7
- 1. Deployment Tools for Windows 7 Microsoft Assessment and Planning Toolkit (MAP) Application Compatibility Toolkit (ACT) Windows Automated Installation Toolkit (WAIK) Microsoft Deployment Toolkit (MDT) Microsoft System Center Configuration Manager (SCCM)
- 2. MAP Toolkit agentless, automated, multi-product planning and assessment tool provides detailed readiness assessment reports extensive hardware and software information utilization data for Hyper-V server virtualization planning virtualization candidate assessments http://www.microsoft.com/en-us/download/details.aspx?id=7826
- 3. Application Compatibility Toolkit helps customers understand their application compatibility situation Verify an application's compatibility with a new version of the Windows operating system mitigate application compatibility issues before deploying Windows 7® Test your Web applications and Web sites for compatibility with new releases and security updates to the Windows Internet Explorer® Internet browser http://www.microsoft.com/en-us/download/details.aspx?id=7352
- 4. Windows AIK is a set of tools and documentation supports the configuration and deployment of Windows® operating systems automate Windows installations, capture Windows images with ImageX configure and modify images using DISM create Windows PE images migrate user profiles and data with the USMT includes the Volume Activation Management Tool http://www.microsoft.com/en-us/download/details.aspx?id=5753
- 5. Microsoft Deployment Toolkit Unified tools and processes required for desktop and server deployment efficiently manage large-scale deployments of Microsoft Office 2010 Reduced deployment time and standardized desktop/server images supports Configuration Manager 2007 and Configuration Manager 2012 Fully automated zero touch installation deployments by utilizing SCCM uses Windows deployment tools for Lite Touch Installation deployments http://technet.microsoft.com/en-us/solutionaccelerators/dd407791.aspx
- 6. Native VHD Boot local disk must have at least two partitions a system partition that contains the Windows 7 boot-environment files and Boot Configuration Data (BCD) store a partition to store the VHD file local disk partition that contains the VHD file must have enough free disk space for expanding a dynamic VHD to its maximum size and for the page file created when booting the VHD. The page file is created outside of the VHD file, unlike in the case of a virtual machine where the page file is contained inside the VHD
- 7. Native VHD Boot benefits Using the same image-management tools for creating, deploying, and maintaining system images to be installed on designated hardware or on a virtual machine multiple boot scenarios without requiring separate disk partitions Deploying Windows 7 images in a VHD container file for faster deployment of reusable development and testing environments Replacing VHD images for server redeployment or recovery Hardware and driver testing http://technet.microsoft.com/en-us/library/dd799282(v=ws.10).aspx
- 8. Native VHD Boot limitations Native VHD boot is supported only by: Windows® 7 Enterprise Windows® 7 Ultimate Windows Server 2008 R2 disk management support can attach approximately 512 VHD files concurrently does not support hibernation of the system, although sleep mode is supported VHD files cannot be nested not supported over Server Message Block (SMB) shares Continued on next slide
- 9. Native VHD Boot limitations Cont’d Bitlocker cannot be used to encrypt the host volume containing VHD files used for native VHD boot, and bitlocker cannot be used on volumes contained inside a VHD An attached VHD cannot be configured as a dynamic disk The parent volume of the VHD cannot be configured as a dynamic disk
- 10. Configure VHD in Windows DEMO Create VHD in Disk Management Mount VHD and assign letter Create VHD in DISKPART for Native Boot VHD from Windows Setup Shift-F10 at setup screen Use Diskpart to create/attach the vdisk Return to Setup and complete the install on the vdisk To Modify the BCD Store with a custom description after the install: BCDEDIT /SET {current} DESCRIPTION "whatever you want to see in the boot menu"
Editor's Notes
- #11: TO install from installation DVD for windows 7 in VHD-Boot to DVD-Shift+F10 to shell out to a PROMPT-Follow instructions belowCommands to create VDISK with DISKPART in WinPEdiskpartlist diskselect disk X (where X is the disk you want to create the VHD)list volume (shows the volumes that you have on the disk)select volume X (where X is the volume that you want to create the VHD)create vdisk file=c:\\windows7.vhd maximum=25600 type=fixedselect vdisk file=c:\\windows7.vhdattach vdiskReturn to setup (use the 'X' in the top right hand corner to close the command prompt and then repeat to close the repair options window) and complete the install on the VDISK you just created.**This method will automatically create a boot record in the BCD store, you just need to create the 'DESCRIPTION' with BCDEDIT to put a meaningful name on the OS selection page using steps as follows:To configure a new description in BCD,BCDEDIT /SET {current} DESCRIPTION "whatever you want to see in the bootmenu"**USING IMAGEX TO DO THE INSTALL FROM WITHIN WINDOWS**If you use 'imagex.exe' to install the WIM to an attached VHD within the windows environment, you would create the VHD in Disk Management, Attach the VHD in Disk Management and then use IMAGEX to apply the WIM image file:imagex /apply c:\\win7disk\\install.wim 1 X:\\vhd7\\ **(where the install.wim is the location you copied the wim from the sources dir of the installation DVD and '1' is the image number associated to the SKU of the product you wish to install and 'V:\\' is the letter associated to the attached Vdisk on the system.)**To create the Boot store entry, use the following:bcdedit.exe /copy {current} /d "Windows 7 VHD"*This will output a GUID, you need to copy the GUID it provides and replacethe <ID> portions of the following commands with the copied GUID.bcdedit /set <ID> device vhd=[X:]\\vhd7\\windows7.vhdbcdedit /set <ID> osdevicevhd=[X:]\\vhd7\\windows7.vhdbcdedit /set <ID> detecthal on**For MOVING A VHD TO A DIFFERENT MACHINE AND CREATING A BOOT OPTION FOR IT**Using 'BCDBOOT.exe' located in System32Copy the VHD to a location on the hard drive. Use 'diskpart' or 'Disk Management' to attach the VHD. Run the following to import the OS info into the BCD store:BCDBOOT V:\\Windows *('v:\\windows' is relative to the attach point of the VHD on the system)*