I might split this off since KMS doesn’t need Citrix and Citrix doesn’t need KMS. But for my environment I needed both.<\/p>\n
Background<\/strong> I actually ended up installing KMS on the WSUS server. Things I found out (my notes, take with a grain of salt since I haven’t gone back over it nor verified anything):<\/p>\n Prerequisites<\/strong><\/p>\n Common Client KMS Setup Keys<\/strong> Windows 7 Professional Install And Activate Your KMS Server<\/strong> You can also use the Volume Activation Management Tool<\/a> (VAMT).<\/p>\n KMS For Office Products<\/strong> Verify KMS Is Working<\/strong> Citrix – Initial Setup<\/strong><\/p>\n Updating the Master Image<\/strong><\/p>\n ***EDIT*** Port 1688 The eventviewer showed “The client has sent an activation request to the key management service machine” along with “0xC0020017, 0X00000000, 127.0.0.1:1688” You can change this by setting the host: To set this back to default: To change the key: Remote key: http:\/\/technet.microsoft.com\/en-us\/library\/ee624350.aspx<\/p>\n NON-Domain Systems KMS Activation I might split this off since KMS doesn’t need Citrix and Citrix doesn’t need KMS. But for my environment I needed both. Background I had installed a KMS server (Key Management Services server) for a recently-deployed Citrix XenDesktop environment. XenDesktop does NOT support MAK keys for the shared desktops (although it technically works), and instead … Continue reading KMS Setup and Citrix XenDesktop<\/span>
\nI had installed a KMS server (Key Management Services server) for a recently-deployed Citrix XenDesktop environment. XenDesktop does NOT support MAK keys for the shared desktops (although it technically works), and instead lets me know to use KMS. KMS is really nice now that it’s working.<\/p>\n\n
\nFull List found here (http:\/\/technet.microsoft.com\/en-us\/library\/jj612867.aspx<\/a> and http:\/\/technet.microsoft.com\/en-us\/library\/jj219430.aspx<\/a>)<\/p>\n
\nFJ82H-XT6CR-J8D7P-XQJJ2-GPDD4<\/code>
\nWindows 7 Enterprise
\n33PXH-7Y6KF-2VJC9-XBBR8-HVTHH<\/code>
\nWindows 8 Professional
\nNG4HW-VH26C-733KW-K6F98-J8CK4<\/code>
\nWindows 8.1 Professional
\nGCRJD-8NW9H-F2CDX-CCM8D-9D6T9<\/code>
\nWindows 8 Enterprise
\n32JNW-9KQ84-P47T8-D8GGY-CWCK7<\/code>
\nWindows 8.1 Enterprise
\nMHF9N-XY6XB-WVXMC-BTDCT-MKKG7<\/code>
\nWindows Server 2008 R2 Standard
\nYC6KT-GKW9T-YTKYR-T4X34-R7VHC<\/code>
\nWindows Server 2008 R2 Enterprise
\n489J6-VHDMP-X63PK-3K798-CPX3Y<\/code>
\nWindows Server 2012 Standard
\nXC9B7-NBPP2-83J2H-RHMBY-92BT4<\/code>
\nWindows Server 2012R2 Standard
\nD2N9P-3P6X9-2R39C-7RTCD-MDVJX<\/code>
\nWindows Server 2012 Datacenter
\n48HP8-DN98B-MYWDG-T2DCC-8W83P<\/code>
\nWindows Server 2012R2 Datacenter
\nW3GGN-FT8W3-Y4M27-J84CP-Q3VJ9<\/code>
\nOffice Professional Plus 2010
\nVYBBJ-TRJPB-QFQRF-QFT4D-H3GVB<\/code>
\nOffice Professional Plus 2013
\nYC7DK-G2NP3-2QQC3-J6H88-GVGXT<\/code><\/p><\/blockquote>\n
\nAdd the product key (your KMS key from the VLSC) on your server and activate with Microsoft. If you utilize the GUI you will receive an alert saying “Are you sure you want this to become a KMS Server in your environment?” I used the command line instead:
\nslmgr \/ipk YOURPRODUCTKEYHERE<\/code>
\nslmgr \/ato<\/code>
\nIf you receive any errors, you will not be able to proceed much further.<\/p>\n
\nDownload the Office 2010 KMS Host License Pack
\nhttp:\/\/www.microsoft.com\/downloads\/en\/details.aspx?displaylang=en&FamilyID=97b7b710-6831-4ce5-9ff5-fdc21fe8d965<\/a>
\nAnd install\/run the executable
\nThe wizard will ask for your KMS key for Office – enter that.
\nTo install a new Office Key, simply type:
\nospp \/inpkey:YOURKMSKEY<\/code>
\nospp \/act<\/code><\/p>\n
\nYou must have 5 or more SERVER clients or 25 or more CLIENT clients trying to activate. Every 6 months. The KMS activation is good for 180 days before it needs to re-register with your KMS server.
\nCommand line find out the number of activations
\nslmgr \/dlv<\/code>
\nYour pop up will display the following key information: The KMS channel your server belongs to (B channel for me), License status, Current KMS count, and number of requests received.
\nThere is a KMS Emulator that can artificially inflate your numbers on the KMS server:
\nKMSClient.exe 1688 127.0.0.1 Windows<\/code>
\nKMSClient.exe 1688 127.0.0.1 Office2010<\/code>
\nKMSClient.exe 1688 127.0.0.1 Office2012<\/code><\/p>\n
\n\n
\nslmgr \/rearm<\/code><\/p>\n\n
\nslmgr \/rearm<\/code><\/p>\n
\nI couldn’t get my office 2010 laptop to activate against the KMS host. I verified that the DNS entry was added:
\nnslookup -type=srv _vlmcs._tcp<\/code><\/p>\n
\nSrv hostname MYSERVER.MYDOMAIN.TLD<\/p><\/blockquote>\n
\nThat’s why! 127.0.0.1! Localhost my arse.<\/p>\n
\nOpen a command prompt with admin privs
\ncd\\program files\\microsoft office\\office14 (or 15)<\/code>
\ncscript ospp.vbs \/sethst:YOURSERVER_FQDN.domain.tld<\/code>
\nThen activate
\ncscript ospp.vbs \/act<\/code>
\nSuccess!<\/p>\n
\ncscript ospp.vbs \/remhst<\/code><\/p>\n
\ncscript ospp.vbs \/inpkey:YOURKEYHERE<\/code><\/p>\n
\ncscript ospp.vbs \/inpkey:KEY COMPUTERNAME<\/code>
\ncscript ospp.vbs \/act COMPUTERNAME<\/code><\/p>\n
\ncscript \\windows\\system32\\slmgr.vbs \/skms FQDN_OF_KMS_SERVER:port<\/code>
\n-or-
\ncscript \\windows\\system32\\slmgr.vbs \/skms IPADDRESS_OF_KMS:port<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"