Scenario 1: Configuring KMS for the first time for a pre-existing vDiskĪ vDisk was pre-built using a tool like XenConvert or the Imaging wizard (with Microsoft Licensing Option set to None): Upgrading Microsoft Office on an existing KMS configured (for Windows) vDisk Installing Microsoft Office to an existing KMS configured (for Windows) vDisk Maintaining or Upgrading a vDisk Image enabled with vDisk Versioning that is currently using KMS Maintaining or upgrading a vDisk image that is currently using KMS Use the following scenarios to configure KMS accordingly: Configuring KMS for the first time to a pre-existing vDisk If a maintenance version is used, promote the maintenance version to production or test version set vDisk access mode from Private to Standard. Note – If the selected version of Provisioning Services supports versioning, the vDisk's private mode and maintenance version can be used interchangeably. Office and operating system are both 32-bit or 64-bit, %ProgramFiles% is Program Files.32-bit Office in 64-bit operating system, %ProgramFiles% is Program Files (x86).Program Files folder - This will be referred to as %ProgramFiles% in this document. Office Folder – This will be referred to as %Office% in this document. The KMS configuration can be done in the following ways in accordance with various environments.You can configure KMS for: The SOAP/Stream Service account must be a member of a local administrator group in PVS Servers.Citrix recommends that administrators complete all the steps in the proper order for a successful configuration.Read all the scenarios to verify which one best fits your deployment and follow the procedures accordingly. The following section outlines the steps to configure KMS in various scenarios to accommodate specific deployment environments.
Note: Information in this article applies only to specified Windows OS and Office versions. Refer to the PVS documentation for more information about managing Microsoft KMS volume licensing. Alternatively, it can be configured at any time using the Console or MCLI/PowerShell command line interfaces. In PVS, the option for KMS is configured while building vDisks using the Imaging Wizard. Refer to the Provisioning Services requirements for the operating system and Office supported in the latest version of Provisioning Services. This does not imply that the previously mentioned operating systems and Offices are supported in all versions of Provisioning Services. Note: This is only a general guide for KMS with Provisioning Services. Windows 8.1s and Microsoft Server 2012 R2.Windows 7s and Microsoft Server 2008 R2.KMS can be configured on the virtual disk (vDisk) image to apply volume licenses for operating systems and Office including: If you are using Access on a local computer, select Microsoft Office from your program menu.This article contains information for administrators about configuring Citrix Provisioning, formerly Provisioning Services (PVS) 5.6 Service Pack 1 (or later) target devices that are using the Microsoft Key Management Server (KMS) in their environment. If you are using Citrix, click on Microsoft Office Applications folder. Creating the Access Database (Tables and Relationships) from the ERD Preparation Open the Visio file created in Part A of this lab, you will reference this file in Part B. If you are not going to continue to Part B of the lab, you may close the file. You will find the orientation options on the design ribbon.) Figure 2-e f. (NOTE: The page orientation in the diagram below has been changed to landscape. OrderID now appears in the OrderLine table as a foreign key. Connect the one end to the orders entity, and the many end to the OrderLine entity. Drag a second relationship shape to the diagram. Right click and designate the attribute as a foreign key by clickiset foreign key. Add OrderID to the OrderLine table as an attribute.