Jump to content

Recommended Posts

Posted
firewall at a guess try poking holes for wmi or just turn it off

 

My computer dosnt like its name... Entered my ip address and it worked fine. Windows has activated, Just gotta get the office count up.

Posted

I'm having issues with VAMT as well, just set it all up and I'm getting :-

 

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 ?

Posted

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.

Posted
I'm having issues with VAMT as well, just set it all up and I'm getting :-

 

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?

Posted
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)
Posted

It's fine

 

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 ?

Posted
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).
Posted
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 ?
Posted
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 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.

Posted
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 ?
Posted

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...."

Posted
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)

  • Thanks 1
Posted
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...

Posted (edited)

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/servicecenter/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).

Edited by Frazer
Posted

Counts for office 2010 is 5

Counts for Windows 7 is 25.

 

Just got to get my head around why I cant connect to computers (WMI) Firewall is disabled and computers are turned on.

Posted
Counts for office 2010 is 5

Counts for Windows 7 is 25.

 

Just got to get my head around why I cant connect to computers (WMI) Firewall is disabled and computers are turned on.

 

From the KMS server open a command prompt and run wbemtest

 

on the connect option where it lists root\cimv2 add the server name that's failing in front e.g \\server\root\cimv2 and provide credentials - does this connect?

Posted
Connected fine...

 

Wouldn't let me add my credentials tho. Said about being local server.

 

Very odd, is your server domain joined? is there any difference in the devices that it can license and those it can't?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...