![]() This base OS component is language independent and a subset of all the Vista product editions. At the lowest level is what Microsoft calls the base OS component-or MinWin-which is about 95 percent of the total Vista code base. Vista's componentized nature also gives Microsoft and its partners many new capabilities when creating various Windows versions. In contrast to OSes on embedded devices, which are generally created once and then never changed, desktop OSes are often upgraded and changed by end users and applications. With a componentized approach, end users, IT administrators, and PC makers will be able to easily specify which applications and services are installed with each Windows version.īecause desktop OSes have more dependencies than OSes on embedded devices, Vista's customization features aren't as fine-grained as those of Windows XP Emdedded, which literally lets device makers specify every single feature. Vista is also internally componentized, making it easier to choose exactly which applications and features will be installed.Ĭomponentization has numerous benefits compared with previous development approaches, in which each product version heaped new features on top of the existing code base. (Technically, there are actually two images: one for 32-bit versions and one for 圆4 versions.) The product key you use during installation determines which edition is installed from the image and which features are available to the user. Furthermore, Microsoft is distributing only one Vista image instead of a different image for each product edition. You can edit a Vista image live and can easily create custom install images. Vista is deployed via a file-based image - similar to an ISO or virtual hard disk file - instead of a complex directory structure of files. But if you're an IT administrator who'll need to deploy Windows Vista either now or in the future, you've got a lot to learn. New capabilities, such as offline servicing and the ability to create just one install image for multiple hardware configurations, make Windows deployment easier than ever. Paulįor the first time since Windows NT, Microsoft has dramactically improved how users, enterprises, PC makers, and OEMs configure, install, and deploy Windows. Read more about WindowsPE.This guide to corporate deployment of Windows Vista was originally published as the cover story of the January 2007 issue of Windows IT Pro Magazine. I can tell you that the 20 or so folks in the room with me at the TechEd conference, all of whom were planning on moving their companies to Vista, were suitably impressed and interested in that particular tool. I have asked an e-mail buddy of mine and BartPE expert to inspect ImageX/WindowsPE and send me his thoughts and will report back when I hear from him. It is used in conjunction with WindowsPE, which is basically Microsoft's answer to BartPE (Microsoft built its own "Preinstalled Environment" imaging tool so that it could offer its own "Microsoft supported" tool.). ImageX is a command-line disk imaging tool that lets you create a single image of a Vista implementation, and then deploy that image to the hundreds of PCs that you need to cutover, regardless of the HAL (more or less). This post is dedicated to ImageX, the tool that the Microsoft "IT evangelist," Chris Avis, spent a good deal of time demonstrating. From Microsoft Subnet editor Julie Bort: So, I promised that I would write about the two other cool tools that I saw during a Microsoft TechEd event a few days ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |