Citrix.com / Support
Citrix
Include legacy content
Self-help Resources
Alerts
Contact Support

Configuring KMS Licensing for Windows and Office 2010 and 2013

  • CTX128276
  • Created onMar 26, 2014
  • Updated onFeb 11, 2015
Article Topic :  Configuration, Licensing
See Applicable Products

Information

This article contains information for administrator about configuring the Provisioning Services (PVS) 5.6 Service Pack 1 (or later) Target Devices that are using Microsoft Key Management Server (KMS) in the best way to fit their environment.

Background

KMS can be configured on the virtual disk (vDisk) image with the help of PVS to apply volume licenses for Microsoft Server 2008, Microsoft Server 2008 R2, Microsoft Server 2012, Windows 7 and Windows Vista, as well as Office 2010 and 2013.

In PVS, the option for KMS can be easily configured while building vDisks 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.

Note: Information in this article applies only to the Windows OS and Office versions specified.

KMS Configuration Scenarios

The following section outlines the steps to configure KMS in various scenarios to accommodate specific deployment environment. Read all the scenarios to verify which one best fits your deployment and follow the procedures accordingly.

Notes:

  • Citrix recommends that the administrators complete all the steps in the proper order for a successful configuration.

  • SOAP/Stream Service account must be a member of local administrator group in PVS Servers.

KMS configuration can be done in the following ways in accordance with various environments. The customers can configure KMS for:

  • Both Windows and Office

  • Only Windows

  • Only Office

The following scenarios help the administrator to configure KMS accordingly:

Scenario 1: Configuring KMS for the first time to a pre-existing vDisk

Assumptions

A vDisk was pre-built using a tool like XenConvert or the Imaging wizard (with Microsoft Licensing Option set to None).

  • For both Windows and Office: A vDisk that has operating system and Office installed on it is pre-built using XenConvert/Imaging Wizard but KMS has never been configured.

  • For only Windows or only Office: A vDisk that has the operating system installed on it (Optional: Office is included in the image); that was pre-built using XenConvert/Imaging wizard but KMS has never been configured.

Procedure

Note: It is important to perform this operation on a system started from the vDisk in Private Image mode so that the rearm count of the master target device hard disk is not reduced. Also, when the system is rearmed, it is not required to rearm it again.

  1. Open PVS Server and in the Console, right-click the vDisk and select Properties.

  2. Click the Microsoft Volume Licensing tab and set the licensing option to None.

  3. Start the device from the vDisk in Private Image mode.

  4. Rearm the system for both Windows and Office, one after the other. If KMS is configured for “Only” one of them, then select your option to rearm one of them accordingly:

  • For Windows Vista, 7, 2008, and 2008 R2: Run cscript.exe slmgr.vbs -rearm

  • For Office (64-bit client): Program Files(x86)\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE

  • For Office (32-bit client): Program Files\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE

  • For Office 2013  (64-bit client): Program Files(x86)\Microsoft Office\Office15\OSPPREARM.EXE

  • For Office 2013  (32-bit client): Program Files\Microsoft Office\Office15\OSPPREARM.EXE

  1. A message appears to reboot the system. Do not reboot - instead, shut down the target device.

  2. Open PVS Server and in the Console, right-click the vDisk and select Properties.

  3. Click the Microsoft Volume Licensing tab and set the licensing option to KMS.

  4. On the Mode tab, set the vDisk access mode to Standard Image mode.

  5. Stream the vDisk to one or more target devices.

    Note: Administrators can validate that the KMS configuration was successful by verifying that the CMID for each device is unique.

  • For Windows Vista, 7, 2008, and 2008 R2: Run cscript.exe slmgr.vbs –dlv

  • For Office 2010: Run C:\Program Files\Microsoft Office\Office14\cscript ospp.vbs /dcmid

  • For Office 2013: Run C:\Program Files\Microsoft Office\Office15\cscript ospp.vbs /dcmid

Scenario 2-A: Maintaining or upgrading a vDisk image that is currently using KMS

Assumptions

A vDisk is already configured for KMS and is deployed successfully.

  • For both Windows and Office: A vDisk is already configured for KMS for both Windows and Office and is deployed successfully.

  • For only Windows or only Office: A vDisk is already configured for KMS for “Only Windows” or “Only Office” and is deployed successfully.

Procedure

  1. From the PVS Console, right-click the vDisk and select Properties.

  2. On the General tab, set the vDisk access mode to Private Image mode.

  3. Start the target device.

  4. Apply the required operating system Application/Service Pack/Update.

  5. Shut down the target device.

  6. Open PVS Server and in the Console, right-click the vDisk and select Properties.

  7. On the General tab, set the vDisk access mode to Standard Image mode.

  8. Stream the vDisk to one or more target devices.

Scenario 2-B: Maintaining or Upgrading a vDisk Image enabled with vDisk Versioning that is currently using KMS

Assumptions

