部署機制 Windows Image (WIM) 曹祖聖 台灣微軟資深講師 jimycao@syset.com http://teacher.allok.com.tw/ MCP, MCP+I, MCSA, MCSE, MCDBA, MCAD, MCSD, MCT, MVP

大綱 Vista 映像技術簡介 建立映像檔 編輯映像檔 部署映像檔

大綱 Vista 映像技術簡介 建立映像檔 編輯映像檔 部署映像檔

Vista 部署的加強 http://www.microsoft.com/technet/windowsvista/deploy 模組化 <SLIDETITLE INCLUDE=7>Vista Deployment Enhancements</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE>Windows Vista contains tools and architectural enhancements that simplify deployment.</KEYMESSAGE> <SLIDEBUILDS>2</SLIDEBUILDS> <SLIDESCRIPT> Vista is built out of modular components, which means that device drivers, service packs, and components can be easily added to meet the specific requirements of your enterprise. The fact that each module is defined as an independent building block means that a specific component can be easily serviced or updated without breaking the whole operating system. Windows Vista is also language-agnostic. Languages, including English, are optional components and can be added separately from the operating system itself. You don't need a separate system configuration for each language, reducing the number of versions that an organization needs and resulting both in easier deployment and cost savings. [BUILD1] A typical cause of deployment complexity and costs is the number of specific configurations that administrators need to manage. Adding new hardware, language packs, updates, and drivers usually requires creating a new system configuration. Updating multiple configurations and testing each of them is costly and time-consuming. Therefore, one of Microsoft’s major goals in Windows Vista is to significantly reduce the number of deployment files you must maintain and help you maintain those files more easily. To achieve this goal, Microsoft added a suite of new tools to Vista that simplify the creation, management, and deployment of system image files. The new imaging capabilities of Windows Vista, along with powerful imaging tools, make the process of deploying Vista easier and less costly for your organization. 模組化 元件分離 獨立的定義 建立映像區塊 Windows Imaging 完整的映像工具 可套用組態檔案 彈性的套用方式 微軟的部署解決方案 http://www.microsoft.com/technet/windowsvista/deploy

映像技術的演進 WINNT32 SMS 2003 RIS 伺服器 .wim 檔 .wim 檔 Windows 安裝光碟片 參考電腦 目標電腦 <SLIDETITLE INCLUDE=7>History of Imaging</SLIDETITLE> <KEYWORDS>history, imaging</KEYWORDS> <KEYMESSAGE>Imaging has become more simple since WINNT.</KEYMESSAGE> <SLIDEBUILDS>3</SLIDEBUILDS> <SLIDESCRIPT> Historically, Microsoft has always offered solutions for script based installation. For example, WinNT32 offers the ability to customize your installation via various answer files. However, Microsoft began to recognize that customers typically use this technology once to capture their system and then do mass deployments via images. [BUILD1] Then came the introduction of the Remote Installation Services or RIS Server, which supported script or file based deployment. The file-based images were managed on the RIS server. This worked with Windows 2000 to install a local copy of the operating system to other computers from remote locations. With RIS, a client computer would contact a DHCP server for an IP address and then contact a boot server to install the operating system. [BUILD2] Next, Automated Deployment Services or ADS introduced a sector based image format. ADS is add-on to Windows Server 2003 Enterprise Edition that provided a solution for deploying Windows server operating systems. With support for script-based mass server administration, ADS also enables administrators to administer hundreds of servers as if they were one. The ADS solution was administrator initiated; whereas, the RIS server deployment was user initiated. However, since ADS was for deploying server operating systems it was not compatible with the RIS server. Then Microsoft released the XP Embedded product, which was also sector-based but was specific to deploying embedded devices. [BUILD3] With the introduction of SMS Operating System Deployment or OSD, we saw the first release of the WIM format. As opposed to the other sector based formats, this WIM format was file-based format. However, this format was specific to the SMS Release and it didn’t work well across the other deployment solutions. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>Microsoft then recognized the need to have a single deployment format with a single set of tools that can be used across all Windows deployment solutions.</TRANSITION> <TRANSITION LENGTH=2>Microsoft then recognized the need to have a single deployment format with a single set of tools that can be used across all Windows deployment solutions.</TRANSITION> <TRANSITION LENGTH=4>Microsoft then recognized the need to have a single deployment format with a single set of tools that can be used across all Windows deployment solutions.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://technet2.microsoft.com/WindowsServer/en/Library/d24c91f2-80cd-4a60-98c0-4b9ad28f678a1033.mspx</ITEM> <ITEM>http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/depopt/remoteos.mspx</ITEM> <ITEM>http://www.microsoft.com/windowsserver2003/techinfo/overview/risvsads.mspx</ITEM> </ADDITIONALINFORMATION> .wim 檔 .wim 檔 WINNT32 Answer Files RIS 伺服器 RIS 用戶端 部署的共用資料夾

