{"id":5489,"date":"2013-08-09T14:04:55","date_gmt":"2013-08-09T12:04:55","guid":{"rendered":"https:\/\/ingmarverheij.com\/?p=5489"},"modified":"2014-07-02T20:26:19","modified_gmt":"2014-07-02T18:26:19","slug":"citrix-pvs-enabling-kms-licensing-on-a-vdisk","status":"publish","type":"post","link":"https:\/\/ingmarverheij.com\/en\/citrix-pvs-enabling-kms-licensing-on-a-vdisk\/","title":{"rendered":"Citrix PVS: Enabling KMS licensing on a vDisk"},"content":{"rendered":"

\"\"<\/a>When streaming a Windows machine the Windows license can be managed by a Key Management System<\/a> (KMS). Citrix describes it as follows \u201cKMS volume licensing utilizes a centralized activation server that runs in the datacenter, and servers as a local activation point (opposed to having each system activate with Microsoft over the internet).<\/em>\u201d<\/p>\n

To ensure KMS is working correctly the Windows machine needs to be prepared for KMS, this involves setting the right license key and \u201cre-arming\u201d the license. Citrix has done a pretty good job describing different scenarios in CTX128276<\/a> and explaining which actions to take, but there are more steps involved.<\/p>\n

In this article I\u2019ll explain what steps you can take to build a PVS vDisk where licensed are managed by KMS and how to troubleshoot some known caveats.<\/p>\n

<\/p>\n

How to prepare your image<\/h1>\n

Creating a Citrix PVS vDisk for Windows machines that are licensed by a Key Management System (KMS) consists of the following eight steps:<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

1) Create vDisk<\/h6>\n

Build your image as you normally would (install your OS, applications and apply the required configuration) and upload the using the imaging wizard<\/strong>. Build a new image and select the Key Management Service <\/strong>(KMS) in the Microsoft Volume Licensing <\/strong>dialog.<\/p>\n

\"Provisioning<\/a>\"Provisioning<\/a>\"Provisioning<\/a>\"Provisioning<\/a>\"Provisioning<\/a>\"Provisioning<\/a>\"Provisioning<\/a>\"Provisioning<\/a>\"Provisioning<\/a>\"Provisioning<\/a><\/p>\n

After the vDisk is created and the target device <\/strong>is assigned to the new vDisk <\/strong>reboot the machine. Boot from Network (or the Boot Device Manager via ISO<\/a> or VHD<\/a>) so the machine will mount <\/strong>the vDisk in private <\/strong>mode.<\/p>\n

\"2013-08-09<\/a><\/p>\n

After you logon with a user (with administrative privileges) the files are converted from volume C: to the vDisk<\/strong>, in other words: the content of the C: drive is copied to the vDisk on the PVS server.<\/p>\n

\"Citrix<\/a>\"Citrix<\/a><\/p>\n

After the content is copied click Finish <\/strong>to continue to the shell.<\/p>\n

 <\/p>\n

2) Cleanup windows activation<\/h6>\n

To start with a clean setup we can cleanup the Windows activation. Run a command prompt with elevated privileges (run as administrator) and issue the following commands:<\/p>\n

Net Stop SpPSvc\r\nDel C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Roaming\\Microsoft\\SoftwareProtectionPlatform\\tokens.dat\r\nNet Start SpPSvc<\/pre>\n
\"Cleanup<\/a><\/em><\/p>\n

Source: How to rebuild the Tokens.dat or Activation Tokens file in Windows 7 | 8<\/a><\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n
3) Install KMS product key\u00a0 (Windows)<\/h6>\n
Now we need to ensure that Windows has a KMS product key (instead of a OEM or VLK). From an elevated command prompt: Run the Software Licensing Management Tool (SlMgr) and install the \"SlMgr<\/a>KMS product key (\/IPK) for your Windows version.<\/p>\n
SlMgr \/IPK <ProductKey><\/pre>\n

\n<\/em><\/p>\n

