+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 54
Windows Server 2008 R2 Thread, KMS Setup in Technical; id say firewall, even if its turned off any services which are disabled remain disabled might be worth checking. theres ...
  1. #31

    Join Date
    Sep 2010
    Posts
    548
    Thank Post
    26
    Thanked 62 Times in 58 Posts
    Rep Power
    19
    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.

  2. #32

    Join Date
    May 2010
    Posts
    1,017
    Thank Post
    105
    Thanked 76 Times in 62 Posts
    Rep Power
    47
    Nope not that either

  3. #33

    Join Date
    Dec 2009
    Posts
    265
    Thank Post
    6
    Thanked 31 Times in 29 Posts
    Rep Power
    15
    Quote Originally Posted by caffrey View Post
    I'm having issues with VAMT as well, just set it all up and I'm getting :-

    Code:
    0xC004F074  The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.
    DNS records are fine, even with nslookup.

    any ideas ?
    You say DNS records are fine, does this also include the _VLMCS srv record needed?

  4. #34

    Join Date
    Sep 2010
    Posts
    548
    Thank Post
    26
    Thanked 62 Times in 58 Posts
    Rep Power
    19
    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)

  5. #35

    Join Date
    May 2010
    Posts
    1,017
    Thank Post
    105
    Thanked 76 Times in 62 Posts
    Rep Power
    47
    It's fine

    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
    Must be something dumb I'm doing, is there anything on the server I'm supposed to do ?

  6. #36


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,581
    Thank Post
    228
    Thanked 854 Times in 733 Posts
    Rep Power
    295
    port whatever kms uses open on the servers firewall? can you ping/ talk to that server?

  7. #37

    Join Date
    Dec 2009
    Posts
    265
    Thank Post
    6
    Thanked 31 Times in 29 Posts
    Rep Power
    15
    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).

  8. #38

    Join Date
    May 2010
    Posts
    1,017
    Thank Post
    105
    Thanked 76 Times in 62 Posts
    Rep Power
    47
    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 ?

  9. #39

    Join Date
    Dec 2009
    Posts
    265
    Thank Post
    6
    Thanked 31 Times in 29 Posts
    Rep Power
    15
    Quote Originally Posted by caffrey View Post
    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 ?
    Extract taken from the following technet article

    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.

  10. #40

    Join Date
    May 2010
    Posts
    1,017
    Thank Post
    105
    Thanked 76 Times in 62 Posts
    Rep Power
    47
    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 ?

  11. #41

    Join Date
    Sep 2010
    Posts
    548
    Thank Post
    26
    Thanked 62 Times in 58 Posts
    Rep Power
    19
    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

  12. #42
    newpersn's Avatar
    Join Date
    Nov 2010
    Location
    Gloucestershire
    Posts
    1,188
    Thank Post
    273
    Thanked 110 Times in 83 Posts
    Rep Power
    76
    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...."

  13. #43

    Join Date
    Dec 2009
    Posts
    265
    Thank Post
    6
    Thanked 31 Times in 29 Posts
    Rep Power
    15
    Quote Originally Posted by newpersn View Post
    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...."
    Generally the WMI failure is for 1 of 2 reasons

    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)

    Inbound -
    Key Management Service (TCP-in)
    Windows Management Instrumentation (ASync -In)
    Windows Management Instrumentation (DCOM-In)
    Windows Management Instrumentation (WMI-In)

    Outbound -

    Windows Management Instrumentation (WMI-Out)

  14. Thanks to Firefox from:

    newpersn (8th November 2013)

  15. #44
    newpersn's Avatar
    Join Date
    Nov 2010
    Location
    Gloucestershire
    Posts
    1,188
    Thank Post
    273
    Thanked 110 Times in 83 Posts
    Rep Power
    76
    Quote Originally Posted by Firefox View Post
    Generally the WMI failure is for 1 of 2 reasons

    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)

    Inbound -
    Key Management Service (TCP-in)
    Windows Management Instrumentation (ASync -In)
    Windows Management Instrumentation (DCOM-In)
    Windows Management Instrumentation (WMI-In)

    Outbound -

    Windows Management Instrumentation (WMI-Out)
    Ah I was missing the Key management service (inbound) and WMI out....

    Restart some computers now to see whats happens...

  16. #45

    Join Date
    Sep 2005
    Posts
    143
    Thank Post
    0
    Thanked 3 Times in 3 Posts
    Rep Power
    19
    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 11:12 AM.

SHARE:
+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast

Similar Threads

  1. KMS Client Setup Keys
    By ZeroHour in forum Licensing Questions
    Replies: 7
    Last Post: 17th September 2013, 09:30 PM
  2. [MS Office - 2010] KMS Setup
    By Stuart_C in forum Office Software
    Replies: 9
    Last Post: 15th February 2012, 10:14 AM
  3. KMS Setup help needed
    By timbo343 in forum Licensing Questions
    Replies: 5
    Last Post: 19th August 2011, 05:11 PM
  4. KMS Client Setup Keys
    By ZeroHour in forum Windows Server 2008
    Replies: 0
    Last Post: 18th February 2010, 11:30 AM
  5. KMS Client Setup Keys
    By ZeroHour in forum Windows Server 2008 R2
    Replies: 0
    Last Post: 18th February 2010, 11:30 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •