Nope not that either
id say firewall, even if its turned off any services which are disabled remain disabled might be worth checking.
theres a nice category name "KMS Keymanagement" in the firewall rules on the server and the client.
Nope not that either
worth mentioning that if you install windows or office with a KMS key it will attempt to update your DNS and the srv records which can mean the machine get pointed to an incorrect host (ive had this before)
Must be something dumb I'm doing, is there anything on the server I'm supposed to do ?Code:Server: server.local Address: 192.168.0.1 _vlmcs._tcp.local SRV service location: priority = 10 weight = 0 port = 1688 svr hostname = server.local server.local internet address = 192.168.0.1
port whatever kms uses open on the servers firewall? can you ping/ talk to that server?
You mentioned you've just installed this, have you activated the KMS host? (sorry for an obvious question, but I figure better to never assume).
Probably not what do I need to do that ? - Is this installing the KMS key on the server itself ? eg on server 2008r2 install the KMS key for server 2008r2 ?
Installing KMS Hosts
Install and activate a KMS key on a Windows 7 or Windows Server 2008 R2 computer by using an elevated command prompt:
To install a KMS key, type slmgr.vbs /ipk <KmsKey> at a command prompt.
To activate online, type slmgr.vbs /ato at a command prompt.
To activate by using the telephone, type slui.exe 4 at a command prompt.
After activating the KMS key, restart the Software Protection Service.
Okay, guess I missed that bit, I'm guessing it's installed as slmgr.bs /dli is saying its enabled - still can't activate anything (same error) but it does say total requests received 3 - so I guess it's working ?
sounds better, the count will go up till the min limit has been reached and then clients will activate
rather than sit in the grace period
Im getting the same here
Im trying to discover computers and some are connecting and some are coming up with "Can not connect to WMI service...."
1) the device is off
2) the firewall ports are not open
on the client devices I believe you need the following (a reboot of the device will be required if you enable any of the below)
Key Management Service (TCP-in)
Windows Management Instrumentation (ASync -In)
Windows Management Instrumentation (DCOM-In)
Windows Management Instrumentation (WMI-In)
Windows Management Instrumentation (WMI-Out)
newpersn (8th November 2013)
For Windows Server and Client OS activation, you only register ONE KMS key with your KMS host, the highest level OS you are licenced for.
Example, if you have licences for Windows 7, Windows 8, Windows 8.1, Server 2008 R2 and Server 2013 R2:
1. Login to the MS Volume Licence Service Centre: https://www.microsoft.com/Licensing/...r/default.aspx
2.a Get your highest level OS KMS Key - in this example, it would be 2012 R2
2.b If you didnt have any Server OS KMS keys, you would register your highest level Client OS (Windows 8.1 for example)
3.a Install the following update if your KMS server is not 2012 R2 - Update adds support for Windows 8.1 and Windows Server 2012 R2 clients to Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 KMS hosts
3.b Register your 2012 R2 key (from Microsoft licencing) with your KMS server - Installing KMS Hosts
4. When installing Windows 7 / 8 / 8.1 / 2008 / 2012 to be activated, use the following KMS keys during their installation procedure: Appendix A: KMS Client Setup Keys (Server OS's and Enterprise client OS's should have these keys embedded by default. You can use this page to input them again if youre unsure)
Server OS's (2003/2008/2012) wont activate until the KMS server has 5 requests
Client OS's (7 / 8 / 8.1) - 25 requests
Office - 10 requests
Be aware that if you setup two KMS servers for redundancy, each server will require the minimum requests before they will start activating.
Office 2010 and 2013 require separate KMS keys to be added to your server, you also need to install ONE key per version (1 for 2010 1 for 2013)
There are also separate installation files to support Office activation.
In total you would end up with 3 keys registered with your KMS server (your highest level OS that you have a KMS key for, office 2010, office 2013)
If your installation image isnt rearmed via sysprep then you will get problems with your activation count not going up.
They need to be rearmed to generate their own unique ID - this is used when requesting activation, when the same ID is used for each PC, the KMS server will only see one request (from the same ID multiple times).
Last edited by Frazer; 8th November 2013 at 12:12 PM.
There are currently 2 users browsing this thread. (0 members and 2 guests)