Microsoft Press mcts training kit 70 - 643 applications platform configuring phần 10 pdf

Appendix 599 The specialize pass is always used in conjunction with the generalize pass and is never run as part of normal Windows Setup. When a system has been resealed using the syspresp /general- ize command, the next time the system is started, the specialize pass immediately runs. In other words, what the generalize pass takes away from the system, the specialize pass restores. Understanding the auditSystem Configuration Pass The auditSystem pass runs in the context of audit mode, and for this mode to run, the sysprep /audit command must have been run on the system. The auditSystem pass is typically used for installing additional device drivers and software updates to a reference image that contains only a minimal set of device drivers. After the auditSystem pass runs, the auditUser pass then runs on the system, and neither of these passes can run during normal Windows Setup. Understanding the auditUser Configuration Pass The auditUser pass runs immediately after the auditSystem pass on a system that has had the sysprep /audit command run on it. The auditUser pass is typically used to execute additional commands for running scripts or applications on the system. These commands can be run using either the RunSynchronous or the RunAsynchronous answer file setting. Understanding the oobeSystem Configuration Pass Finally, the oobeSystem pass configures settings that are applied during the Out Of Box Expe- rience (OOBE) portion of Windows Setup. For computers running Windows Vista, this means during the Windows Welcome phase of Setup. Configuration Passes Used During an Install from Image Deployment To conclude this section, you will learn how these various configuration passes are used dur- ing a typical install from image deployment, specifically an install from image method that uses ImageX to capture an image of a master computer and apply that image to a destination computer. Table A-3 summarizes the various steps that occur during this type of deployment and indicates which configuration passes are used during each step where appropriate. 600 Appendix Upgrading to Windows Server 2008 The objective of this section is to familiarize you with upgrading previous versions of Windows Server operating systems to Windows Server 2008. The section highlights several important things to consider before deciding upon upgrading instead of clean installs and lists prepara- tory steps to perform before starting an upgrade. The supported upgrade paths and system requirements for Windows Server 2008 are also explained. Finally, the section explains how to use various setup logs for troubleshooting purposes when a clean install or upgrade fails. Upgrading a system from Windows Server 2003 to Windows Server 2008 is a very different process from performing a clean install on a new bare-metal system that has no operating sys- tem. When you perform a clean install, you can automate the install process, using Windows AIK and other deployment technologies; alternatively, upgrades need to be manually per- formed and require careful planning. Before you upgrade your existing servers from Windows Server 2003 to Windows Server 2008, you need to ask yourself several questions: Q Are the applications currently running on the server compatible with the new version of Windows? The last thing you want to do is upgrade your servers only to discover that your third-party (or even Microsoft) applications running on them no longer work prop- erly and cannot support the operational needs of your business. To ensure that your cur- rent applications are compatible with Windows Server 2008, download the latest version of the Microsoft Application Compatibility Toolkit (ACT) from the Microsoft Table A-3 Configuration Passes During an Install from Image Deployment Using ImageX Deployment Step Configuration Passes Create a master installation, using the install from DVD method with Autounattend.xml answer file. windowsPE offlineServicing oobeSystem Use sysprep /generalize /oobe to reseal the master installation to pre- pare it for imaging. generalize Start the master computer from bootable Windows PE media and cap- ture a Windows image from the computer, using ImageX. windowsPE Start the destination computer from bootable Windows PE media and apply the previously captured master image. windowsPE Restart the destination computer from its installed image. specialize oobeSystem Appendix 601 Download Center at http://www.microsoft.com/downloads and carefully test your appli- cations for compatibility with the new platform. Q Is the hardware of your existing servers capable of running Windows Server 2008? Be sure to review the hardware requirements for Windows Server 2008 in Table A-4 later in this section and consider carefully whether it makes sense to upgrade your existing serv- ers or purchase new hardware and do clean installs instead. In addition, you need to check that Windows Server 2008 device drivers are available for any mass storage devices on your existing server systems; otherwise, you won’t be able to upgrade them. Visit the Windows Server Catalog at http://www.windowsservercatalog.com to verify that the hardware devices on your servers support the new operating system. In addition, be aware that Windows Server 2008 supports only systems that use the hardware require- ments for Windows Server 2008 ACPI, and you cannot specify a custom hardware abstraction layer (HAL) file when installing Windows Server 2008. Q Have your backed up your servers? You should back up both the configuration of your servers and any data stored on your servers before you upgrade them to the new version of Windows. You should also back up any role-specific data from your servers, for exam- ple, by backing up the DHCP database from your DHCP servers. Q Do the current server roles installed on your servers support upgrading to Windows Server 2008? Not all server roles support upgrading, and some roles might be easier to upgrade than others. Be sure to visit the Windows Server 2008 TechCenter at http:// technet.microsoft.com/en-us/windowsserver/2008/ for the latest information concerning upgrading different server roles. In addition to general upgrade considerations like the preceding ones, you need to perform some specific tasks before upgrading a Windows Server 2003 system to Windows Server 2008: Q Run diagnostics on your server’s memory and hard drives to make sure there are no problems that could corrupt the installation. Q Disable any virus protection software running on the server because such software can sometimes interfere with the installation process. Q Disconnect any UPS device connected to your server because such devices can some- times cause issues with the hardware detection process used by Windows Setup. Finally, you also need to be aware of the supported upgrade paths from earlier Windows Server operating systems to Windows Server 2008. This is discussed later, in the section titled “Supported Upgrade Paths to Windows Server 2008.” 602 Appendix Performing Side-by-Side Upgrades One way of using existing server hardware while keeping your options open in case the upgrade process goes wrong is to perform a side-by-side upgrade. In this scenario, you would install Windows Server 2008 onto a separate partition from where your Windows Server 2003 installation is located. For example, if Windows Server 2003 is installed on your C drive, you can create a second partition called D and then launch Windows Setup from within Windows Server 2003 to install Windows Server 2008 on D drive. Although this approach is really a form of clean install and not an upgrade, it enables you to reuse your existing server hardware while maintaining the ability to access your previous version of Windows in case the upgrade causes problems. In addition, you could use this approach to migrate your server settings gradually from Windows Server 2003 to Windows Server 2008 on the same system. System Requirements for Windows Server 2008 Before you upgrade an existing server system to Windows Server 2008, make sure it meets the system requirements shown in Table A-4: Table A-4 System Requirements for Windows Server 2008 Component Requirement Processor Minimum: 1 GHz (x86 processor) or 1.4 GHz (x64 processor). Recommended: 2 GHz or faster. Note: An Intel Itanium 2 processor is required for Windows Server 2008 for Ita- nium-based systems. Memory Minimum: 512 MB RAM Recommended: 2 GB RAM or greater Maximum (32-bit systems): 4 GB (Standard Edition) or 64 GB (Enterprise Edi- tion and Datacenter Edition) Maximum (64-bit systems): 32 GB (Standard Edition) or 2 TB (Enterprise Edi- tion, Datacenter Edition, and Itanium-based systems) Available Disk Space Minimum: 10 GB. Recommended: 40 GB or greater. Note: Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files. Drive DVD-ROM drive Appendix 603 Supported Upgrade Paths to Windows Server 2008 Before you consider upgrading systems from earlier Windows Server versions to Windows Server 2008, you also need to be aware of the supported upgrade paths. Table A-5 summarizes the upgrade paths that are supported. Here are some additional notes concerning the upgrade matrix for Windows Server 2008: Q You cannot upgrade from Windows 2000 Server to Windows Server 2008. Q You cannot upgrade from Windows NT 4.0 Server to Windows Server 2008. Q You cannot upgrade across architectures. For example, you cannot upgrade a 32-bit version of Windows Server 2003 to a 64-bit version of Windows Server 2008, and nei- ther can you upgrade a 64-bit version of Windows Server 2003 to a 32-bit version of Windows Server 2008. Q You cannot upgrade Windows Server 2003 Web Edition to any edition of Windows Server 2008. Display and Peripherals Super VGA (800 x 600) or higher-resolution monitor Keyboard Microsoft mouse or compatible pointing device Table A-4 System Requirements for Windows Server 2008 Component Requirement Table A-5 Supported Upgrade Paths to Windows Server 2008 If you are running . . . You can upgrade to . . . Microsoft Windows Server 2003 R2 Standard Edition Microsoft Windows Server 2003 operating systems with Service Pack 1 (SP1) Standard Edition Microsoft Windows Server 2003 operating systems with Service Pack 2 (SP2) Standard Edition Full installation of Windows Server 2008 Standard Edition Full installation of Windows Server 2008 Enterprise Edition Microsoft Windows Server 2003 R2 Enterprise Edition Microsoft Windows Server 2003 operating systems with Service Pack 1 (SP1) Enterprise Edition Microsoft Windows Server 2003 operating systems with Service Pack 2 (SP2) Enterprise Edition Full installation of Windows Server 2008 Enterprise Edition Microsoft Windows Server 2003 R2 Datacenter Edition Microsoft Windows Server 2003 with Service Pack 1 (SP1) Datacenter Edition Microsoft Windows Server 2003 with Service Pack 2 (SP2) Datacenter Edition Full installation of Windows Server 2008 Datacenter Edition 604 Appendix Q You cannot upgrade any Itanium (IA64) edition of Windows Server 2003 to any edition of Windows Server 2008. Q You cannot upgrade the RTM release of any version of Windows Server 2003 to Windows Server 2008. In other words, you must apply at least Service Pack 1 to Windows Server 2003 before you can upgrade it to Windows Server 2008. Q You cannot upgrade any edition of Windows Server 2003 to a Windows Server Core installation of Windows Server 2008. In other words, you can upgrade only to full instal- lations of Windows Server 2008—Server Core installations require a clean install. Quick Check 1. Why should you disconnect any UPS device attached to your server before upgrad- ing it? 2. How can you check whether a mass storage device supports upgrading to Windows Server 2008? Quick Check Answers 1. The UPS device can interfere with the hardware detection process used during setup. 2. Visit the Windows Server Catalog at http://www.windowsservercatalog.com to verify whether the device supports Windows Server 2008. Troubleshooting Installation Issues Whether you perform a clean install of Windows Server 2008 or upgrade from Windows Server 2003, sometimes things go wrong during a deployment. It’s important to know what troubleshooting steps you can perform when situations like this arise, and the following are some tips in this regard. Setup Log Files If an installation failed for an unknown reason, a good place to start is with reviewing the setup logs. Two log files in particular are often useful for troubleshooting installation problems: Q setupact.log This log file contains information about the setup actions that occurred during the installation process. Q setuperr.log This log file contains information about any setup errors that were gener- ated during the installation process. Appendix 605 Where these log files can be found can depend on during which phase of the setup process they were generated. Typically, this can mean that these log files are found in one of the fol- lowing directories: Q C:\$WINDOWS.~BT\Sources\Panther The setup log files are stored in this location dur- ing the windowsPE configuration pass of Windows Setup. The logs can also be found in the X:\$WINDOWS.~BT\Sources\Panther directory on the Windows PE RAM disk— that is, in memory. Q C:\Windows\Panther The online configuration phase is the first boot phase of Windows Setup and begins when the “Please wait a moment while Windows prepares to start for the first time,” message is displayed. During the online configuration phase, basic hard- ware support is installed, and if you are performing an upgrade installation, data and programs are also migrated during this phase. The setup log files are also stored in this location during the oobeSystem configuration pass. Note that in the preceding examples, C drive is either the partition on which Windows Server 2008 is being installed or the partition that contains the previous operating system being upgraded. If the system uses an Itanium (IA64) hardware architecture, the log files might also be located on another hard drive, depending on the amount of disk space available during setup. Driver Problems A common issue in failed installs is problems with device drivers. Some examples of driver- related setup problems include the following: Q Installing an unsigned device driver during setup can render an x64 installation of Windows Server 2008 unbootable. A workaround for this is to press F8 during the boot process and select Disable Driver Signature Enforcement from the Advanced Boot Options menu, but the best solution is to obtain a digitally signed version of the driver causing the issue. Q If setup cannot detect a removable boot device during an upgrade installation, setup might fail with a blue screen after the first restart. If you need to load a device driver for a boot device during setup, store the driver on removable media such as a floppy disk, USB flash device, CD media, or DVD media. The driver should be located either in the root directory of the media or in one of the following subfolders: T \Sources for x86-based systems T \AMD64 for x64-based systems T \IA64 for Itanium-based systems 606 Appendix Installing Server Core A new feature of Windows Server 2008 is the Windows Server Core installation option, which enables you to install a stripped-down version of Windows Server 2008 that, compared to the full installation option, has fewer hardware requirements, is more secure, and is easier to main- tain. IT administrators will welcome Server Core as a new platform for running critical net- work services such as DHCP and DNS. Although the tools for deploying Server Core are the same as those for deploying the full ver- sion of Windows Server 2008, there are some differences in how these tools are used, espe- cially for automating post-installation tasks such as performing the initial configuration of the server and adding server roles and features. Understanding Windows Server Core With previous versions of Windows server operating systems such as Windows Server 2003, installing the operating system also installed binaries for features that were often not required in many networking environments. For example, a server that isn’t being used as an applica- tion server doesn’t really need the .NET Framework and CLR installed on it. Similarly, a head- less server that is managed remotely doesn’t really need the Windows Explorer desktop shell or various GUI-dependent elements such as Themes or the Search window. In fact, the prob- lem with installing the binaries for such features is that they can increase the maintenance requirements for the server. For example, if the .NET Framework is installed on your server, any software updates released by Microsoft for this feature must be applied to your server— even if you are not actually using this feature. Otherwise, you risk leaving your server unpro- tected if you fail to apply patches to unused features like this. Another reason installing unneeded features on a server is a bad idea is because each feature has its own resource needs in terms of memory, processor, and disk requirements. Because of these issues, Microsoft has created two separate installation options for Windows Server 2008: full and Server Core. The full installation option installs the binaries for all fea- tures onto your system. By contrast, the new Server Core option installs only a subset of these binaries that are required to support a limited set of server roles, role services, and features. By providing only a minimal environment for running a limited set of server roles and features, the new Server Core installation option can help reduce both the hardware and maintenance needs for your server. Specifically, the Server Core installation option provides the following benefits: Q Greater stability and performance Server Core supports running only a limited number of server roles, which means fewer services running on your server. Having fewer ser- vices means more stability and better performance. Appendix 607 Q Smaller attack surface Because fewer network services are running on a computer run- ning Server Core, the attack surface of the computer is smaller as well. By eliminating bina- ries for unneeded services from your system and reducing the number of running services required, Server Core can be a more secure platform than the full installation option. Q Less maintenance required If a role or feature is not available on Server Core, the bina- ries for that role or feature are not even present on the system. Therefore, when a soft- ware update is released for a role or feature not present, you don’t even need to apply it to your system. In fact, Microsoft estimates that Server Core needs only about 40 percent of the software updates that earlier versions of Windows Server required. Q Smaller disk requirements Because many binaries included in the full installation option are not needed in Server Core, the Server Core option has much smaller disk requirements than the full installation option (about 1.5GB compared to approximately 5.9GB for a full installation). In addition, Server Core can also run more efficiently than the full option on systems having a limited amount of RAM. Availability and System Requirements for Server Core Server Core is available as an installation option for both the 32-bit and 64-bit versions of these Windows Server 2008 SKUs: Q Windows Server 2008 Standard Edition Q Windows Server 2008 Enterprise Edition Q Windows Server 2008 Datacenter Edition Table A-6 shows the minimum and recommended system requirements for installing the Server Core option of Windows Server 2008. Table A-6 Minimum and Recommended System Requirements for Server Core Component Requirement Processor Minimum: 1GHz. Recommended: 2GHz. Optimal: 3GHz or faster. Note that an Intel Itanium 2 processor is required for Windows Server 2008 for Itanium-based systems. Memory Minimum: 512MB RAM Recommended: 1GB RAM Optimal: 1GB RAM (Server Core installation) or more Maximum (32-bit systems): 4GB (Standard) or 64GB (Enterprise Edition and Datacenter Edition) Maximum (64-bit systems): 32GB (Standard Edition) or 2TB (Enterprise Edition, Datacenter Edition, and Itanium-based systems) 608 Appendix What’s in Server Core Server Core is intended mainly for dedicated servers running one or more critical server roles. For example, you might use Server Core for a dedicated DHCP server, DNS server, domain controller, and so on. Because the goal behind the design of Server Core is to keep its require- ments and attack surface at a minimum, only a subset of the server roles available on the full installation of Windows Server 2008 are available in Server Core. Specifically, the following server roles are the only roles available for a Server Core installation: Q Active Directory Domain Services (AD DS) Q Active Directory Lightweight Directory Services (AD LDS) Q DHCP Server Q DNS Server Q File Services Q Print Services Q Web Server (IIS) Q Hyper-V Another role that can be installed on Server Core is Streaming Media Services. This role is not available in Windows Server 2008, however, but is instead available as an out-of-band (OOB) download that can be accessed from a link in Microsoft Knowledge Base article 934518 (http://support.microsoft.com/kb/934518). Note that the mere fact of a server role being available for installation on Server Core does not mean that all role services associated with that role can be installed. For instance, although Hard Disk Minimum: 8GB. Recommended: 10GB (Server Core installation). Optimal: 40GB (Server Core installation) or more. Note that computers with more than 16GB of RAM will require more disk space for paging, hibernation, and dump files. In addition, although Server Core has an initial disk requirement of about 1.5GB, a partition of at least 10GB is recom- mended to accommodate updates, hotfixes, temporary files, and other future changes. Drive DVD-ROM drive Display Super VGA (800 × 600) or higher-resolution monitor Other Keyboard and Microsoft mouse or compatible pointing device Table A-6 Minimum and Recommended System Requirements for Server Core Component Requirement [...]... Id="NET-Framework" Id="WSRM" Id="Wireless-Networking" Id="Backup" Id="WINS-Server" Id="Remote-Assistance" Id="Simple-TCPIP" Id="Telnet-Client" Id="Telnet-Server" Id="Subsystem-UNIX-Apps" Id="RPC-over-HTTP-Proxy" Id="SMTP-Server" Id="LPR-Port-Monitor" Id="Storage-Mgr-SANs" Id="BITS" Id="MSMQ"/> Id="MSMQ-Services"/> Id="MSMQ-DCOM"/> Id="WPAS" Id="Windows-Internal-DB" Id="BitLocker" Id="Multipath-IO" Id="ISNS"... file setting: Microsoft- Windows-Shell-Setup\UserAccounts\AdministratorPassword Similarly, the time zone can be specified during installation by configuring the Microsoft- Windows-Shell-Setup setting in your answer file (See Figure A-15.) Figure A-15 Specifying the time zone in your answer file If you want to enable Remote Desktop on your server during installation, you can do this by configuring the... conjunction with your Autounattend.xml or Unattend.xml answer file The key to doing this is to add the Microsoft- Windows-Shell-Setup\FirstLogonCommands component to the oobeSystem configuration pass section of your answer file (See Figure A-18.) 632 Appendix Figure A-18 Configuring the Microsoft- Windows-Shell-Setup\FirstLogonCommands section of the oobeSystem pass for an answer file The FirstLogonCommands... do this by configuring the following answer file setting: Microsoft- Windows-TerminalServices-LocalSessionManager To do this, add this setting to the offlineServicing pass section of your answer file and then use Windows SIM to configure the fDenyTSConnections setting so it has the Boolean value of False (See Figure A-16.) 622 Appendix Figure A-16 Enabling Remote Desktop using an answer file Once Remote... Figure A-19 shows three commands being executed synchronously (one after the other) during the oobeSystem pass of setup, with the second command installing the DHCP Server role using its default settings Figure A-19 Running multiple commands during the oobeSystem configuration pass of setup Note that in addition to using FirstLogonCommands as described, you must also use the Microsoft- Windows-Shell-Setup\Autologon... statement bears some further investigation, namely, that Server Core in general is not intended as a platform for running network applications For instance, not only can you not install the Terminal Services role on Server Core, you also can’t install applications such as the 2007 Microsoft Office System or Microsoft Visual Studio on Server Core The reason an application such as Office or Visual Studio... Id="Storage-Mgr-SANs" Id="BITS" Id="MSMQ"/> Id="MSMQ-Services"/> Id="MSMQ-DCOM"/> Id="WPAS" Id="Windows-Internal-DB" Id="BitLocker" Id="Multipath-IO" Id="ISNS" Id="Removable-Storage" Id="TFTP-Client" Id="SNMP-Service" Id="Internet-Print-Client" Id="PNRP" Id="CMAK" 631 InstallAllSubFeatures="true"/> InstallAllSubFeatures="true"/> InstallAllSubFeatures="true"/> InstallAllSubFeatures="true"/> InstallAllSubFeatures="true"/>... by -remove Removes the role, role service, or feature specified by -query [] The parameter specifies the role or feature you want to install or remove by using ServerManagerCmd.exe For example, the parameter for the DHCP Server role is simply DHCP whereas the parameter for the Active Directory Domain Services (AD DS) role is ADDS-Domain-Controller... such applications are supported in Server Core Table A-7 summarizes these available tools along with a brief explanation of why they are included In addition, note that some of the functionality in these tools doesn’t work For example, if you select Help from the menu in Notepad, no Help file opens because the Help engine for running chm files is not present in Server Core  610 Appendix Table A-7 TGUI... to installing and configuring roles, role services, and features on your server Many of these tasks can be automated, and the objective of this section is to familiarize you with the various ways you can perform post-installation tasks during Windows Server 2008 deployments The methods covered here include configuring servers manually, using both GUI tools and the command line, and configuring them . that your third-party (or even Microsoft) applications running on them no longer work prop- erly and cannot support the operational needs of your business. To ensure that your cur- rent applications. cannot upgrade a 32-bit version of Windows Server 2003 to a 64-bit version of Windows Server 2008, and nei- ther can you upgrade a 64-bit version of Windows Server 2003 to a 32-bit version of Windows. Appendix Performing Side-by-Side Upgrades One way of using existing server hardware while keeping your options open in case the upgrade process goes wrong is to perform a side-by-side upgrade. In this