Business Value Launch 2006 3/27/2017 2:27 AM © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Il deployment in azienda

Agenda Considerazioni sul deployment I tool di deployment di Vista Il deploy di Windows Vista

Agenda Considerazioni sul deployment Uso dei tool di deployment di Vista Il deploy di Windows Vista The deployment process is associated with a number of risks and complexities. A poorly planned or executed deployment of new software systems can result in costly delays, loss of enterprise functionality, and numerous administrative headaches. In the first part of this session, we will talk about some of the problems traditionally associated with deploying software systems and how a managed deployment process can help reduce these risks. Next, we will look at a number of new technologies in Windows Vista that can help administrators manage their deployment process. These technologies include tools for creating and managing Vista deployment configurations, as well as seamlessly migrating existing applications, settings, and user data. Finally, we’ll examine the deployment process itself. We’ll see how the new image-based Windows Vista setup works and cover management tools that are available to administrators for automating the installation of Windows Vista. By the end of this session, you should have a better understanding of the powerful technologies in Windows Vista that can facilitate your enterprise deployment, as well as the management tools that can increase the reliability and efficiency of how new systems are rolled out in your enterprise digital infrastructure. -------------------------------------------------------------------------------------------------------------- In this session, we will cover a number of topics related to deploying Windows Vista. We’ll look at the advantages of using a managed deployment process, and how automating your Windows deployment can increase the reliability and manageability of your digital infrastructure while lowering costs. We will examine the new imaging format and the new image management tools developed for Windows Vista to simplify your deployment process. We’ll also talk about the Windows Preinstallation Environment, which is the platform for installing Windows Vista. An understanding of Windows PE will not only help you manage your Vista deployment, but it will also serve as a valuable resource for troubleshooting and recovering Windows Vista systems. To help streamline your Vista deployment, Microsoft provides a number of tools and wizards. In this session, we will see a few of the more important tools, like the Application Compatibility Toolkit, which helps ensure that your legacy applications continue to function correctly with Windows Vista. Finally, we will cover some of the deployment management systems that can help administrators in enterprise environments to automate the deployment of Windows Vista.

Considerazioni sul deployment Sfide poste dal deployment Vantaggi del deployment gestito Diversità dei sistemi Hardware Software Ruoli Costi di amministrazione Configurazione Test Gestione Migrazione dei dati Applicazioni Dati degli utenti Impostazioni del sistema Consistenza Numero limitato di configurazioni Standardizzazione dei sistemi Gestibilità Centralizzazione Automatizzazione Affidabilità Test dei sistemi Riprisistino dei sistemi Typically, the digital infrastructure of an enterprise includes a diverse set of both hardware and software components. Computers that play different roles within an enterprise may have vastly different configurations, and this diversity must be taken into account by administrators during the deployment process. In many cases, several different upgrade approaches must be taken, and different computers will require distinct sets of drivers, applications, and computer settings. All of these factors add complexity to the process of deploying new systems. [BUILD1] This complexity means that deploying systems entails significant costs, both in terms of time and administrative expertise, for many enterprises. Typically, administrators need to configure each desktop configuration and role separately. Each new configuration must be tested for compatibility and interoperability, both with legacy systems and in the new environment. Finally, managing this diverse set of configurations creates an ongoing administrative challenge. [BUILD2] During the deployment process, administrators are confronted with the need for seamless data migration. Existing applications, user data, and system settings must be moved from the old environment to the new one. In many cases, simply moving data between environments is not enough, since configuration settings will function differently in each system. Loss of data or system functionality during migration can result in costly delays or loss of productivity. By standardizing and rationalizing the deployment process, administrators can reduce the overall complexity of the digital environment in an enterprise. Managed deployment systems define a set of common configurations that can be applied to multiple computers. With a smaller number of desktop and server configurations, administrators can more effectively set up and manage enterprise systems, and can reduce the number of exceptions and hidden settings that can cause interoperability or upgrade problems. Managed deployment can also decrease administrative costs by centralizing and automating the deployment process. Typically, managed deployment systems rely on deployment servers to consistently update the computers in an enterprise. Using a deployment server, administrators only need to build a single version of each configuration that can be automatically rolled out to individual workstations, rather than spending hours beside each desktop. Finally, managed deployment can increase the reliability of computers within an enterprise by simplifying the process of testing new configurations and restoring damaged systems. Since managed deployment uses a single canonical image to update multiple desktops, administrators only need to test each new configuration once rather than individually troubleshooting each desktop. If a system is damaged, its configuration is stored in a centralized location and can be redeployed by administrators, often without even leaving their desks.