See the tables attached to this article for the KMS client key for your Windows version<\/p>\n
 <\/p>\n
 <\/p>\n
4) Activate Windows<\/h6>\n
To verify that the license key is a KMS license key and the license can be activated by a KMS server we can test the activation. \"SlMgr<\/a>Run the Software Licensing Management Tool (SlMgr) and activate Windows (\/ATO).<\/p>\n
SlMgr \/ATO<\/pre>\n
 <\/p>\n
Verbose information about the licensing can be retrieved with the Software Licensing Management Tool.<\/p>\n
SlMgr \/DLV<\/pre>\n
\"SlMgr<\/a><\/p>\n
 <\/p>\n
As you can see the License Status is Licensed<\/strong>. If you have any other result first troubleshoot that (see Microsoft TechNet – How to troubleshoot the Key Management Service (KMS)<\/a>).<\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n
5) Re-arm Windows license<\/h6>\n
Since we\u2019re going to distribute this vDisk to multiple machines we need to reset it to a non-activated state using the rearm command. Run the Software Licensing Management Tool (SlMgr)\"SlMgr<\/a> and reset the licensing status of the machine (\/ReArm).<\/p>\n
SlMgr \/ReArm<\/pre>\n
 <\/p>\n
Do\u00a0 \/\/\u00a0 NOT\u00a0 \/\/\u00a0 <\/em><\/strong>reboot the machine<\/p>\n
\"Error:<\/a><\/p>\n
If you have exceeded the maximum of 3 allowed rearms an error message is thrown \u201cError: 0xC004D307 The maximum allowed number of re-arms has been exceeded. You must re-install the OS before trying to re-arm again\u201d. This can be solved by setting the following registry key:<\/em> HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\SoftwareProtectionPlatform\\SkipRearm = 0x1 (REG_DWORD).<\/em><\/p>\n
 <\/p>\n
6) Install KMS product key (Office)<\/h6>\n
In case you\u2019ve installed Microsoft Office and need to license it via KMS,\u00a0 nearly the same steps are required. Run the Office Software Protection Platform (OsPP.vbs) and install the product key (\/InPKey) for your Office version.<\/p>\n
cscript.exe ospp.vbs \/InPKey:<ProductKey><\/pre>\n
\"cscript.exe<\/a><\/em><\/p>\n

See the tables attached to this article for the KMS client key for your Office version<\/p>\n
 <\/p>\n
You can verify if Office generated a Client Machine ID (CMID) by running the Office Software Protection Platform tool with \/dcmid.<\/p>\n
cscript.exe ospp.vbs \/dcmid<\/pre>\n
\"cscript.exe<\/a><\/em><\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n
7) Re-arm Office license<\/h6>\n
Just like Windows, Office also needs to be to reset to a non-activated state using the rearm command. Run the Office Software Protection Plafrom Rearm (OSPPREARM) tool from the x86 location.<\/p>\n
C:\\Program Files\\Common Files\\microsoft shared\\OfficeSoftwareProtectionPlatform\\OSPPREARM.EXE\r\nor\r\nC:\\Program Files (x86)\\Common Files\\microsoft shared\\OfficeSoftwareProtectionPlatform\\OSPPREARM.EXE<\/pre>\n
\"OSPPREARM.EXE\"<\/a><\/p>\n
 <\/p>\n
8) Put vDisk in Standard mode<\/h6>\n
Unlock vDisk<\/span><\/h5>\n
Shut down the target device and wait until the vDisk changes from locked (1) to unlocked (0).<\/p>\n

\"vDisk<\/a>\u00a0 
\"vDisk<\/a><\/p>\n
<\/h5>\n
 <\/p>\n
