Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống
1
/ 50 trang
THÔNG TIN TÀI LIỆU
Thông tin cơ bản
Định dạng
Số trang
50
Dung lượng
0,99 MB
Nội dung
Additional Resources CHAPTER 11
353
an Activation Call Center. Customers in the United States can call 888-352-7140. International
customers should contact their local Support Center. For the telephone numbers of Activation
Call Centers worldwide, go to http://go.microsoft.com/fwlink/?LinkId=107418. When calling a
Support Center, customers must have the Volume License agreement.
Volume Licensing customers can log on to the VLSC Web page at any time to view their
KMS key information. The VLSC Web site also contains information on how to request and use
MAKs. For more information about MAK and KMS keys, including information about increas-
ing the number of allowed activations, go to the Existing Customers page at
http://go.microsoft.com/fwlink/?LinkId=74008.
Summary
Volume Activation helps IT professionals automate and manage the product activation process
on computers running Windows7 editions that are licensed under a Volume Licensing pro-
gram or other programs that provide Volume License editions of Windows. Two options are
available for Volume Activation: KMS and MAK. KMS activation provides a solution that is easy
to deploy and manage, requiring little interaction. Environments that don’t meet the minimum
requirements for KMS can use MAK activation to activate systems with the Microsoft-hosted
activation service.
Additional Resources
These resources contain additional information and tools related to this chapter.
Related Information
n
Genuine Microsoft Software at http://go.microsoft.com/fwlink/?LinkId=151993.
n
Genuine Microsoft Software validation page at http://go.microsoft.com/fwlink/?LinkId=64187.
n
“Key Management Service 1.1 (x64) for Windows Server 2003 SP1 and Later” at
http://go.microsoft.com/fwlink/?LinkId=83041.
n
“Microsoft Activation Centers Worldwide Telephone Numbers” at http://go.microsoft.com
/fwlink/?LinkId=107418.
n
Microsoft Volume Licensing at http://go.microsoft.com/fwlink/?LinkId=73076.
n
Microsoft Volume Licensing Service Center at http://go.microsoft.com/fwlink/?LinkId=107544.
n
“Product Activation and Key Information” at http://go.microsoft.com/fwlink/?LinkId=74008.
n
“System Center Pack Catalog” at http://go.microsoft.com/fwlink/?LinkID=110332.
n
“Volume Activation 2.0 Technical Guidance” at http://go.microsoft.com/fwlink/?LinkID=75674.
n
Volume Activation Deployment Guide at http://go.microsoft.com/fwlink/?LinkId=150083.
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
CHAPTER 11 Using Volume Activation
354
n
Volume Activation on TechNet at http://technet.microsoft.com/en-us/windows
/dd197314.aspx.
n
Volume Activation Operations Guide at http://go.microsoft.com/fwlink/?LinkId=150084.
n
Volume Activation Planning Guide at http://go.microsoft.com/fwlink/?LinkID=149823.
n
Volume Activation Technical Reference Guide at http://go.microsoft.com/fwlink/?LinkId=152550.
n
“Windows Vista Privacy Notice Highlights” at http://go.microsoft.com/fwlink/?LinkID=52526.
n
“Windows Automated Installation Kit (Windows AIK) for Windows7 RC” at
http://go.microsoft.com/fwlink/?LinkId=136976.
On the Companion Media
n
Volume Activation Planning Guide
n
Volume Activation Deployment Guide
n
Volume Activation Operations Guide
n
Volume Activation Technical Reference Guide
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
355
CHAPTER 12
Deploying with Microsoft
Deployment Toolkit
n
Introducing MDT 2010 355
n
Using LTI with MDT 2010 357
n
Customizing MDT 2010 367
n
Summary 378
n
Additional Resources 378
T
he Windows7 operating system and the Windows Automated Installation Kit
(Windows AIK) include the low-level tools necessary to deploy the operating system.
However, they don’t provide a framework for managing and automating high-volume
Windows 7 deployments or business logic for managing complex projects. Microsoft
Deployment Toolkit 2010 (MDT 2010) provides this framework and business logic,
making it Microsoft’s primary tool for deploying Windows 7.
This chapter describes how to use MDT 2010 to deploy Windows7. It assumes that
you’ve already created a deployment share in a lab and populated it with applications,
device drivers, and packages. It also assumes that you’ve already designed and built cus-
tom Windows7 disk images, as described in Chapter 6, “Developing Disk Images.” This
chapter helps you configure and customize MDT 2010 for Lite Touch Installation (LTI). For
more information about Zero Touch Installation (ZTI) by using MDT 2010 with Microsoft
System Center Configuration Manager 2007, see the MDT 2010 documentation.
Introducing MDT 2010
The following sections introduce key concepts for using MDT 2010 to deploy Windows7.
Specifically, the section titled “Deployment Scenarios” describes the scenarios that MDT
2010 supports. For LTI, MDT 2010 relies entirely on MDT 2010, the Windows AIK, and
potentially Windows Deployment Services.
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
CHAPTER 12 Deploying with Microsoft Deployment Toolkit
356
Deployment Scenarios
The following list describes the scenarios supported by MDT 2010:
n
New Computer A new installation of Windows is deployed to a new computer. This
scenario assumes that there is no user data or profile to preserve.
n
Upgrade Computer The current Windows operating system on the target computer
is upgraded to the target operating system. The existing user state data and applications
are retained (as supported by the target operating system).
n
Refresh Computer A computer currently running a supported Windows operating
system is refreshed. This scenario includes computers that must be reimaged for image
standardization or to address a problem. This scenario assumes that you’re preserving
the existing user state data on the computer. Applications are not preserved in this
scenario.
n
Replace Computer A computer currently running a supported Windows operating
system is replaced with another computer. The existing user state migration data is
saved from the original computer. Then, a new installation of Windows is deployed to a
new computer. Finally, the user state data is restored to the new computer.
Based on your existing environment, you can select any combination of these scenarios in
the deployment. For example, if you are upgrading only existing computers, only the Refresh
Computer scenario or the Upgrade Computer scenario is necessary. If you’re deploying new
computers for some users and upgrading the remaining computers, use the Upgrade Com-
puter, Replace Computer, and Refresh Computer scenarios as appropriate.
Resource Access
Before starting the deployment, create additional shared folders in which to store the user
state migration data and the deployment logs. You can create these shared folders on any
server that is accessible to destination computers. Refer to your deployment plan to guide
you on server placement. The following list describes the shared folders you should create:
n
MigData Stores the user state migration data during the deployment process
n
Logs Stores the deployment logs during the deployment process
note MigData and Logs are recommended shared folder names. You can use any name
for these shared folders; however, the remainder of this chapter refers to these shared
folders by these names.
During deployment to destination computers, the MDT 2010 deployment scripts connect
to the deployment shares and shared folders. Create accounts for use by these scripts when
accessing these resources.
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Using LTI with MDT 2010 CHAPTER 12
357
After creating the additional shared folders, configure the appropriate shared folder
permissions. Ensure that unauthorized users are unable to access user state migration
information and the deployment logs. Only the destination computer creating the user
state migration information and the deployment logs should have access to these folders.
For each shared folder, disable inheritance and remove existing permissions. Then give
the domain Computers group the Create Folder/Append Data permission for each folder
only, and do the same for the domain Users group. Also, add the Creator Owner group to
each shared folder, giving it the Full Control permission for subfolders and files only. Also,
give each group that will have administrator access to migration data and log files the same
permissions.
The permissions that you set in these steps allow a target computer to connect to the ap-
propriate share and create a new folder in which to store user state information or logs. The
folder permissions prevent other users or computers from accessing the data stored in the
folder.
Using LTI with MDT 2010
Prior to deploying Windows7 by using LTI with MDT 2010, be sure to perform the following
steps, as described in Chapter 6:
n
Create a deployment share, possibly in a lab environment, and add the appropriate
resources to it. To add applications to the deployment share, see Chapter 8, “Deploying
Applications.”
n
In the deployment share, create and customize task sequences that install Windows7
as required.
n
Build any custom Windows7 images required for deployment.
n
Test your deployment share and custom disk images in the lab.
Chapter 6 describes how to fully stock the deployment share with applications, device
drivers, packages, and operating system source files. It also describes how to create task se-
quences and build custom Windows7 disk images. In this chapter, you learn how to replicate
your deployment share onto the production network and how to perform an LTI deployment
by using it.
Replicating a Deployment Share
For LTI, you need to replicate the deployment share in the production environment or copy
it to removable media. This process enables you to develop in a controlled environment and
then easily move the deployment share into the production environment when you’re ready
to deploy Windows7. MDT 2010 provides both capabilities.
When you replicate a deployment share, you can replicate everything or you can choose
which folders in the deployment share to replicate. You choose folders to replicate by creat-
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
CHAPTER 12 Deploying with Microsoft Deployment Toolkit
358
ing selection profiles. A selection profile simply selects folders across applications, operating
systems, out-of-box drivers, packages, and task sequences. You create a selection profile in
advance, and then you choose that selection profile when you set up replication.
During replication, Deployment Workbench updates the boot media. The updated boot
media contains an updated Bootstrap.ini file that is configured to connect to the replicated
deployment share. In other words, each deployment share has its own boot media associated
with it, and that boot media is configured to connect a specific share.
To create a selection profile, perform the following steps:
1. In the Deployment Workbench console tree under the Advanced Configuration folder
of your deployment share, right-click Selection Profiles and click New Selection Profile.
2. In the Selection Profile Name box, type a descriptive name for the selection profile and
then click Next. For example, a selection profile that selects files for deployment in a
particular department might use the department name for its title.
3. On the Folder page, select the folders that you want to include in the selection profile
and then click Next.
4. On the Summary page, review the details and click Next.
5. Click Finish to close the New Selection Profile Wizard.
To link deployment shares for replication, perform the following steps:
1. In the production environment, create a share in which to replicate the deployment
share. Make sure that your account has full control of the product sharing.
2. In the Deployment Workbench console tree under the Advanced Configuration folder
of your deployment share, right-click Linked Deployment Shares and then click New
Linked Deployment Share.
3. On the General Settings page, shown on the following page, do the following and then
click Next:
a. In the Linked Deployment Share UNC Path box, type the Universal Naming Con-
vention (UNC) path of the deployment share in the production environment.
b. From the Selection Profile list, click the profile that contains the folders that you
want to replicate to the production environment.
c. Click the Merge The Selected Contents Into The Target Deployment Share option
to merge this deployment share with the production share; alternatively, click the
Replace The Contents Of The Target Deployment Share Folder With Those Selected
option to replace the contents of the production share with this share.
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Using LTI with MDT 2010 CHAPTER 12
359
4. On the Summary page, review the details and then click Next.
5. On the Confirmation page, click Finish to close the New Linked Deployment Share
Wizard.
To replicate the lab deployment share to production, perform the following steps:
1. In the Deployment Workbench console tree under the Advanced Configuration folder
of your deployment share, click Linked Deployment Shares.
2. In the Details pane, right-click the replication partnership you created previously and
then click Replicate Content.
3. On the Confirmation page, click Finish to close the Replicate To Linked Deployment
Share dialog box.
To link removable media to the deployment share, perform the following steps:
1. In the Deployment Workbench console tree under the Advanced Configuration folder
of your deployment share, right-click Media and click New Media.
2. On the General Settings page, do the following and then click Next:
a. In the Media Path box, type the path of the removable media to which you want to
copy the deployment share.
b. From the Selection Profile list, click the profile that contains the folders you want to
replicate to the production environment.
3. On the Summary page, review the details and click Next.
4. On the Confirmation page, click Finish to close the New Media Wizard.
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
CHAPTER 12 Deploying with Microsoft Deployment Toolkit
360
To replicate the lab deployment share to removable media, perform the following steps:
1. In the Deployment Workbench console tree under the Advanced Configuration folder
of your deployment share, click Media.
2. In the details pane, right-click the media link you created previously and then click
Update Media Content.
3. On the Confirmation page, click Finish to close the Updated Media Content dialog box.
Preparing Windows Deployment Services
In the deployment process, Windows Deployment Services servers are responsible for
starting Windows Preinstallation Environment (Windows PE) on destination computers to
prepare the computers for image installation. After you install and initially configure Windows
Deployment Services, ensure that Windows PE images created by updating deployment
shares in Deployment Workbench have the appropriate flat-file image structures and add
them to the Windows Deployment Services server.
Windows Deployment Services is responsible for initiating the deployment process for
Pre-Boot Execution Environment (PXE) boot-enabled destination computers. For more
information about setting up and configuring the Windows Deployment Services server, see
Chapter 10, “Configuring Windows Deployment Services.”
Configuring Resources
In addition to the shared folders described in the section titled “Resource Access” earlier
in this chapter, the MDT 2010 scripts may require access to other resources, including
application or database servers, such as Microsoft SQL Server 2008. The resources that the
installation requires access to depend on the applications you’ve added to the distribution
and the customizations you’ve made to MDT 2010 and the task sequence.
For LTI, you need to grant access to the deployment share to the credentials specified in
one the following ways:
n
UserID, UserPassword, and UserDomain properties in the CustomSettings.ini file. MDT
2010 uses these credentials to connect to the deployment share and other network
resources. Make sure the credentials used in these properties have Read and
Execute permissions on the deployment share. By providing these credentials in
CustomSettings.ini, you can fully automate the LTI installation process.
n
If you don’t provide the credentials in CustomSettings.ini, you provide the credentials
necessary to connect to the deployment share when you start the Windows Deploy-
ment Wizard on the destination computer. Make sure that the credentials used to start
the Windows Deployment Wizard have at least Read and Execute permissions on the
deployment share.
Make sure that the credentials used for LTI (defined in CustomSettings.ini or used to start
the Windows Deployment Wizard) have Read and Execute permissions to access the following
resources:
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Using LTI with MDT 2010 CHAPTER 12
361
n
Deployment share Configure access to the deployment share created in Deployment
Workbench.
n
Any resources on application or database servers Configure access to applica-
tions or databases that are accessed through the SQLServer, SQLShare, and Database
properties.
note Other connections to the same servers, such as Named Pipes and Remote Procedure
Call (RPC), use the same credentials listed here. Use the ZTIConnect.wsf script to establish
these connections. For more information about the ZTIConnect.wsf script, see the MDT
2010 documentation.
Configuring CustomSettings.ini
CustomSettings.ini is the primary customization file for MDT 2010. The customizations you
perform are specific to your organization. The names of the servers, default gateways for
each subnet, media access control (MAC) addresses, and other details are unique to your
organization, of course. The customization that you perform configures the deployment
processes to run properly in your network environment. The examples in this section are
provided as guides to help you in your customization. For more information on other
configuration scenarios, see the MDT 2010 documentation.
The following listing shows a customized version of the CustomSettings.ini file after com-
pleting the New Deployment Share Wizard in Deployment Workbench. The initial contents
of CustomSettings.ini depend on the answers given to the New Deployment Share Wizard, of
course. The section titled “Customizing CustomSettings.ini” later in this chapter describes in
more detail how to customize these settings for different computers.
CustomSettings.ini Modified by Deployment Workbench
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
The CustomSettings.ini file in the listing contains the property values for all the target
computers to be deployed using this version of the file. This version of the file contains no
values that are unique to a specific target computer, because all of the settings are defined
in the [Default] section. In this case, the target computer–specific configuration values are
provided manually during the installation process by using the Windows Deployment Wizard.
Table 12-1 explains the properties and corresponding values used in the listing.
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
CHAPTER 12 Deploying with Microsoft Deployment Toolkit
362
note In MDT 2010, the document Microsoft Deployment Toolkit Reference defines these
and dozens of other settings that you can define in CustomSettings.ini. Of all the guides in
MDT 2010, the Microsoft Deployment Toolkit Reference is the most useful, particularly for IT
professionals already familiar with the MDT 2010 basic concepts.
TABLE 12-1 Explanation of CustomSettings.ini Properties for LTI
LINE IN CUSTOMSETTINGS.INI PURPOSE
[Settings] Indicates the start of the [Settings] section.
Priority=Default Establishes the sequence in which the process parses sub-
sections to locate values for the variables. In this example,
the [Default] section is the only subsection that is parsed
for variables.
Properties=MyCustomProperty Indicates any additional properties to locate. The proper-
ties listed here are in addition to the properties listed in
ZTIGather.xml. ZTIGather.wsf parses ZTIGather.xml to ob-
tain a list of the properties. The property names defined
here are added to them.
[Default] Indicates the start of the [Default] section. The settings
defined in this section apply to all computers.
OSInstall=Y Indicates that the computer is supposed to perform an
operating system deployment.
SkipAppsOnUpgrade=YES Indicates whether the Windows Deployment Wizard
prompts the user to install applications during an
upgrade. If the property is set to YES, the wizard page
is not displayed.
SkipCapture=NO Indicates whether the Windows Deployment Wizard
prompts to capture an image. If the property is set to YES,
the wizard page is not displayed.
SkipAdminPassword=YES Indicates whether the Windows Deployment Wizard
prompts to set the local Administrator password. If the
property is set to YES, the wizard page is skipped and not
displayed.
SkipProductKey=YES Indicates whether the Windows Deployment Wizard
prompts for a product key. If the property is set to YES,
the wizard page is skipped and not displayed.
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
[...]... substitutes the value for Make that it determines through a Windows Management Instrumentation (WMI) call and looks for the corresponding section, such as [Dell Computer Corporation] Grouping with [DefaultGateway] [DefaultGateway] 172 .16.0.3=NYC 172 .16.1.3=NYC 172 .16.2.3=NYC 172 .16.111.3=DALLAS 172 .16.112.3=DALLAS 172 .16.116.3=WASHINGTON 172 .16.1 17. 3=WASHINGTON [NYC] UDShare=\\NYC-AM-FIL-01\MigData SLShare=\\NYC-AM-FIL-01\Logs... configuring MDT 2010 to deploy Windows 7 using LTI LTI is a simple way to deploy Windows7 in small and medium-sized businesses It requires no infrastructure and is very easy to set up and customize Additional Resources These resources contain additional information and tools related to this chapter n 378 Chapter 3, “Deployment Platform,” includes information about the Windows7 installation architecture... Included Tools 384 n Downloadable Tools 388 n Windows Sysinternals Suite 389 n Windows7 Enterprise and the Microsoft Desktop Optimization Pack 390 n Microsoft System Center 393 n Introduction to Windows PowerShell Scripting 396 n Summary 475 n Additional Resources 476 A s an administrator, you will need tools for managing computers running the Windows7 operating system The tools you will use,... Windows Firewall on Windows7 computers More Info For a list of available commands and their detailed syntax, see the “Com- mand Reference” section of “Commands, References, and Tools for Windows Server 2008 R2,” which can be found in the Windows Server TechCenter on Microsoft TechNet at http://technet.microsoft.com/en-us/library/dd69 574 7.aspx Remote Desktop The Remote Desktop feature of Windows7. .. Administration Tools, Feature Administration Tools, Turn Windows Features On Or Off New in Windows7 and Windows Server 2008 R2 is the ability to use Windows PowerShell to automate common Group Policy tasks such as creating, configuring, linking, backing up Group Policy objects (GPOs), and direct editing of registry-based policy settings Windows7 and Windows Server 2008 R2 also include other enhancements... tools available for managing Windows7 computers and points you to where you can learn more about these tools, either within this book or elsewhere online The chapter also provides you with a comprehensive introduction on how to use Windows PowerShell 2.0, which is included in Windows7 and provides a powerful language for scripting the remote administration of Windows7 clients Please purchase PDF... WMI can be used to manage Windows 7 computers in several ways: n Interactively, by using the Windows Management Instrumentation Command-line (WMIC) n In batch mode, by using WMI scripts written in Microsoft VBScript n Either interactively or in batch mode by using Windows PowerShell More Info For information on how to use WMI to manage Windows 7 computers, see the various resources available on the... http://www.microsoft.com/technet/scriptcenter/scripts/default.mspx?mfr=true Windows PowerShell Windows PowerShell is a command-line shell and scripting language designed for system administration of Windows- based computers Windows PowerShell helps administrators control and automate the administration of Windows operating systems and applications Windows PowerShell is built on the Microsoft NET Framework and uses standardized command-line tools called cmdlets to manage Windows- based... Policy The GPMC is available as a feature you can install on Windows Server 2008 R2 The GPMC can also be used on administrative workstations running the Windows 7 Professional, Enterprise, or Ultimate Edition operating systems To use the GPMC on a computer running Windows 7, first install the Remote Server Administration Tools (RSAT) for Windows7 on the computer and then enable the Group Policy Management... administrators to connect to and remotely manage a Windows7 computer on their network when the need arises For more information about Remote Desktop in Windows 7, see Chapter 27, “Connecting Remote Users and Networks.” By using Remote Desktop Connection (Mstsc.exe) on an administrative workstation, an administrator can connect remotely to any Windows7 computer on the network that has Remote Desktop . 3 57
n
Customizing MDT 2010 3 67
n
Summary 378
n
Additional Resources 378
T
he Windows 7 operating system and the Windows Automated Installation Kit
(Windows. [DefaultGateway]
[DefaultGateway]
172 .16.0.3=NYC
172 .16.1.3=NYC
172 .16.2.3=NYC
172 .16.111.3=DALLAS
172 .16.112.3=DALLAS
172 .16.116.3=WASHINGTON
172 .16.1 17. 3=WASHINGTON