A vDisk is already configured for KMS and is deployed successfully. The vDisk is enabled to use vDisk versioning, hence might already have versions.

  • For both Windows and Office: A vDisk is already configured for KMS for both Windows and Office and is deployed successfully.

  • For only Windows or only Office: A vDisk is already configured for KMS for “Only Windows” or “Only Office” and is deployed successfully.

Procedure

  1. From the PVS Console, right-click the vDisk, and select Versions.

  2. Create a new disk version.

  3. Access target device properties and set Type to Maintenance.

  4. Start the Target device.

  5. Access the target device machine and select Maintenance from the Boot menu when prompted.

  6. Apply the required operating system Application/Service Pack/Update.

  7. Shut down the target device.

  8. Access the PVS Server Console, right-click the vDisk, and select Versions. Promote the vDisk from Maintenance to Production or Test.

  9. Access the PVS Server Console. Under target device properties, change the Type to Production or Test.

  10. Stream the vDisk with this version to one or more target devices.

Scenario 3: Installing Microsoft Office to an existing KMS configured (for Windows) vDisk during Maintenance

Assumption

A vDisk is already KMS configured for Windows and is deployed successfully.

Procedure

  1. From the PVS Console, right-click the vDisk and select Properties.

  2. Click the Microsoft Volume Licensing tab and change the licensing option from KMS to None.

  3. On the General tab, set the vDisk access mode to Private Image mode.

  4. PXE boot to the vDisk in Private Image mode to rearm.

  • For Office 2010 (64-bit client): Program Files(x86)\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE

  • For Office 2010 (32-bit client): Program Files\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE
  • For Office 2013 (64-bit client): Program Files(x86)\Microsoft Office\Office15\OSPPREARM.EXE

  • For Office 2013 (32-bit client): Program Files\Microsoft Office\Office15\OSPPREARM.EXE

  • Windows Vista, 7, 2008, and 2008R2: Run cscript.exe slmgr.vbs –rearm

  1. A message is displayed to reboot the system. Do not reboot - instead, shut down the target device.

  2. In the Console, right-click the vDisk and select Properties.

  3. Click the Microsoft Volume Licensing tab and change the license option from None to KMS.

  4. On the General tab, set the vDisk access mode to Standard Image mode.

  5. Stream the vDisk to one or more target devices.

    Note: Administrators can validate that the KMS configuration was successful by verifying that the CMID for each device is unique.

  • For Windows Vista, 7, 2008, and 2008 R2: Run cscript.exe slmgr.vbs –dlv

  • For Office 2010: Run C:\Program Files\Microsoft Office\Office14\cscript ospp.vbs /dcmid

  • For Office 2013: Run C:\Program Files\Microsoft Office\Office15\cscript ospp.vbs /dcmid

Scenario 4-A: Upgrading Microsoft Office from 2010 to 2013 on an existing KMS configured (for Windows) vDisk during Maintenance

Assumption

A vDisk is already KMS configured for Windows and Microsoft Office.

Note: Microsoft Office 2013 is only supported on PVS 7.1 and later.

Procedure

  1. From the Provisioning Services Console, right-click on the vDisk and select Properties.

  2. On the General tab, set the vDisk access mode to Private Image mode.

  3. Start the target device.

  4. Run the Microsoft Office 2013 setup and choose to perform an upgrade.

  5. Reboot the target as required by the installation.

  6. Shut down the target device.

  7. Open Provisioning Services Server. In the Console, right-click on the vDisk and select Properties.

  8. On the General tab, set the vDisk access mode to Standard Image mode.

  9. Stream the vDisk to one or more target devices.

Scenario 4-B: Upgrading Microsoft Office from 2010 to 2013 on an existing KMS configured (for Windows) vDisk Image enabled with vDisk Versioning

Assumptions

A vDisk is already KMS configured for Windows and Microsoft Office.

Note: Microsoft Office 2013 is only supported on PVS 7.1 and later.

Procedure

  1. From the Provisioning Services Console, right-click the vDisk, and select Versions.

  2. Create a new disk version.

  3. Access target device properties and set Type to Maintenance.

  4. Start the target device.

  5. Access the target device machine and select Maintenance from the Boot Menu when prompted.

  6. Run the Microsoft Office 2013 setup and choose to perform an upgrade.

  7. Reboot the target as required by the installation.

  8. Shut down the Target device.

  9. Access the Provisioning Services Server Console, right-click the vDisk, and select Versions. Promote the vDisk from Maintenance to Production or Test.

  10. Access the Provisioning Services Server Console. Under target device properties, change the Type to Production or Test.

  11. Stream the vDisk with this version to one or more target devices.

Important Information on Rearm

  • Microsoft limits the number of times you can run “rearm” on an installed operating system Image and Office. The operating system and Office must be reinstalled accordingly if the number of allowed rearm attempts is exceeded.

  • However, in all of the preceding scenarios, for a successful KMS configuration for a Provisioning Services vDisk, it is not required to rearm the vDisk except the first time when it is configured.

  • Citrix recommends that you rearm the system which is started from the vDisk in Private Image mode so that the rearm count of the master target device hard disk is not reduced.