Scenari di deployment Server WDS Nuovi sistemi Upgrade di sistemi In general, managed deployment makes use of a central deployment server to simplify and automate the deployment process. Administrators use the deployment server to create and manage system configuration definitions. After these configuration definitions are tested in a controlled environment, they are applied to computers throughout the enterprise. Usually, these new deployment configurations can be applied in one of three ways. [BUILD1] In the first of these scenarios, the configuration is used to build a new system. This would be the case when a new computer is being added to the enterprise network, or when administrators decide to completely overwrite any existing data on a computer and replace it with the new configuration. The key element of the new system scenario is that no data is moved between the existing environment and the new environment. For that reason, this scenario is sometimes referred to as a wipe-and-load deployment. [BUILD2] A second deployment scenario is the system upgrade approach. In this case, user data, applications, and configuration settings from the existing system environment are migrated to the new system. In some instances, files can simply be preserved across the two systems. In other cases, applications must be updated or settings must be reapplied to take effect in the new system. For many administrators, this is the most commonly faced deployment scenario, since most enterprises purchase new software more often than they purchase new hardware. This can also be the most challenging deployment scenario because of the complexities involved in moving data and applications between systems without causing a loss of functionality. [BUILD3] A third deployment scenario is the side-by-side approach. In this scenario, the new system is installed alongside the existing system without replacing or modifying it. This is a good deployment approach in cases when it is important for administrators to preserve the functionality of existing systems while testing newer systems, or when performing a full upgrade is not possible due to limited compatibility. Upgrade di sistemi Affiancamento di sistemi

Agenda Considerazioni sul deployment I deployment di Vista Il deploy di Windows Vista

Novità del deployment in Vista Modularizzazione Separazione dei componenti Device driver Lingue Componenti aggiuntivi Definizioni indipendenti Building block Windows imaging Tool potenti File configurabili Uso flessibile Image base installation WDS SMS Vista is built out of modular components, which means that device drivers, service packs, and optional 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, which reduces the number of versions that an organization needs and results 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. [BUILD2] Windows Vista is also supported by a broad set of Microsoft deployment solutions, such as Microsoft Systems Management Server (SMS), the Microsoft Solution Accelerator for Business Desktop Deployment (BDD), and Windows Deployment Services (WDS). Together, these technologies can simplify and streamline the process of managing your deployment needs in virtually any enterprise environment. Microsoft Deployment Solutions www.microsoft.com/technet/windowsvista/deploy