WIM 映像的目標 <SLIDETITLE INCLUDE=7>Vista Imaging Design Goals</SLIDETITLE> <KEYWORDS>Vista, imaging</KEYWORDS> <KEYMESSAGE>Vista imaging format provides a single format across Windows deployment.</KEYMESSAGE> <SLIDEBUILDS>1</SLIDEBUILDS> <SLIDESCRIPT> There were various design goals around how to build an image format and what needed to be enabled within that format. First there needed to be a unified format that can be used across all Windows deployment solutions. [BUILD1] With this in mind, we developed the Windows Image Format. The WIM format eliminated the need to tie architecture with Windows Images. Historically you’ve had to manage multiple images across things like Processor types or Hardware Abstraction Layer, or HAL types. Although you still have to maintain separate images for different processor types, with the Windows Image format you can manage a single image across HAL types. There’s also been work to make sure the tools and technologies work across 32 bit and 64 bit systems. This means you can run a 32 bit pre-installation operating system and capture a 64 bit system and nothing is stored in the format itself that ties it to a specific architecture. Storing redundant data within an image uses up disk space, so the goal with the new Windows Image format was to reduce the need to store this redundant data. Ways were examined to consolidate the number of images that you’d have to manage and lower bandwidth cost associated with moving images. Finally, with the understanding that modification and servicing of images can be extremely costly, we developed tools for the Vista release to reduce these costs and allow you to modify the images without having to boot into them and recapture them. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>The Windows Imaging format provides significant benefits over the more common sector-based image formats.</TRANSITION> <TRANSITION LENGTH=2>The Windows Imaging format provides significant benefits over the more common sector-based image formats.</TRANSITION> <TRANSITION LENGTH=4>The Windows Imaging format provides significant benefits over the more common sector-based image formats.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/technet/windowsvista/evaluate/keyreas.mspx</ITEM> </ADDITIONALINFORMATION> WIM 檔

WIM 格式的優點 WIM 檔 映像 #1 映像 #3 映像 #2 映像 #4 <SLIDETITLE INCLUDE=7>Benefits of WIM Format</SLIDETITLE> <KEYWORDS>WIM, Windows Imaging format</KEYWORDS> <KEYMESSAGE>Cover some key benefits of the WIM Format</KEYMESSAGE> <SLIDEBUILDS>3</SLIDEBUILDS> <SLIDESCRIPT> File-based means there isn’t any disk or file-system structure information stored within the imaging format. All interaction with the image, such as capturing and applying the image occurs through the physical disk’s file system. [BUILD1] The first benefit of the WIM format is it is hardware-agnostic. This means that if you have many different hardware configurations, you only need one image. [BUILD2] Second, the WIM image format can store multiple images within one file making image management easier and saving disk space. A situation where you might want to have multiple images would be if you wanted to have an image that contains the Windows Vista operating system and another image that contains the organization’s core applications. You can also mark one of the images as bootable, allowing you to start a computer from a disk image contained in a WIM file. [BUILD3] Additionally, the WIM image format enables compression and single instancing, thus reducing the size of image files. Single instancing is a technique that stores only a single instance of a file even though it may be used in multiple images or in multiple locations. It eliminates duplicate files by using SHA-1 hashing where all files are hashed and duplicate files are only stored once. Also, all file streams are either compressed with LZX compression which is a very tight compression algorithm, or Xpress compression, which gives you a faster compression. You should determine which compression to use by deciding whether time or size is important. If you boot the image you probably want to use LZX compression because the tighter compression helps in situations where there are memory or bandwidth constraints [BUILD4] With a Windows XP image, you must boot the master image, add the patch, and then prepare the image again. The WIM image format allows you to service an image offline. You can add or delete certain operating system components, patches, and drivers without creating a new image, which could save hours updating an image. Additionally, unlike sector-based image formats, the WIM image format lets you install an image to partitions of any size. Windows Vista provides an API for the WIM image format called WIMGAPI that developers can use to work with WIM image files. Finally, the WIM image format allows for non-destructive deployment. This means that you can leave data on the volume to which you apply the image because the application of the image does not erase the disk's existing contents. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>By looking at the structure of the WIM format we will show how to optimize your image files.</TRANSITION> <TRANSITION LENGTH=2>By looking at the structure of the WIM format we will show how to optimize your image files.</TRANSITION> <TRANSITION LENGTH=4>By looking at the structure of the WIM format we will show how to optimize your image files.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/technet/windowsvista/expert/ximage.mspx</ITEM> </ADDITIONALINFORMATION> 映像 #1 映像 #3 映像 #2 映像 #4

WIM 映像檔案格式 標頭 檔案資源 Metadata 資源表 XML 資料 WIM 檔案 Slide Title: WIM Image Format Overview Keywords: header, file resources, metadata, resource table Key Message: There are five sections of the WIM file structure. Slide Builds: 4 Slide Script: [BUILD4] The last section of the format is the image info descriptor. This contains XML data which allows you to customize the image information using APIs. There is a default set of XML data generated and stored after the resource table in the WIM file. Slide Transition: ImageX is a command-line tool that allows you to do basic operations and manipulate a WIM file. Slide Comment: Additional Information: WIM 檔案 Metadata 資源表 XML 資料