Set Access Mode<\/span><\/h5>\n
Open the properties of the vDisk and set the Access Mode <\/strong>to \u201cStandard Image (multi-device, read-only access)<\/strong>\u201d and verify that Key \u201cManagement Service (KMS)\u201d <\/strong>is selected at the Microsoft Volume Licensing <\/strong>tab.<\/p>\n
\"vDisk<\/a>\"vDisk<\/a><\/p>\n
What\u2019s important to know is that the Citrix PVS Stream Service at the moment will mount <\/strong>the vDisk, execute a KmsPrep – <\/strong>or KmsReset <\/strong>if this has been done before – and then unmount it again. This only happens if you change the Access Mode from Private to Standard. If the Access Mode is already in Standard and KMS is selected, the image is NOT<\/em><\/span> updated.<\/strong><\/p>\n
As Citrix describes in Managing Microsoft KMS Volume Licensing<\/a>\u00a0\u201cNote: When preparing or updating a KMS configured vDisk that will be copied or cloned, it is important to complete the final KMS configuration task, which is to change the vDisk mode from Private Image Mode to Shared Image Mode, before copying or cloning the vDisk to other Provisioning Servers. Also, both the .pvp and .vhd file must be copied to retain the properties and KMS configuration of the original vDisk\u201d<\/em><\/p>\n
 <\/p>\n
Error
\n<\/span><\/p>\n
 <\/p>\n
In case the following error is thrown \u201cAn unexpected MAP error occurred – Failed to map vDisk, no Driver<\/strong>\u201d there are two possible problem. 1) The drivers are not installed correctly or 2) the account configured at the Streaming service had insufficient privileges.<\/p>\n

\"An<\/a><\/p>\n
1) Drivers are not installed correctly
\n<\/span><\/p>\n
 <\/p>\n
The first problem is easy to detect and solve. Try to mount <\/strong>the vDisk (right-click on the vDisk > Mount vDisk) from the Provisioning Services Console on the PVS server. If that does not work the drivers <\/strong>are not correctly installed. Go to C:\\Program Files\\Citrix\\Provisioning Services\\drivers<\/strong>, right-click on cfsdep2.inf<\/strong> and click Install<\/strong>.<\/p>\n
2) Insufficient privileges
\n<\/span><\/p>\n
 <\/p>\n
If you\u2019re able to mount the vDisk from the Provisioning Service Console then the Citrix PVS Stream Service has insufficient privileges<\/strong>. The account <\/strong>configured to run the Citrix PVS Stream Service needs to have the Perform volume maintenance tasks<\/a> (SE_MANAGE_VOLUME_NAME) privilege. The reason this privileges is required is because the Citrix PVS Stream service need to mount the vDisk in order to execute the KmsPrep \/ KmsReset. See CTX132995<\/a> for details.<\/em><\/p>\n
\"Citrix<\/a><\/p>\n
By default only the local Administrators <\/strong>group has the SE_MANAGE_COLUME_NAME privilege assigned. The problem can be solved by making the AD account, or NETWORK SERVICE <\/strong>when log on as \u201cLocal System account\u201d is used, member of the local Administrators group. If you don\u2019t want to add NETWORK SERVICE to the local Administrators group \u2013 which I don\u2019t recommend <\/em>\u2013 the privilege can be assigned in the security policy: Windows Settings > Security Settings > Local Polies > User Rights Assignment > Perform volume maintenance tasks<\/em><\/p>\n
\"Perform<\/a><\/p>\n
 <\/p>\n
 <\/p>\n