Windows imaging Formato WIM per i file immagine Tool di cattura dello stato dei sistemi Possibilità di immagini multiple in un file WIM Indipendenza delle immagini dall’hardware WIM files are used to store installable instances of Vista, and can also contain detailed system configuration information, such as device drivers, applications, and even user data. The Windows Vista setup and installation process is image-based, and images can be used to deploy pre-configured installations of Vista, either manually or using an automated process. Since WIM files are compressed, their small size makes them portable and easy to store. [BUILD1] You can capture WIM files from the running or offline system state of an existing Vista installation. This means that for a bulk deployment, you can configure a single Vista desktop with the applications and settings used most frequently in your enterprise, and then create a WIM file from this computer. The WIM file can then be applied to multiple desktops. It’s also possible to capture WIM files based on a computer’s local system. This is convenient for single-computer upgrades or migrations, since the current system state can be stored and retrieved locally, instead of moving this data to and from a server. [BUILD2] Each WIM file is also capable of containing multiple system images and configurations, increasing manageability and reducing the overall number of deployment files that need to be administered and stored. This is an important feature, because typically, administrators in an enterprise will need to deploy several configurations that have many elements in common, but each will contain a few differences. For example, all desktops in an enterprise might require the latest version of Windows and Microsoft Word, but only some desktops also require a legacy database application. Traditionally, to automatically deploy these configurations, administrators would need to create two different image files, one with the legacy database application and one without this application. Using the WIM format, administrators only need to create a single file and then create a new configuration within the file containing the legacy application. Any files used in common between the two configurations, like core Windows files and shared applications, are not duplicated. [BUILD3] Another important enhancement in the WIM file format is that WIM files are hardware-independent. WIM is a true image-based format, which does not store any disk or file-system structure information. This means that images can be applied regardless of whether the target disk configuration matches the disk configuration of the source system. WIM files also do not store processor or platform information, so the same image can be applied to both 32-bit and 64-bit processor systems. Hardware independence helps administrators limit even further the number of image files that need to be stored and managed. Vista also ships with a set of powerful tools for creating and manipulating WIM files.