XImage 指令 將一個映像加入 WIM 檔中 掛載映像到資料夾 (唯讀) 列出映像中的所有檔案和資料夾 卸載映像 /append <SLIDETITLE INCLUDE=7>XImage</SLIDETITLE> <KEYWORDS>XImage, WIM</KEYWORDS> <KEYMESSAGE>XImage is a command line tool for working with WIM files.</KEYMESSAGE> <SLIDEBUILDS>4</SLIDEBUILDS> <SLIDESCRIPT> XImage is a simple utility that you run from the command prompt or from Windows PE. The batch-scripting features in Windows Vista are versatile so you can script XImage to do almost everything with the image you need. XImage's core features let you capture a volume to a WIM file and apply a WIM file to a volume. You can mount an image, modify the image just like you would any file or folder on the file system, and then unmount the image. For example, you can mount an operating-system image, add device drivers, and then unmount it which saves time as opposed to rebuilding the disk image from scratch. [BUILD1] Some commands with Ximage include the append command which appends a volume image into an existing WIM file. [BUILD2] The mount command mounts an image with read-only access to the specified directory. MountRW will mount the image with read/write access. [BUILD3] The dir command allows you to list the contents of an image. [BUILD4] Once you’ve completed your work with the image file, you’ll unmount it from XImage. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1> Microsoft Windows PE 2.0 is a bootable tool that provides operating system features for installation, troubleshooting, and recovery.</TRANSITION> <TRANSITION LENGTH=2> Microsoft Windows PE 2.0 is a bootable tool that provides operating system features for installation, troubleshooting, and recovery.</TRANSITION> <TRANSITION LENGTH=4> Microsoft Windows PE 2.0 is a bootable tool that provides operating system features for installation, troubleshooting, and recovery.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/technet/windowsvista/expert/ximage.mspx</ITEM> </ADDITIONALINFORMATION> /append 將一個映像加入 WIM 檔中 /mount 掛載映像到資料夾 (唯讀) /dir 列出映像中的所有檔案和資料夾 /unmount 卸載映像

Windows PE 2.0 安裝 Microsoft Windows Vista 問題處理 修復 Slide Title: Windows PE 2.0 Keywords: Windows PE 2.0, installing, troubleshooting, recovery Key Message: Windows PE 2.0 is a bootable tool used for installation, troubleshooting, and recovery. Slide Builds: 2 Slide Script: [BUILD2] Original Equipment Manufacturers (OEMs) and Independent Software Vendors (ISVs) can use Windows PE to build customized, automated solutions for recovering and rebuilding computers running Windows Vista. For example, users could start their computers from Windows PE recovery CDs or recovery partitions to automatically reformat their hard disks and reinstall Windows Vista with the original drivers, settings, and applications. There are several benefits to using the new Windows PE 2.0. Window PE 2.0 starts quickly, is stored entirely in a computer’s memory, and can be stored on removable media. The exact size of Windows PE can vary depending on how you customize the image, but it typically consumes less than 100 MB when compressed in WIM format. You can compress Windows PE within a WIM file and run it from memory without ever decompressing it. Therefore, you benefit from compression, both when storing the image on a disk and after loading it into your computer’s memory. Although Windows PE is designed to be small, it contains much of the core functionality of Windows Vista. Because Windows PE supports Win32, most Windows applications will run in Windows PE. Windows PE also supports multithreading and multitasking, so you can run multiple tools at the same time. Windows PE can also run batch files, VBScript scripts, Windows Script Host scripts, HTML applications, and Microsoft ActiveX data objects. Because Windows PE provides RAM-based temporary space, Windows PE can run applications that require the ability to write temporary files to the hard disk even if no hard disk is available. Windows PE includes most Windows Vista drivers, and you can add new drivers to a Windows PE image. Although you can run Windows PE directly from a hard disk or removable media, you can also choose to run Windows PE directly from memory. Loading Windows PE from RAM provides additional flexibility, because you remove the Windows PE media after Windows PE has started. Therefore, you could load Windows PE from a CD, and then replace the CD with a second CD containing tools or drivers. When Windows PE runs from memory, it supports writing temporary files to the virtual RAM disk, which wouldn’t be possible with read-only media such as a CD. Slide Transition: When Windows PE runs from memory, it supports writing temporary files to the virtual RAM disk, which wouldn’t be possible with read-only media such as a CD. Slide Comment: Additional Information: http://www.microsoft.com/technet/windowsvista/deploy/winpe.mspx 問題處理 修復

