KMS Configuration. KMS configuration using Provisioning Services. Page 1

Transcription

1 KMS Configuration KMS configuration using Provisioning Services Page 1

2 Table of Contents I. INTRODUCTION... 3 II. KMS CONFIGURATION SCENARIOS:... 3 SCENARIO 1: CONFIGURE KMS BY BUILDING VDISK USING IMAGING WIZARD... 4 SCENARIO 2: CONFIGURE KMS FOR THE FIRST TIME TO A PRE-EXISTING VDISK... 5 SCENARIO 3: MAINTAINING OR UPGRADING A VDISK IMAGE THAT IS CURRENTLY USING KMS... 6 SCENARIO 4: INSTALLING MICROSOFT OFFICE 2010 TO AN EXISTING KMS CONFIGURED (FOR WINDOWS) VDISK DURING MAINTENANCE... 6 III. IMPORTANT INFORMATION ON REARM:... 7 Page 2

3 I. Introduction The purpose of this document is to help an Administrator configure Provisioning Services 5.6 SP1 (PVS) Target Devices that are using Microsoft Key Management Server (KMS) in the best way to fit their environment. KMS can be configured on a vdisk Image with the help of PVS to apply volume licenses for Microsoft Server 2008, Microsoft Server 2008R2, Windows 7 and Windows Vista, as well as Office In PVS the option for KMS can be easily configured while building vdisk s with the Imaging Wizard; alternatively it can be configured at any time using the Console or MCLI/Powershell command-line interfaces The Product Administrator s Guide, Section Managing Microsoft KMS Volume Licensing provides further details on KMS configuration for a PVS vdisk. II. KMS Configuration Scenarios: The following section outlines the steps to configure KMS in various scenarios to accommodate specific deployment environment. Please make sure to read all the scenarios to verify which one best fits ones deployment and follow the steps accordingly. It is recommended that the admin completes all steps in the right order for a successful configuration. KMS configuration can be done in the following ways in accordance with various environment: Customers can configure KMS for both Windows & Office Customers can configure KMS for Only Windows Customers can configure KMS for Only Office The Scenario s below will help the admin to configure KMS accordingly. Page 3

4 SCENARIO 1: Configure KMS by building vdisk using Imaging Wizard For both Windows & Office 2010: The Physical or Virtual Machine with the OS and Office 2010 installed on it. For Only Windows or Only Office 2010: The Physical or Virtual Machine with the OS installed on it. (Optional: Office 2010 is included in the image) 1. Install PVS Client software (PVS5.6.1) 2. Run Imaging wizard to build vdisk 3. On the page of Microsoft Volume Licensing select "KMS" 4. Build the vdisk 5. Shutdown the target device 6. Boot the device off vdisk in Private Image mode 7. Rearm the system for both Windows & Office, one after the other. If KMS is configured for Only one of them, then rearm one of them accordingly. For Windows Vista, 7, 2008, & 2008R2: Run cscript.exe slmgr.vbs -rearm For Office 2010: Program Files(x86)\Common Files\microsoft shared\officesoftwareprotectionplatform\ospprearm.exe Note: It is important to perform this operation on a system booted from the vdisk in Private Image mode so that the master target device hard disk's rearm count is not reduced. Also if the system is rearmed once, an admin will never have to rearm it again. 8. Shutdown the target device 9. Set the vdisk mode to Standard Image mode 10. Stream the vdisk to one or more target devices Note: Admin s can validate the KMS configuration was successful by verifying that the CMID for each device is unique. For Windows Vista, 7, 2008, and 2008R2: Run cscript.exe slmgr.vbs dlv For Office 2010: Run C:\Program Files\Microsoft Office\Office14\cscript ospp.vbs /dcmid Page 4