Formato WIM Header Risorse file FILE WIM Metadati Tabella risorse firma, dimensione, versione, GUID, lista parti, indice di boot Risorse file Una per ogni file in blocchi di dati FILE WIM There are five sections of the WIM format structure. The first section is the header, which is a signature that is used to identify WIM files. The header contains a signature, a size, a version, and a GUID that allows us to uniquely identify that WIM image. There is also a part list, that lists the separate parts of an image if you split the WIM file. Also, if the WIM file has been split, there is a boot index. The boot index is used when you boot from a WIM file, which we’ll show later. [BUILD1] After the header, file resources are stored as data blocks. There is a file resource for every file stored in the WIM image. [BUILD2] Next, the WIM image format stores metadata. There is a metadata block for each image stored in the WIM file. The metadata contains the entire directory structure of the image and any file names that are contained in the image. This includes all the file attributes, the hard links, the reparse points, the streams, and any file system attribute that was captured from the volume image. The metadata ensures that when the image is applied back to a system it inherits all of the file system attributes that it had on the source computer. [BUILD3] After the metadata section of the WIM file, there is a resource table. The resource table contains references to attributes of the image and is used for a file lookup within the WIM file. [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. Metadati Un blocco per ogni immagine: struttura dir, nomi file, attributi, reparse point, stream, hard link Tabella risorse Riferimenti (hash) alle risorse, usati per lookup nell’immagine Dati XML Informazioni di descrizione, personalizzabili

WIMGAPI fornisce funzioni per estendere/creare tool di imaing ImageX Appende l’immagine di un volume ad un file WIM Cancella l’immagine di un volume da un file WIM WIMGAPI fornisce funzioni per estendere/creare tool di imaing Elenca il contenuto di un volume in un file WIM ImageX 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 ImageX to do almost everything with the image you need. ImageX'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 ImageX 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 ImageX. To support these systems, the powerful imaging functions of Windows Vista are available through an API called WIMGAPI. WIMGAPI is distributed and documented as part of the Microsoft Corporate Deployment Kit, and it allows developers to write custom applications for manipulating and deploying WIM files. Some of the basic functions included in WIMGAPI are listed on this slide, and include calls for creating, capturing, and applying WIM files. Using this API, enterprises can develop custom applications for integrating the new imaging capabilities of Vista into their enterprise infrastructure. ====================================== DEMO - ImageX cd \revolution\Vista-Install-source ImageX /? ImageX /info INSTALL.WIM ImageX /mount INSTALL.WIM 1 c:\Revolution\mount ImageX /unmount c:\revolution\mount Suddivide un file WIM per la scrittura su CD Monta un’immagine su una directory (RO – RW) anche da share di rete e device rimovibili Termina il mount di un’immagine con o senza commit delle modifiche

Windows PE 2.0 WIM file di meno di 100 MB salvabile su device rimovibili (CD, USBKey,...) Avviabile direttamente dai device rimovibili in molti casi completamente caricabile in RAM Caricabile da server di distribuzione via PXE Contiene le funzionalità base di Vista Multithreading e multitasking Contiene la maggior parte dei driver di Vista Possibile aggiungere driver all’immagine WinPE Usabile come tool per troubleshooting 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 100 megabytes 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 computer. 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. [BUILD3] Although Windows PE is designed to be small, it contains much of the core functionality of Windows Vista, so 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. These capabilities can save time and resources during the installation process, and allow administrators and developers to write scripts or applications to perform customized deployment and configuration steps. If Windows Vista includes drivers for your computer hardware, your hardware will probably work with Windows PE, too, because Windows PE includes most Windows Vista drivers. You can also add new drivers to a Windows PE image. In enterprise environments, you could add every core networking and mass storage driver required by any computer in your organization to a single Windows PE image so that the image will work with any of your computers. [BUILD4] The primary purpose of Windows PE is as a deployment tool for Windows Vista. However, the features and flexibility of Windows PE mean that it is also a powerful resource for troubleshooting Windows. Since Windows PE can be run in RAM and booted from a network server, it allows administrators to diagnose critical hardware and software failures, replace critical system files, or recover data from a damaged system. Other utilities include built-in disk partitioning tools, user database management tools, and network configuration commands. In short, Windows PE provides administrators with a complete suite of powerful utilities, even before Windows Vista is fully deployed.

Processo di boot da WIM Supportato solo per immagini WinPE e abilitato dal filtro WIM File System Lettura file BCD (Boot.wiw) Mount di boot.sdi Attacco di Boot WIM a boot.sdi Continua processo di boot filtro WIM FS Caricamento The boot option is only supported with WIN PE images and is enabled with the WIM file system filter. The WIM boot filter does not support rights, which is why WIN PE is supported in this case. WIN PE can run in a read-only environment, whereas operating systems like Vista or XP do not run in these environments. In the process of booting from the WIM image, there is a a BCD file and a source directory that contains a boot.wiw file. The boot.wiw file is a WIN PE image that contains setup. [BUILD1] First, the boot manager reads the RAM disk options from the BCD, which is preconfigured on the media. [BUILD2] There is also a boot directory that contains a boot.sdi file. After the boot manager reads the RAM disk options, it mounts that empty RAM disk or boot.sdi file into memory. [BUILD3] Once the boot.sdi file is in memory, the Boot WIM will attach to it. [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. ====================================== DEMO - WinPE Avviare PGM-DC01 e PGM-SRV01 cd "c:\Program files\Windows AIK\Tools\PETools\" copype.cmd x86 c:\Revolution\WinPE-x86 md c:\Revolution\WinPE-x86\ISO\Tools copy "c:\Program files\Windows AIK\Tools\x86\imagex.exe" c:\Revolution\WinPE-x86\ISO\Tools oscdimg -n -bc:\Revolution\WinPE-x86\etfsboot.com c:\Revolution\WinPE-x86\ISO c:\Revolution\WinPE-x86-new.iso Fare boot di client con WinPE

Cattura delle immagini Configurare il computer da cui ricavare l’immagine Eseguire Sysprep per rimuovere riferimenti unici Catturare l’immagine con ImmageX Scegliere compressione tra LZX e Xpress Appendere a WIM esistente o creare nuovo WIM Da WinPE: preferibile perchè non ci sono file bloccati Da WinXPS-P2/Win2003-SP1/Vista: ci sono file in lock  inserire in lista di esclusione con NTFS.log, Recycle, swap,...(WIMSCRIPT.INI) Suddividere l’immagine (se necessario) 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 use 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 should 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, however, 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. For example, if you needed to distribute an image on a CD and the image didn’t fit on a single CD, you could split the WIM into parts that fit on the CD. ---------------------------------------------------------------------------------------------------------------------------------------------------------------- First, you can choose the type of compression for the image. These compression types are either the LZX compression or Xpress compression method. 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. 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. The exclusion list is the list of 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 Recycle Bin. These types of files are relevant in a deployment environment and get regenerated when the system is specialized through Sysprep. By excluding these files, you save space on the image and reduce the size. There is also an option with ImageX 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 recapture 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, you should append those images to the single WIM image. ====================================== DEMO - Cattura di immagini Net use * \\192.168.1.104\images /user:administrator D:\tools\ImageX /capture c: z:\WinXP.wim “WinXP”

Modifica dell’immagine Directory di mount ImageX /MOUNT /MOUNTRW /COMMIT /UNMOUNT To edit an image, you first need to mount the file into a mount directory. In ImageX, you enter the mount command to mount it with read-only permissions, or you enter 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. 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 edited 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 that 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. For example, if you want to check the version of a file in an image, 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. File WIM

Agenda Considerazioni sul deployment Uso dei tool di deployment di Vista Il deploy di Windows Vista

Deploy basato su immagine The image-based 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. 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 the first boot, the OOBE scripts are executed. These scripts prompt the user to accept any applicable license agreements and to register his or her system. At this point, the new Windows Vista installation is deployed and fully functional. 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. 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, such as Microsoft SMS. 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. Offline Test Cattura immagine Windows PE Prepara disco Applica immagine Online Lettura impostazioni da Unattend.xml Installazione componenti e registrazione applicazioni Primo boot SysPrep Nuovo SID OOBE Registrazione Configurazione utente

Windows System Image Manager Riconoscimento dei package Gestione dei path di installazione Interfaccia semplice 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 configuration files, and they 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 that include all the components referenced by your configuration file. This means that administrators do not need to worry about resolving component paths and making sure that all setup components are in the right places—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. Unattend.xml Windows Setup File .xml unico Personalizzazione semplificata

Impatto sul deployment 3/27/2017 2:27 AM File XML Unattend.txt è ora Unattend.xml Sysprep.inf è ora Unattend.xml WINBOM.INI è ora Unattend.xml CMDLINES.TXT è ora Unattend.xml Notepad non è più il tool di editing preferenziale USMT ora usa XML in luogo dei file INF Indipendenza da HAL Una sola immagine può supportare tutti l’hardware Non c’è supporto per hardware non-ACPI © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Upgrade in posto È un’istallazione “pulita” di Windows Vista Copia dei dati utenti e delle applicazioni in una porzione dedicata del disco Applicazione dell’immagine Ripristino di applicazioni e dati utente Cancellazione della porzione riservata del disco 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 remaining intact. The in-place upgrade process uses a clean install and then retains the environment of the old operating system, including applications and data settings. With this approach, you can push nondestructive images to your desktops. 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.

Application Compatibility Toolkit Run level corretto One of these features is a new set of account privileges, called Protected Administrator (PA) accounts. With Protected Administrator accounts, users with administrative rights actually log in to an account with limited privileges, but can run applications with full administrative privileges when necessary. By using Protected Administrator accounts, Windows Vista prevents unauthorized processes or applications from making critical system changes. Because of these new security measures, in some cases, legacy applications may not run correctly in Windows Vista with default settings. To help administrators make sure that their critical legacy applications continue to function, Microsoft has provided a new version of the Application Compatibility Toolkit. [BUILD1] The Application Compatibility Toolkit can inspect your Windows Vista system and identify applications that may not run correctly with default Vista security settings. Information about these applications is stored in a local database, along with recommendations about appropriate security settings. [BUILD2] Administrators can then review the contents of their local database and authorize each application to run with the security privileges it needs in order to function correctly. After an application has been added to the database and authorized by an administrator, Windows Vista will run that application with appropriate settings. By using the Application Compatibility Toolkit, administrators can deploy Windows Vista without disrupting the functionality of their existing enterprise software. Database Applicazioni

Virtual PC Virtual PC è e sarà liberamente scaricabile da Internet Chi ha Software Assurance ha la possibilià di eseguire in VPC su Windows Vista fino a quattro istanze di sistemi operativi legacy senza costi aggiuntivi

Wizard “Files and Settings Transfer” Cavo USB Media rimovibili Rete If users cannot access their e-mail and saved files, or need to reconfigure the new system to meet their day-to-day needs, they are not able to fulfill their roles. To help administrators make sure that user data is moved seamlessly between systems, Microsoft has provided a wizard for transferring files and settings from one computer to another. [BUILD1] The Files and Settings Transfer Wizard is a system that can automatically migrate most user data and settings between computers. The wizard can function over a network, using a direct USB cable connection between computers, or by copying data to removable media. This flexibility means that the Files and Settings Transfer Wizard is a practical choice for migrating data in most small to midsize enterprise environments, and requires no special hardware or software. [BUILD2] The transfer tool is capable of migrating system settings, user e-mail, files, favorites, and application settings with virtually no hands-on administrative cost. Instead, an easy-to-use wizard walks users through the process of data migration, reducing demands on your IT staff. Impostazioni di sistema E-mail File Favorites

Windows Deployment Services 3/27/2017 2:27 AM Soluzione end-to-end per eseguire installazioni “pulite” Da “metallo nudo” Reinstallazione di macchine Deployment di Windows Vista, Longhorn Server, Windows XP, Win2K3 e Win2K Supporto pieno per immagini sysprep (in formato WIM) Una nuova applicazione lato client rimpiazza OSChooser Opzioni di boot: PXE boot e non-PXE boot Integrazione con Active Directory © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Windows Deployment Services 3/27/2017 2:27 AM Uso comune di WinPE Soluzione di deployment personalizzate Ambienti di recovery Supporto al boot in RAMDISK per WinPE 2.0 Aumento della velocità di download Dimensione dei blocchi TFTP modificabile Formato WIM fornisce compressione Gestione semplificata delle immagini Può funzionare anche senza Active Directory © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Windows Deployment Services 3/27/2017 2:27 AM Server PXE scalabile costruito su un’architettura unificata I plug-in rimpiazzabili consentono di aumentare le funzionalità di networking fondamentali API pubblicate Può funzionare senza Active Directory File di boot di WinPE PXE per uso con server PXE di terze parti Protocollo di comunicazione Client  Server Possibile sviluppare applicazioni personalizzate di deployment SMS & BDD usano le funzioni di estensibilità © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

Deploy di Windows Vista con SMS Microsoft Systems Management Server is an integrated management tool that provides a single interface for administering your enterprise-wide digital infrastructure. Windows Vista includes a new set of Web services for remote management that allows administrators even more flexible and granular control over enterprise desktops, servers, and software systems using SMS. SMS is also the single most powerful tool available for deploying Windows Vista in large enterprise environments. Administrators who are familiar with SMS will be aware of the suite of features in Systems Management Server that simplify the installation of software packages. Since Windows Vista images are handled by SMS just like other software packages, they can be deployed as quickly and easily as rolling out a new application update. SMS also allows administrators to catalog, sort, and modify WIM images, providing a comprehensive centralized database of deployable configurations. [BUILD1] In addition to providing a powerful database of deployment configurations, SMS allows administrators to quickly create task sequences to manage the deployment process. In this screenshot, you can see a sample task sequence for deploying Windows Vista. Each step is configurable, and additional steps can be added at any point in the sequence. Administrators can build their custom deployment task lists using the library of actions built in to SMS, or they can create their own actions. Built-in actions include saving user state, deploying an image, restoring user state, and applying software packages. Custom actions can be any command-line executable, including running VBscript. This flexibility means that SMS tasks can be quickly created to accommodate virtually any deployment scenario.

Webcast per approfondire Windows Vista Deployment: preparazione delle immagini base 300 22/09/2006 10:00-11:30 Deployment remoto con Windows Deploymeny Service 06/10/2006 Longhorn Installazione da remoto di client e server con Windows Deployment Service 29/05/2007

© 2006 Microsoft Corporation. All rights reserved © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.