與 Longhorn 伺服器整合 Longhorn Vista Slide Title: Integration with Longhorn Keywords: Longhorn, Vista Key Message: The WIM technology is integrated with Longhorn and Vista’s setup and deployment tools. Slide Builds: 0 Slide Script: The WIM technology is integrated with “Longhorn” (the code name for the new software release for Microsoft Windows Server) and Vista’s setup and deployment tools. Longhorn includes the core foundation and application programming interfaces (APIs) for server components. Longhorn supports the same imaging components as Windows Vista. With both Vista and Longhorn, the media that includes the operating system setup includes an image in the WIM image format. This replaces WINNT32. With a custom WIM image, you can plug it into setup, and setup will actually deploy your custom OEM or corporate image. WIN PE leverages the WIM format by allowing you to boot from a compressed WIM file. This reduces the space required in the RAM disk and the bandwidth requirements when you PXE-boot WIN PE from a WDS or RIS server. Windows Deployment Services, or WDS, has native support for WIM images. You don’t need to create and manage the RIS files anymore, because all the images that are stored and managed on the WDS server are WIM images. By adding the WIM file to the Windows Deployment Server, it will automatically be available for deployment in your environment. There is also an image capture utility available with WDS that will allow you to capture a reference system and publish that image back up to the WDS server. In the SMS V4 release, there is also native support for WIM images. Slide Transition: This is the same WIM format that will be released with Vista and Longhorn operating system releases. Slide Comment: Additional Information: http://www.microsoft.com/windowsserversystem/windowsserver/bulletins/longhorn/beta1.mspx

大綱 Vista 映像技術簡介 建立映像檔 編輯映像檔 部署映像檔

擷取映像 WIM 檔案 <SLIDETITLE INCLUDE=7>Image Capture</SLIDETITLE> <KEYWORDS>Image Capture, WIM, Windows PE</KEYWORDS> <KEYMESSAGE>Options for using Ximage to capture an image.</KEYMESSAGE> <SLIDEBUILDS>3</SLIDEBUILDS> <SLIDESCRIPT> The first step in capturing an image is to create the configuration to be deployed. You will configure the operating system and applications and then un SysPrep to remove the unique security identifiers, or SIDs, from the computer. You can capture the image file from Windows PE, Windows Vista, Microsoft Windows XP with Service Pack 2, Windows Server 2003 with Service Pack 1, or a customized Windows PE provided by Microsoft SMS OSD Feature Pack or Windows Deployment Services. [BUILD1] If you capture an entire installation, the best practice is to start the computer from Windows PE. Because Windows PE runs in memory, or from a CD/DVD, it ensures that no locked files or folders will be included in your installation image. Locked files or folders will cause the image capture to fail. You can also capture an image from a running version of Windows; however, you can do this only if you intend to capture individual files and folders not in use by the operating system. If you capture the installation image from a running Windows operating system, you must include the names of the locked files, or the files in use by Windows, in the exclusion list of the configuration script. It is highly recommended that you start the capture in Windows PE, though, because any capture from a running operating system might fail, due to the attempted processing of locked files or folders. [BUILD2] The WIM Format supports span-media, which allows you to split a WIM file into multiple parts and then apply the image from the parts. [BUILD3] There are several cases where you would want to split a WIM file either for bandwidth or media constraints. One example is if you need to distribute an image on a CD and the image doesn’t fit on a single CD. In this situation you can split the WIM into parts that fit on the CD. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>There are several configuration options with the image capture.</TRANSITION> <TRANSITION LENGTH=2>There are several configuration options with the image capture.</TRANSITION> <TRANSITION LENGTH=4>There are several configuration options with the image capture.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/technet/windowsvista/library/9b645b6b-7e15-484d-8dd1-fef56f22904d.mspx</ITEM> </ADDITIONALINFORMATION> WIM 檔案 WIM 檔案

映像檔擷取選項 WIM 檔案 WIMSCRIPT.INI <SLIDETITLE INCLUDE=7>Image Capture Options</SLIDETITLE> <KEYWORDS>compression, exclusion list, WIMSCRIPT.INI, append</KEYWORDS> <KEYMESSAGE>Imagining technology introduced with WIM includes compression options, exclusion lists and the ability to append an image to a WIM file.</KEYMESSAGE> <SLIDEBUILDS>3</SLIDEBUILDS> <SLIDESCRIPT> First, you can choose the type of compression for the image. These compression types are either the LZX compression or Xpress compression. Since the compression type is set at the WIM file level, you can’t mix compression types across images within your WIM or within a single WIM file. [BUILD1] You can create an exclusion list by either creating a file called WIMSCRIPT.INI, or by providing a parameter to X-image that will point to the exclusion list. The parameter is defined in the config option. [BUILD2] The exclusion list is the files that you don’t want included during your image capture. Some examples of the files you may want to exclude are the NTFS log, system volume information and the recycling bin. These types of files are relevant in a deployment environment and get regenerated when the system is specialized through sys prep. By excluding these files you save space on the image and reduce the size. [BUILD3] There is also an option with Ximage that allows you to append files to a WIM image. If you have time restraints, you can capture the image and then append files onto the WIM image at a later time. You are able to append images because of single instancing; you don’t have to re-capture files that are already in the WIM image. If the file is already in the WIM image you can add a reference to the file. To see if the file is already on the WIM image you hash the file and compare it to the set of hashes that are in the WIM file. While using append, you may notice that hashing is faster than compression. So if you have multiple versions of Windows in a single WIM file with only slight variations in those installs, then you should append those images into the single WIM image. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>This will also reduce the number of WIM files that you have to manage in your system.</TRANSITION> <TRANSITION LENGTH=2>This will also reduce the number of WIM files that you have to manage in your system.</TRANSITION> <TRANSITION LENGTH=4>This will also reduce the number of WIM files that you have to manage in your system.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM></ITEM> </ADDITIONALINFORMATION> WIMSCRIPT.INI