Verify license activation<\/h1>\n
Boot another <\/strong>target device, a different <\/strong>machine then where you created the image\/vDisk, and login with an administrative account.<\/p>\n
Open an command prompt with elevated privileges and retrieve verbose information about the licensing with the Software Licensing Management Tool.<\/p>\n
SlMgr \/DLV<\/pre>\n
\"License<\/a><\/p>\n
Initially the machine is not <\/strong>licensed, instead the license status is \u201cAdditional grace period <\/strong>(KMS license expired or hardware out of tolerance\u201d.<\/p>\n
During boot the Software Protection Service (Security-SPP) notices that hardware has changed. Besides different hardware is the Client Machine ID (CMID)\u00a0 is changed, this is expected as each machine needs a unique ID.<\/p>\n
 <\/p>\n

In the Application<\/strong> log in the Event Viewer\u00a0 you\u2019ll find an event from Security-SPP <\/strong>with ID 1040<\/strong> informing that \u201cHardware has changed from previous boot<\/strong>\u201d, immediately followed by ID 1025<\/strong> \u201cGrace period<\/strong> has been started. Grace days=30 Grace type=1\u201d\u00a0 and ID 1024<\/strong> \u201cThe hardware has changed\u201d<\/p>\n
\"Event<\/a>\"Event<\/a>\"Event<\/a><\/p>\n
After 30 minutes (up to 2 hours<\/a>) the client will sent an activation request to the KMS server. Sure enough the KMS server will grant the license and the client is licensed. In the event log an event is raised by Security-SPP <\/strong>with ID 12288 <\/strong>when an activation is requested, ID 12289 <\/strong>when a response is received and finally ID 1003 <\/strong>when the license status check <\/strong>is completed.<\/p>\n
\"Event<\/a>\"Event<\/a>\"Event<\/a><\/p>\n
Again open an command prompt with elevated privileges and retrieve verbose information about the licensing with the Software Licensing Management Tool.<\/p>\n
SlMgr \/DLV<\/pre>\n
\"License<\/a><\/p>\n
The license is no longer in grace period<\/strong>, it is now licensed<\/strong>.<\/p>\n
 <\/p>\n
KMS keys<\/h1>\n
The KMS keys are provided by Microsoft, it\u2019s not a secret. For your convenience I listed all known products keys in tables below.<\/p>\n
 <\/p>\n
Microsoft Windows<\/h6>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Product<\/strong><\/td>\nEdition<\/strong><\/td>\nProduct key<\/strong><\/td>\n<\/tr>\n
Vista<\/td>\nBusiness<\/td>\nYFKBB-PQJJV-G996G-VWGXY-2V3X8<\/td>\n<\/tr>\n
<\/td>\nBusiness N<\/td>\nHMBQG-8H2RH-C77VX-27R82-VMQBT<\/td>\n<\/tr>\n
<\/td>\nEnterprise<\/td>\nVKK3X-68KWM-X2YGT-QR4M6-4BWMV<\/td>\n<\/tr>\n
<\/td>\nEnterprise N<\/td>\nVTC42-BM838-43QHV-84HX6-XJXK<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
7<\/td>\nProfessional<\/td>\nFJ82H-XT6CR-J8D7P-XQJJ2-GPDD4<\/td>\n<\/tr>\n
<\/td>\nProfessional N<\/td>\nMRPKT-YTG23-K7D7T-X2JMM-QY7MG<\/td>\n<\/tr>\n
<\/td>\nProfessional E<\/td>\nW82YF-2Q76Y-63HXB-FGJG9-GF7QX<\/td>\n<\/tr>\n
<\/td>\nEnterprise<\/td>\n33PXH-7Y6KF-2VJC9-XBBR8-HVTHH<\/td>\n<\/tr>\n
<\/td>\nEnterprise N<\/td>\nYDRBP-3D83W-TY26F-D46B2-XCKRJ<\/td>\n<\/tr>\n
<\/td>\nEnterprise E<\/td>\nC29WB-22CC8-VJ326-GHFJW-H9DH4<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
8<\/td>\nProfessional<\/td>\nNG4HW-VH26C-733KW-K6F98-J8CK4<\/td>\n<\/tr>\n
<\/td>\nProfessional N<\/td>\nXCVCF-2NXM9-723PB-MHCB7-2RYQQ<\/td>\n<\/tr>\n
<\/td>\nEnterprise<\/td>\n32JNW-9KQ84-P47T8-D8GGY-CWCK7<\/td>\n<\/tr>\n
<\/td>\nEnterprise N<\/td>\nJMNMF-RHW7P-DMY6X-RF3DR-X2BQT<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
Server 2008<\/td>\nStandard<\/td>\nTM24T-X9RMF-VWXK6-X8JC9-BFGM2<\/td>\n<\/tr>\n
<\/td>\nStandard without Hyper-V<\/td>\nW7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ<\/td>\n<\/tr>\n
<\/td>\nEnterprise<\/td>\nYQGMW-MPWTJ-34KDK-48M3W-X4Q6V<\/td>\n<\/tr>\n
<\/td>\nEnterprise without Hyper-V<\/td>\n39BXF-X8Q23-P2WWT-38T2F-G3FPG<\/td>\n<\/tr>\n
<\/td>\nHPC<\/td>\nRCTX3-KWVHP-BR6TB-RB6DM-6X7HP<\/td>\n<\/tr>\n
<\/td>\nDatacenter<\/td>\n7M67G-PC374-GR742-YH8V4-TCBY3<\/td>\n<\/tr>\n
<\/td>\nDatacenter without Hyper-V<\/td>\n22XQ2-VRXRG-P8D42-K34TD-G3QQC<\/td>\n<\/tr>\n
<\/td>\nFor Itanium-Based Systems<\/td>\n4DWFP-JF3DJ-B7DTH-78FJB-PDRHK<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
Server 2008 R2<\/td>\nWeb<\/td>\n6TPJF-RBVHG-WBW2R-86QPH-6RTM4<\/td>\n<\/tr>\n
<\/td>\nHPC edition<\/td>\nTT8MH-CG224-D3D7Q-498W2-9QCTX<\/td>\n<\/tr>\n
<\/td>\nStandard<\/td>\nYC6KT-GKW9T-YTKYR-T4X34-R7VHC<\/td>\n<\/tr>\n
<\/td>\nEnterprise<\/td>\n489J6-VHDMP-X63PK-3K798-CPX3Y<\/td>\n<\/tr>\n
<\/td>\nDatacenter<\/td>\n74YFP-3QFB3-KQT8W-PMXWJ-7M648<\/td>\n<\/tr>\n
<\/td>\nFor Itanium-based Systems<\/td>\nGT63C-RJFQ3-4GMB6-BRFB9-CB83V<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
Server 2012<\/td>\nCore<\/td>\nBN3D2-R7TKB-3YPBD-8DRP2-27GG4<\/td>\n<\/tr>\n
<\/td>\nCore N<\/td>\n8N2M2-HWPGY-7PGT9-HGDD8-GVGGY<\/td>\n<\/tr>\n
<\/td>\nCore Single Language<\/td>\n2WN2H-YGCQR-KFX6K-CD6TF-84YXQ<\/td>\n<\/tr>\n
<\/td>\nCore Country Specific<\/td>\n4K36P-JN4VD-GDC6V-KDT89-DYFKP<\/td>\n<\/tr>\n
<\/td>\nServer Standard<\/td>\nXC9B7-NBPP2-83J2H-RHMBY-92BT4<\/td>\n<\/tr>\n
<\/td>\nStandard Core<\/td>\nXC9B7-NBPP2-83J2H-RHMBY-92BT4<\/td>\n<\/tr>\n
<\/td>\nMultiPoint Standard<\/td>\nHM7DN-YVMH3-46JC3-XYTG7-CYQJJ<\/td>\n<\/tr>\n
<\/td>\nMultiPoint Premium<\/td>\nXNH6W-2V9GX-RGJ4K-Y8X6F-QGJ2G<\/td>\n<\/tr>\n
<\/td>\nDatacenter<\/td>\n48HP8-DN98B-MYWDG-T2DCC-8W83P<\/td>\n<\/tr>\n
<\/td>\nDatacenter Core<\/td>\n48HP8-DN98B-MYWDG-T2DCC-8W83P<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Source: Microsoft TechNet<\/a><\/em><\/p>\n
 <\/p>\n
Microsoft Office<\/h6>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Type<\/strong><\/td>\nVersion<\/strong><\/td>\nEdition<\/strong><\/td>\nProduct key<\/strong><\/td>\n<\/tr>\n
Suites<\/td>\n2010<\/td>\nOffice Professional Plus<\/td>\nVYBBJ-TRJPB-QFQRF-QFT4D-H3GVB<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nOffice Standard<\/td>\nV7QKV-4XVVR-XYV4D-F7DFM-8R6BM<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
<\/td>\n2013<\/td>\nOffice Professional Plus<\/td>\nYC7DK-G2NP3-2QQC3-J6H88-GVGXT<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nOffice Standard<\/td>\nKBKQT-2NMXY-JJWGP-M62JB-92CD4<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
Stand-alone products<\/td>\n2010<\/td>\nAccess<\/td>\nV7Y44-9T38C-R2VJK-666HK-T7DDX<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nExcel<\/td>\nH62QG-HXVKF-PP4HP-66KMR-CW9BM<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nSharepoint Workspace<\/td>\nQYYW6-QP4CB-MBV6G-HYMCJ-4T3J4<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nInfoPath<\/td>\nK96W8-67RPQ-62T9Y-J8FQJ-BT37T<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nOneNote<\/td>\nQ4Y4M-RHWJM-PY37F-MTKWH-D3XHX<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nOutlook<\/td>\n7YDC2-CWM8M-RRTJC-8MDVC-X3DWQ<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nPowerPoint<\/td>\nRC8FX-88JRY-3PF7C-X8P67-P4VTT<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nProject Professional<\/td>\nYGX6F-PGV49-PGW3J-9BTGG-VHKC6<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nProject Standard<\/td>\n4HP3K-88W3F-W2K3D-6677X-F9PGB<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nPublisher<\/td>\nBFK7F-9MYHM-V68C7-DRQ66-83YTP<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nVisio Premium<\/td>\nD9DWC-HPYVV-JGF4P-BTWQB-WX8BJ<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nVisio Professional<\/td>\n7MCW8-VRQVK-G677T-PDJCM-Q8TCP<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nVisio Standard<\/td>\n767HD-QGMWX-8QTDB-9G3R2-KHFGJ<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nWord<\/td>\nHVHB3-C6FV7-KQX9W-YQG79-CRY7T<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
<\/td>\n2013<\/td>\nAccess<\/td>\nNG2JY-H4JBT-HQXYP-78QH9-4JM2D<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nExcel<\/td>\nVGPNG-Y7HQW-9RHP7-TKPV3-BG7GB<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nInfoPath<\/td>\nDKT8B-N7VXH-D963P-Q4PHY-F8894<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nLync<\/td>\n2MG3G-3BNTT-3MFW9-KDQW3-TCK7R<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nOneNote<\/td>\nTGN6P-8MMBC-37P2F-XHXXK-P34VW<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nOutlook<\/td>\nQPN8Q-BJBTJ-334K3-93TGY-2PMBT<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nPowerPoint<\/td>\n4NT99-8RJFH-Q2VDH-KYG2C-4RD4F<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nProject Professional<\/td>\nFN8TT-7WMH6-2D4X9-M337T-2342K<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nProject Standard<\/td>\n6NTH3-CW976-3G3Y2-JK3TX-8QHTT<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nPublisher<\/td>\nPN2WF-29XG2-T9HJ7-JQPJR-FCXK4<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nVisio Professional<\/td>\nC2FG9-N6J68-H8BTJ-BW3QX-RM3B3<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nVisio Standard<\/td>\nJ484Y-4NKBF-W2HMG-DBMJC-PGWR7<\/td>\n<\/tr>\n
<\/td>\n<\/td>\nWord<\/td>\n6Q7VD-NX8JD-WJ2VH-88V73-4GBJ7<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Source: Office 2010<\/a>, Office 2013<\/a><\/em><\/p>\n
 <\/p>\n
Resources<\/h1>\n