5 SCENARIO 2: Configure KMS for the first time to a pre-existing vdisk Vdisk was pre-build using a tool like XenConvert or the Imaging wizard (with Microsoft Licensing Option set to None ) For both Windows & Office 2010: VDisk that has OS and Office 2010 installed on it; is pre-build using XenConvert/Imaging Wizard but KMS has never been configured. For Only Windows or Only Office 2010: VDisk that has the OS installed on it (Optional: Office 2010 is included in the image); that was pre-built using XenConvert/Imaging wizard but KMS has never been configured. 1. Goto PVS Server: In the Console, right-click on the vdisk, then select the File Properties menu option. The vdisk File Properties dialog appears 2. Click on the Microsoft Volume Licensing tab, then set the licensing option to None 3. Boot up the device off vdisk in Private Image mode 4. Rearm the system for both Windows & Office2010, one after the other. If KMS is configured for Only one of them, then pick your option to rearm one of them accordingly. For Windows Vista, 7, 2008, & 2008R2: Run cscript.exe slmgr.vbs -rearm For Office 2010: Program Files(x86)\Common Files\microsoft shared\officesoftwareprotectionplatform\ospprearm.exe Note: It is important to perform this operation on a system booted from the vdisk in Private Image mode so that the master target device hard disk's rearm count is not reduced. Also once the system is rearmed once, you will never have to rearm it again. 5. Shutdown the target device 6. Goto PVS Server: In the Console, right-click on the vdisk, then select the File Properties menu option. The vdisk File Properties dialog appears 7. Click on the Microsoft Volume Licensing tab, then set the licensing option to KMS 8. On the Mode tab, set the vdisk access mode to Standard Image mode 9. Stream the vdisk to one or more target devices Note: Admin s can validate the KMS configuration was successful by verifying that the CMID for each device is unique. Page 5

6 For Windows Vista, 7, 2008, and 2008R2: Run cscript.exe slmgr.vbs dlv For Office 2010: Run C:\Program Files\Microsoft Office\Office14\cscript ospp.vbs /dcmid SCENARIO 3: Maintaining or Upgrading a vdisk Image that is currently using KMS VDisk is already configured for KMS and is deployed successfully. For both Windows & Office 2010: VDisk is already configured for KMS for both Windows & Office2010 and is deployed successfully. For Only Windows or Only Office 2010: VDisk is already configured for KMS for Only Windows or Only Office2010 and is deployed successfully. 1. From the PVS Console: Set the vdisk mode to Private Image mode 2. Boot up a target device 3. Apply the required OS Application/Service Pack/Update 4. Shutdown the target device 5. Set the vdisk mode back to Standard Image mode 6. Stream the vdisk to one or more target devices SCENARIO 4: Installing Microsoft Office 2010 to an existing KMS configured (for Windows) vdisk during Maintenance VDisk is already KMS configured for Windows and is deployed successfully. 1. In the Console, right-click on the vdisk, then select the File Properties menu option 2. Click on the Microsoft Volume Licensing tab, then change the licensing option from KMS to None 3. On the Mode tab, set the vdisk access mode to Private Image mode Page 6

7 4. PXE boot to the vdisk in Private Image mode to rearm: For Office 2010: Program Files(x86)\Common Files\microsoft shared\officesoftwareprotectionplatform\ospprearm.exe Repeat for Windows Vista, 7, 2008, & 2008R2: Run cscript.exe slmgr.vbs -rearm 5. Shutdown the target device 6. In the Console, right-click on the vdisk, then select the File Properties menu option 7. Click on the Microsoft Volume Licensing tab, then change the license option from None to KMS 8. On the Mode tab, set the vdisk access mode to Standard Image mode 9. Stream the vdisk to one or more target devices Note: Admin s can validate the KMS configuration was successful by verifying that the CMID for each device is unique. For Windows Vista, 7, 2008, and 2008R2: Run cscript.exe slmgr.vbs dlv For Office 2010: Run C:\Program Files\Microsoft Office\Office14\cscript ospp.vbs /dcmid III. Important Information on Rearm: Microsoft limits the number of times you can run rearm on an installed OS Image and Office. The Operating System and Office will need to be reinstalled accordingly if the number of allowed rearm attempts is exceeded. However in all of the above cases for a successful KMS configuration for a PVS vdisk, you will never need to rearm the vdisk except the first time when you configure it. We recommend that you rearm the system booted from the vdisk in Private Image mode so that the master target device hard disk's rearm count is not reduced. Page 7