建立映像檔 建立壓縮映像檔 分割映像 建立排除清單

大綱 Vista 映像技術簡介 建立映像檔 編輯映像檔 部署映像檔

Imaging Filters Filter 用途 Filter 類型 WIM file system filter 編輯映像檔 <SLIDETITLE INCLUDE=7>Imaging Filters</SLIDETITLE> <KEYWORDS>Imaging Filter, WIM file system filter, WIM boot filter, WIM FS Filter</KEYWORDS> <KEYMESSAGE>There are several filters to enable the features of the WIM format.</KEYMESSAGE> <SLIDEBUILDS>3</SLIDEBUILDS> <SLIDESCRIPT> The first is the WIM file system filters. This is a filter that allows you to attach a Windows image to your local file system and then edit the image. For example, you can add drives, hot-fixes, files or audit the contents of the WIM file. [BUILD1] The second filter is the WIM boot filter. This filter is used with WIN PE to boot from a WIM image. We’ll look at this technology more later in this session. [BUILD2] To manipulate an image, you must install the Windows Imaging File System Filter, or WIM FS Filter driver. Once installed, the driver enables you to mount your image with read-only or read/write permissions, and view the included files and folders from a file management tool, such as Windows Explorer. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>Once you’ve installed the WIM file system filter, you can attach an image and edit the image.</TRANSITION> <TRANSITION LENGTH=2>Once you’ve installed the WIM file system filter, you can attach an image and edit the image.</TRANSITION> <TRANSITION LENGTH=4>Once you’ve installed the WIM file system filter, you can attach an image and edit the image.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM></ITEM> </ADDITIONALINFORMATION> WIM file system filter 編輯映像檔 WIM boot filter 由 WIM 映像檔開機 WIM FS Filter driver 掛載與檢視映像檔

映像掛載、變更與卸載 XImage /MOUNT /MOUNTRW /COMMIT WIM 檔案 /UNMOUNT 掛載的資料夾 <SLIDETITLE INCLUDE=7>Image Editing</SLIDETITLE> <KEYWORDS>mount, mountrw, commit, unmount</KEYWORDS> <KEYMESSAGE>Use Ximage to mount a .wim file for viewing or editing.</KEYMESSAGE> <SLIDEBUILDS>3</SLIDEBUILDS> <SLIDESCRIPT> To edit an image, you first need to mount the file into a mount directory. In Ximage you enter the mount command to mount it with read-only permissions or the mountrw command to mount the file with read/write permissions. [BUILD1] Once the image is attached to that mount directory, you can view the contents of the image in the mount directory. As you make changes to that image the changes are queued to a temporary directory. By default, the system temporary directory is used, but you can also customize that temporary directory through the APIs. [BUILD2] By mounting the image to the temporary directory, you can make changes to an image and then decide if you want to commit the changes. Once you have editing the image the way you want it you need to commit the image. [BUILD3] Alternatively, if you don’t want to commit those changes you can unmount the image without the commit option and all the changes that you made to the image file will be erased. It’s important to note if you’re mounting an image for read-write, you can only mount a single image within a WIM file to a specific mount point. If you want to mount an image for just read you can mount unlimited images within a WIM file. An example of when you would want to mount an image for read-only, is if you want to check the version of a file in an image. In this case, you wouldn’t need to do any editing so you can just mount the image and find the version. You can also mount from a network share or removable media. The MOUNT and MOUNTRW functionality is also exposed through the WIMGAPI APIs, so you can build custom solutions for mounting and editing images. Once you mount an image, the directory structure becomes available from a file management tool, such as Windows Explorer. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1> From the file management tool, you can review your file and folder structure, add files and folders, edit the existing files and folders, and delete any files and folders that you do not need. </TRANSITION> <TRANSITION LENGTH=2> From the file management tool, you can review your file and folder structure, add files and folders, edit the existing files and folders, and delete any files and folders that you do not need. </TRANSITION> <TRANSITION LENGTH=4> From the file management tool, you can review your file and folder structure, add files and folders, edit the existing files and folders, and delete any files and folders that you do not need. </TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM></ITEM> </ADDITIONALINFORMATION> /MOUNT /MOUNTRW /COMMIT /UNMOUNT WIM 檔案

XImage 安裝 WIM Boot Filter 掛載映像檔 檢視並修改檔案與資料夾

大綱 Vista 映像技術簡介 建立映像檔 編輯映像檔 部署映像檔