Additional Resources

Office 2010 KMS installation and troubleshooting

Plan KMS activation of Office 2010

Microsoft Office 2010 KMS Host License Pack

Rearm the Office 2013 Installation

Applicable Products

Automatic translation

Important: Non-English versions of this article are translated by an automatic translation system (also referred to as Machine Translation, or MT) and have not been translated or reviewed by a person. Citrix offers a machine translated version of this article to allow for greater access to the support content. However, automatic translation is not always perfect and may contain vocabulary, syntax or grammar errors. Citrix is not responsible for inconsistencies, errors or damage incurred as a result of the use of machine translated articles. Thank you.

Traduction automatique

Important : cet article a été traduit par un système de traduction automatique (également appelé Traduction automatique ou TA) et n'a pas été vérifié par des spécialistes. Citrix propose une traduction automatique de cet article afin de permettre à toute personne ne maîtrisant pas l'anglais d'accéder au contenu de l'assistance. Toutefois, la traduction automatique n'étant pas parfaite, elle peut contenir des erreurs de terminologie, de syntaxe ou de grammaire. Citrix n'est pas responsable des incohérences, erreurs ou dommages pouvant résulter de l'utilisation par nos clients d'articles TA.

Automatische vertaling

Belangrijk: Dit artikel is vertaald door een automatisch vertalingssysteem (ook Machine Translation of MT genoemd) en is niet vertaald of beoordeeld door mensen. Citrix biedt een machine-vertaalde versie van dit artikel aan om een betere toegang mogelijk te maken tot de support-inhoud. Automatisch vertalen werkt echter niet altijd perfect en het resultaat kan fouten bevatten in de woordkeuze, syntaxis of grammatica. Citrix is niet verantwoordelijk voor inconsistenties, fouten of schade als gevolg van het gebruik van MT-artikelen door onze klanten.

Maschinelle Übersetzung

Wichtig: Dieser Artikel wurde mit einem maschinellen Übersetzungssystem und ohne jegliche Bearbeitung durch Personen übersetzt. Citrix bietet maschinelle Übersetzungen von Artikeln an, damit Benutzer umfassenden Zugriff auf Support-Inhalte haben. Maschinelle Übersetzungen enthalten jedoch möglicherweise Fehler in Bezug auf Terminologie, Syntax und Grammatik. Citrix übernimmt keine Verantwortung für Inkonsistenzen, Fehler oder Schäden, die aus der Verwendung von maschinell übersetzten Artikeln durch Kunden resultieren.

自动翻译

重要提示：本文是由自动翻译系统翻译完成的（也称为“机器翻译”或 MT），未经人工翻译或审查。Citrix 提供本文的机器翻译版本是为了方便更多人访问支持内容。然而，自动翻译的文章并不总是完美的，可能存在词汇、语法或文法方面的错误。对于因客户使用机器翻译文章导致出现的不一致、错误或损害，Citrix 不承担任何责任。

機械翻訳

重要：この技術情報資料は機械翻訳システム（自動翻訳あるいはMTとも呼ぶ）により翻訳され、翻訳者により翻訳またはレビューされたものではありません。サポート用資料をより参照しやすくするため、Citrixはこの技術文書の機械翻訳バージョンを提供しています。しかしながら、機械翻訳の品質は翻訳者による翻訳ほど十分ではありません。誤訳や、文法、言葉使い、そのほか、たとえば日本語を母国語としない方が日本語を話すときに間違えるようなミスを含んでいる可能性があります。機械翻訳の品質、および技術情報資料の内容の誤訳やお客様が技術情報資料を利用されたことによって生じた直接または間接的な問題や損害については、いかなる責任も負わないものとします。

Tradução automática

Importante: este artigo foi traduzido por um sistema de tradução automática (também conhecido por Machine Translation ou MT) e não foi traduzido nem revisado por pessoas. A Citrix oferece uma versão traduzida por máquina deste artigo para permitir maior acesso ao conteúdo de suporte. No entanto, a tradução automática não é sempre perfeita, podendo conter erros de vocabulário, sintaxe ou gramática. A Citrix não se responsabiliza por inconsistências, erros ou danos incorridos como resultado do uso de artigos de MT de nossos clientes.

Traducción automática

Importante: Este artículo ha sido traducido por un sistema de Traducción automática (también llamada MT o Machine Translation) sin intervención de un traductor humano. Citrix ofrece la traducción automática de este artículo para ampliar el acceso a la información de asistencia técnica. No obstante, la traducción automática no es perfecta y puede contener errores de vocabulario, sintaxis y gramática. Citrix no se hace responsable de cualquier imprecisión, error o daño ocasionados por el uso que hagan nuestros clientes de los artículos traducidos automáticamente.
Languages
print
Was this helpful?
Thank you for your feedback

Share your comments or find out more about this topic

Citrix Forums