映像安裝 <SLIDETITLE INCLUDE=7>Image Installation</SLIDETITLE> <KEYWORDS>installation, wipe-and-reload</KEYWORDS> <KEYMESSAGE>Installing Windows Vista is a completely image-based process.</KEYMESSAGE> <SLIDEBUILDS>1</SLIDEBUILDS> <SLIDESCRIPT> Windows Vista ships exclusively in the WIM image format. [BUILD1] The in-place upgrade process works better than it did in Windows XP. This is because upgrading to Windows Vista is a clean installation with the migration of user settings, documents, and applications from an older version of Windows. The in-place upgrade process is also called wipe-and-reload. With previous versions of Windows, imaging could only be used for new Windows installations since deploying an image would overwrite the computer's hard disk. To upgrade a user's computer, administrators had to copy the user's files and settings to a different computer, and then restore the files and settings after deploying the image. Windows Vista includes nondestructive imaging using the WIM image format, which copies files and settings to a reserved portion of the computer's hard disk before deploying the Windows Vista image. After the Windows Vista image is deployed, Windows Vista migrates the files and settings and then restores the portion of the computer's hard disk that had been reserved. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>Overall, migrating to Windows Vista is much faster than migrating to Windows XP.</TRANSITION> <TRANSITION LENGTH=2>Overall, migrating to Windows Vista is much faster than migrating to Windows XP.</TRANSITION> <TRANSITION LENGTH=4>Overall, migrating to Windows Vista is much faster than migrating to Windows XP.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/technet/windowsvista/expert/ximage.mspx</ITEM> <ITEM>http://www.microsoft.com/technet/windowsvista/evaluate/overvw.mspx</ITEM> </ADDITIONALINFORMATION> WIM 檔案

Windows System Image Manager 偵測套件 處理安裝路徑 簡化介面 <SLIDETITLE INCLUDE=7>Windows System Image Manager</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE>Windows Setup Manager simplifies setup configuration by using a single comprehensive unattend.xml file.</KEYMESSAGE> <SLIDEBUILDS>2</SLIDEBUILDS> <SLIDESCRIPT> For example, unattend.txt and sysprep.inf were used during the sysprep phase of setup, while ooboeinfo.ini was used to manage the out-of-box experience script. Managing and maintaining these files required administrators to use a number of different tools and often enter duplicate information in each file. [BUILD1] Windows Vista simplifies this process with a new setup manager that uses a single configuration file, called unattend.xml, for all stages of setup and initial system configuration. The use of a single file means that administrators do not need to worry about synchronizing the contents of multiple config files, and have a single definitive location where all aspects of the windows setup process can be controlled. [BUILD2] Windows Vista also includes a powerful new tool, the System Image Manager. The System Image Manager replaced the Windows XP Setup Manager, and is used to simplify the process of creating and editing the unattend.xml file even further. The System Image Manager can read the contents of an existing unattend.xml file, and use this data to automatically create setup configuration sets which include all the components referenced by your configuration file. This means that administrators do not need to worry about resolving components paths and making sure that all setup components are in the right places, since the System Image Manager takes care of these functions automatically. Since the Image Manager handles component paths, this means that unattend.xml files are now portable. You can access your configuration file from any location without needing to edit the file paths that it contains. The System Image Manager also provides simple graphical or command-line interfaces for entering license data, specifying setup steps, and defining initial settings. Together, these functions mean that the System Image Manager replaces the disparate suite of tools needed to configure previous versions of Windows Setup with a single, powerful utility. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=4>Let’s look at a demonstration of how this works.</TRANSITION> <TRANSITION LENGTH=2>Let’s look at a demonstration of how this works.</TRANSITION> <TRANSITION LENGTH=1>Let’s look at a demonstration of how this works.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/middleeast/windowsvista/basics/deployment.mspx</ITEM> <ITEM>http://www.microsoft.com/technet/windowsvista/evaluate/feat/deplovw.mspx</ITEM> </ADDITIONALINFORMATION> Windows 安裝設定 單一的 .xml 檔案 簡化客製化所需的動作 Unattend.xml

Windows System Image Manager <SLIDETITLE INCLUDE=7>Windows System Image Manager</SLIDETITLE> <KEYWORDS>Windows System Image Manager, unattend.xml</KEYWORDS> <KEYMESSAGE>Use the Windows System Image Manager to view image file</KEYMESSAGE> <SLIDEBUILDS>0</SLIDEBUILDS> <SLIDESCRIPT> This GUI tool is a similar experience to previous versions, but there is a new answer file for Vista. [BUILD1] With the Windows System Image Manager you can create and edit the unattend.xml file. Additionally, unattend.xml can be applied offline or online. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=1>Also in the Windows System Image Manager, you can add or modify optional components such as languages, service packs, or drivers.</TRANSITION> <TRANSITION LENGTH=2>Also in the Windows System Image Manager, you can add or modify optional components such as languages, service packs, or drivers.</TRANSITION> <TRANSITION LENGTH=4>Also in the Windows System Image Manager, you can add or modify optional components such as languages, service packs, or drivers.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM></ITEM> </ADDITIONALINFORMATION> 編輯 unattend.xml Answer File

System Image Manager 掛載 Windows 映像 設定 IE 選項 設定磁碟分割

以映像為基礎的部署 離線階段 第一次開機 OOBE script Windows PE 線上階段 測試 SysPrep 授權註冊 初始化磁碟 <SLIDETITLE INCLUDE=7>Image Based Deployment</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE>This is an overview of the image-based deployment process.</KEYMESSAGE> <SLIDEBUILDS>4</SLIDEBUILDS> <SLIDESCRIPT> The image-based managed deployment process begins with the offline phase. During this phase, administrators test new system configurations and build images for these new configurations. The images are stored on either Windows Deployment Service servers, or in some cases on removable media. These images should contain applications and configuration settings that are common to enterprise systems, and typically the number of deployment images should reflect the number of typical computer configurations in the digital infrastructure. For example, if there are two standard desktop configurations in an enterprise, generally there will be two deployment images. [BUILD1] After the images have been built, the deployment rollout process starts with the Windows PE phase. Computers that are targeted for deployment load and boot the Windows PE environment, either from supplied removable media or from a central Windows PE image on the deployment server using the built-in network pre-execution environment. Windows PE then performs the core system initialization steps, like preparing the target drive for Windows Vista installation. Once the disk preparation step is complete, Windows PE applies the specified deployment image to the target computer. [BUILD2] The third step in the deployment process is the online setup phase. During this phase, Windows Setup reads configuration information from the unified unattend.xml file, and applies these settings to the local system. During this phase, selected Windows components are installed and applications with licensing information stored in unattend.xml are registered. [BUILD3] After online configuration, the target computer boots a local copy of Windows Vista for the first time. The first boot triggers the SysPrep process, which generates unique identification information for the computer. [BUILD4] Finally, after first boot, the OOBE scripts are executed. These scripts prompt the user to accept any applicable license agreements and to register their system. At this point, the new Windows Vista installation is deployed and fully functional. 離線階段 測試 建立映像 Windows PE 初始化磁碟 套用映像 OOBE script 授權註冊 使用者設定 線上階段 設定 Unattend.xml 第一次開機 SysPrep Unique ID

以映像為基礎的升級 套用新系統 硬體特殊處理 還原使用者資料 安裝非標準驅動程式 刪除舊系統 測試硬體 離線階段 Windows PE 線上階段 第一次開機 OOBE script <SLIDETITLE INCLUDE=7>Image Based Upgrade</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE>This is an overview of the image-based upgrade process</KEYMESSAGE> <SLIDEBUILDS>2</SLIDEBUILDS> <SLIDESCRIPT> In many cases, deployment images can be created that contain the same set of applications and settings used most commonly in an enterprise. These applications are applied to the target system along with the WIM image, and the new image can be installed on an automatically created secondary partition. Optionally, the old system can be captured as a WIM image and stored for easy restore. [BUILD1] Even if required device drivers do not ship with Windows Vista, typically drivers for hardware devices that are commonly used in an enterprise can also be packed into the WIM image and automatically installed during the deployment process. However, in the case of an upgrade some legacy systems may make use of non-standard hardware that is not commonly used in the computing environment. In these cases, after setup is complete administrators will need to install these custom drivers and test the non-standard devices. In many cases, this can be accomplished through a centralized management system like Microsoft SMS. [BUILD2] Next, user data is copied from the old system to the new environment. Since it is possible to automatically install Windows Vista on a separate partition or to store the existing system as a WIM image, copying user data can be accomplished locally and quickly. If user data is consistently stored in a particular location, like the My Documents folder, the process of migrating this data can also be automated. Finally, the old system partition or image is deleted, freeing additional disk space for Windows Vista. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=4>The Windows Vista upgrade process offers a number of important enhancements from previous versions of Windows.</TRANSITION> <TRANSITION LENGTH=2>The Windows Vista upgrade process offers a number of important enhancements from previous versions of Windows.</TRANSITION> <TRANSITION LENGTH=1>The Windows Vista upgrade process offers a number of important enhancements from previous versions of Windows.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>Customizing and Servicing Windows Vista Images</ITEM> </ADDITIONALINFORMATION> 硬體特殊處理 安裝非標準驅動程式 測試硬體 套用新系統 還原使用者資料 刪除舊系統

安裝 Windows Vista 或檢測安裝問題 Pre-Boot Execution (PXE) 環境 Windows PE 2.0 安裝 Windows Vista 或檢測安裝問題 Windows 預載環境 <SLIDETITLE INCLUDE=7>Windows PE 2.0</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE>Windows Preinstallation Environment 2.0 is a lightweight, powerful boot environment for installing or troubleshooting Windows Vista.</KEYMESSAGE> <SLIDEBUILDS>4</SLIDEBUILDS> <SLIDESCRIPT> The Windows Preinstallation Environment, or WinPE, is a bootable tool that provides a lightweight, powerful, and flexible environment for installing, troubleshooting, and recovering Windows Vista. The new version of Windows PE that ships with Vista replaces the old MS-DOS setup environment, and offers numerous advantages over both DOS and previous versions of Windows PE. [BUILD1] A typical Windows PE image occupies less than 100MB of disk space, which means that it can easily be stored on removable media. Unlike other types of WIM images, which must be copied to a hard disk before they can be booted, Windows PE can boot directly from removable media, and in many cases can be loaded entirely in RAM. [BUILD2] Enterprises will appreciate Windows PE because it can also be easily loaded from a deployment server, using the built-in Windows pre-boot execution environment, or PXE. In this scenario, when a new computer is connected to the network, the PXE client connects to a Windows Deployment Service server and downloads the Windows PE image to the local machine. The downloaded Windows PE image can be customized with drivers and configuration scripts appropriate for a specific computing environment, providing a platform for a highly automated deployment process. Pre-Boot Execution (PXE) 環境 部署目標 可移動式媒體 部署伺服器

Vista 升級功能的加強 乾淨的安裝 升級報告 錯誤自動還原 <SLIDETITLE INCLUDE=7>Vista Upgrade Enhancements</SLIDETITLE> <KEYWORDS></KEYWORDS> <KEYMESSAGE>Windows Vista offers a more robust upgrade process than previous versions of Windows.</KEYMESSAGE> <SLIDEBUILDS>2</SLIDEBUILDS> <SLIDESCRIPT> One of the most important ways in which the Vista upgrade process is different is that it actually uses a clean install model for upgrading existing systems, instead of a merge model. This change is made possible by the image-based install process. Since the older system can be stored as a WIM image, it is no longer necessary for the upgrade process to make ad-hoc decisions about how to treat existing applications and data. Instead, the new environment is installed cleanly, and then existing settings, software and data can be migrated systematically into the new environment. [BUILD1] To help manage the upgrade process, Windows Vista also automatically generates a comprehensive upgrade report. This report contains data on how existing settings have been interpreted, which drivers have been applied, and any errors encountered during installation. The upgrade report allows administrators to see the upgrade status of a computer at a single glance, rather than sorting through event logs or waiting for errors to occur at runtime. [BUILD2] Finally, Windows Vista includes the ability to automatically roll back an upgrade in the event of a critical failure. With previous versions of Windows, a serious error during the upgrade process could mean that a machine needed to be rebuilt from scratch. Using the image-based setup process however, the old system is stored as a WIM file so that in case of a problem, the old environment can be quickly and completely reinstalled. Enhancements like these make upgrading to Windows Vista a safe and reliable process, without the risks of traditional operating system upgrades. </SLIDESCRIPT> <SLIDETRANSITION> <TRANSITION LENGTH=4>These enhancements are also designed to integrate seamlessly with a number of management tools.</TRANSITION> <TRANSITION LENGTH=2>These enhancements are also designed to integrate seamlessly with a number of management tools.</TRANSITION> <TRANSITION LENGTH=1>These enhancements are also designed to integrate seamlessly with a number of management tools.</TRANSITION> </SLIDETRANSITION> <COMMENT></COMMENT> <ADDITIONALINFORMATION> <ITEM>http://www.microsoft.com/technet/windowsvista/deploy/depenhnc.mspx</ITEM> </ADDITIONALINFORMATION> 升級報告 錯誤自動還原

安裝 WIM file system filter Read BCD file (boot.wiw) 掛載 boot.sdi 安裝 WIM file system filter Slide Title: Boot from WIM Keywords: WIM, boot.wiw, BCD file, boot.sdi, WIM file systems filter Key Message: You can boot directly from the WIM image file. Slide Builds: 4 Slide Script: [BUILD4] Then the boot process continues. When the operating system comes up and the kernel initializes, we load the WIM file systems filter, and then all subsequent reads to that WIM file are handled through that filter. The filter manages the mapping between all file requests from the system to the underlying WIM file, which enables us to boot from a WIM file in these WIN PE scenarios. Slide Transition: Although the primary purpose of Windows PE is to install Windows Vista, you can also use Windows PE for troubleshooting. Slide Comment: Additional Information: 將開機 WIM 附加到 boot.sdi 繼續啟動流程

總結 新的 WIM 映像技術 新的 WIM 映像工具 簡化部署

參考資訊 TechNet http://www.microsoft.com/taiwan/technet/default.mspx 聖哥的資訊站 teacher.allok.com.tw KEY MESSAGE: For more information on this session see these web sites. SLIDE BUILDS: SLIDE SCRIPT: For more information on this session see the main TechNet Web site at www.microsoft.com/technet Additional resources to support this Session page can be found at www.microsoft.com/technet/tnt1-97 SLIDE TRANSITION: For additional information on the technologies used, see these links.

Questions and Answers 請不要忘了填一下問卷 接下來即將舉行的線上課程: http://www.microsoft.com/taiwan/technet /webcast/online.mspx