Hi, KMS server stopped activating because of reached to the activation limit (500) but we did not install not even 60 clients!!!Why is that and how can I solve that issue?

Please paste the output of slmgr /dlv from your not activating client, here. Thanks!- thestriver

Hi, How many KMS hosts installed in your environment? Do you happen to use KMS host key to activate KMS client machine if there are already six KMS hosts installed in your environment? Generally, a KMS host key can be used to setup 6 KMS hosts. If you happen to run KMS host key on the seventh machine, you’ll get the activation limit error. To resolve this, you should call Microsoft Activation Center. However, if KMS host key doesn’t reach its limit, the issue occurred during activating KMS client machine. I would like to recommend you to run the command: slmgr.vbs /dli on KMS client machine to show the activation information. From the above output of KMS host activation information, I noticed that the current count of KMS host is 24. By default, only if the count number meets the activation threshold, the KMS client machines can be activated. The Windows Vista/7 KMS client threshold is 25, and the Windows Server 2008 KMS client threshold is 5. If there are only Windows Vista/7 KMS client installed in your environment, then you need to setup more than 25 machines to meet the threshold so that KMS client can contact KMS host to be activated. To solid troubleshoot the cause, please check the following event log: On KMS client, please look in the Application event log for event 12289. On KMS host, please look in the KMS event log for event 12290. Best Regards Dale Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Hi, I have only 1 KMS host and I using it to activate Windows 7 clients and Office 2010. I do not have any other KMS host. KMS system activated more than 40 clients until today with no problem. I do not have any 12289 logs but full of many 12290 events logged. We do have license agreement for 200 machines and MS Volume sites says 500 available! and so far we never reached (not even close) that number of machines at all. Note:All clients installed with Sysprep and generalized. As you can see I already put the screen shots whihc belong to /dli and /dlv. So what should I do now?

Hi, I have only 1 KMS host and I using it to activate Windows 7 clients and Office 2010. I do not have any other KMS host. KMS system activated more than 40 clients until today with no problem. I do not have any 12289 logs but full of many 12290 events logged. We do have license agreement for 200 machines and MS Volume sites says 500 available! and so far we never reached (not even close) that number of machines at all. As you can see I already put the screen shots whihc belong to /dli and /dlv. So what should I do now?

Is there any 12288 event log on KMS client machine? Since there is no 12289 event log on KMS client, it means that the KMS client doesn’t receive the response back from the KMS server. 12290 is generated and created for each activation and renewal request from each client. Please check if the client is running a third party firewall, try temporarily turn off firewall to test. Meanwhile, as I mentioned in my first reply, you have activated more than 40 machines but the current count is 24, it seems that the KMS current count doesn’t increase. This occurs if the client computers that you add to the network have identical KMS client machine IDs (CMIDs). To resolve this, please refer to the following KB: The KMS current count does not increase when you add new Windows Vista-based client computers to the network Best Regards DalePlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Yes 12288 and 12289 logged as seen below but still no activation. I turned off AV and firewall.All machines installed by using sysprep /oobe /generalize /unattend:unattend.xml command successfully and joined to the domain. Note: SkipRearm command not included in sysprep unattend.xml slmgr -dli command result on client machine after running slmgr -rearm Log Name: Application Source: Microsoft-Windows-Security-SPP Date: 16/11/2010 9:43:22 AM Event ID: 12289 Task Category: None Level: Information Keywords: Classic User: N/A Computer: com-a01.itc.local Description: The client has processed an activation response from the key management service machine. Info: 0x00000000, 0x04000000, 0, 0, 24, 120, 10080, 2010/11/15 23:43 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-SPP" Guid="{E23B33B0-C8C9-472C-A5F9-F2BDFEA0F156}" EventSourceName="Software Protection Platform Service" /> <EventID Qualifiers="16384">12289</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-11-15T23:43:22.000000000Z" /> <EventRecordID>2095</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>com-a01.itc.local</Computer> <Security /> </System> <EventData> <Data>0x00000000, 0x04000000, 0, 0, 24, 120, 10080, 2010/11/15 23:43</Data> <Binary>000004006t;/Binary> </EventData> </Event> ############################################################# Log Name: Application Source: Microsoft-Windows-Security-SPP Date: 16/11/2010 9:43:22 AM Event ID: 12288 Task Category: None Level: Information Keywords: Classic User: N/A Computer: com-a01.itc.local Description: The client has sent an activation request to the key management service machine. Info: 0x00000000, 0x00000000, vegemite.itc.local:1688, 2ec3feba-1adc-447d-b50f-fe951dfb9813, 2010/11/15 23:43, 0, 2, 43080, b92e9980-b9d5-4821-9c94-140f632f6312, 25 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-SPP" Guid="{E23B33B0-C8C9-472C-A5F9-F2BDFEA0F156}" EventSourceName="Software Protection Platform Service" /> <EventID Qualifiers="16384">12288</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-11-15T23:43:22.000000000Z" /> <EventRecordID>2094</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>com-a01.itc.local</Computer> <Security /> </System> <EventData> <Data>0x00000000, 0x00000000, vegemite.itc.local:1688, 2ec3feba-1adc-447d-b50f-fe951dfb9813, 2010/11/15 23:43, 0, 2, 43080, b92e9980-b9d5-4821-9c94-140f632f6312, 25</Data> <Binary>00000400000000000200000048A8000034200000009BA58D61F28B98185EDC06822BCAE95F</Binary> </EventData> </Event>

Please try to run the following command to force a rearm on client machines, then re-connect to KMS server for activation and see how it works. Rundll32 slc.dll, SLReArmWindows Best Regards DalePlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Unfortunately did not work.

Hello ICBL, the count of 24 means that 24 machines, identified as unique ( Different CMIDs) contacted the KMS host during the past 30 days. You may want to look at the KMS host KMS event log and see which machines have contacted the KMS host in the past 30 days. The following link explains the details in the event log http://technet.microsoft.com/en-us/library/ee939272.aspx Here is where you can verify that all your machines are communicating with the KMS host and verify that all the CMIDs are uniqueThanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Hi Darrell, I think we are about the solve that issue. I classified all logs according to your suggestion above and noticed following logs. I just added here a couple of them because most of them looks same. (LAB2 computers all same but they preinstalled by Dell and activated already! ) (I have used generalize command while using sysprep as I was creating custom profile and change SIDs) SID successfully changed!!! I also found the following article http://blogs.technet.com/b/askcore/archive/2009/10/16/kms-host-client-count-not-increasing-due-to-duplicate-cmid-s.aspx "While it is possible to run slmgr.vbs /rearm to reset the machines CMID that does not leave the machine in a supported state. Images deployed without using Sysprep to prepare the image are not supported by Microsoft. Sysprep executes ~30 sysprep providers. These providers are written to correct issues with various components when you duplicate the installation. By not running sysprep it is unknown what types of issues you could encounter and many components will be in a broken state. The supported solution is to rebuild the image using the Sysprep /generalize switch and redeploy the systems." Now what should I, redeploy the computers or use slmgr /rearm command? An activation request has been processed. Info: 0x0,5,ITC-LAB2-B3.itc.local,9f17870f-512a-4798-9824-9e7b2d12bc9b ,2010/10/18 23:46,0,1,249121,6f327760-8c5c-417c-9b61-836a98287e0c An activation request has been processed. Info: 0x0,5,ITC-LAB2-C8.itc.local,9f17870f-512a-4798-9824-9e7b2d12bc9b ,2010/10/19 03:39,0,1,243223,6f327760-8c5c-417c-9b61-836a98287e0c An activation request has been processed. Info: 0x0,5,ITC-LAB2-B2.itc.local,9f17870f-512a-4798-9824-9e7b2d12bc9b ,2010/10/20 23:38,0,1,249065,6f327760-8c5c-417c-9b61-836a98287e0c An activation request has been processed. Info: 0x0,5,ITC-UE1-A3T7.itc.local,ae1aa770-ce5b-4d93-9e49-dedd833df71e ,2010/10/18 01:33,0,1,249120,6f327760-8c5c-417c-9b61-836a98287e0c

ah yeah, we had this issue with *cough random vendor cough * supplied workstations. they all presented the same CMID. We had to get the vendor image fixed and redeploy.

But I used Volume License disc for the other workstations and deployed them with sysprep. SIDs changed but CMID remains same. Isn't weird or where Im mistaken?

I believe this process still applies to win7 (or may not :-) ) http://support.microsoft.com/kb/929829/en-us you have CMID clashes, until you correct that you're in a not great state.

Please open a case with MS. In the meanwhile you can refer http://blogs.technet.com/b/askcore/archive/2009/10/16/kms-host-client-count-not-increasing-due-to-duplicate-cmid-s.aspx- thestriver

yes, it should apply to Win7 situations as well - thestriver

How we gonna find out whats the machine CMID? slmgr /dli does not return with CMID on Windows 7 (On Vista its ok). For Windows 7 which command or method will be used on the client machine ? slmgr /dlv or /dli does not give CMID

hmm for me (on windows 7 64 bit) slmgr.vbs /dlv does display CMID But I just noticed the service version on my machine is 6.1.7601.17105, possibly because I have SP1 RC installed at the moment. Other thing is line 3 says OEM_SLP Channel. Shouldn't that be VOLUME_MKSCLIENT channel? or does it not matter? I'd be tempted to try slmgr /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 on the client and see what happens. (that key is from http://technet.microsoft.com/en-us/library/ff793421.aspx )

CAN YOU PASTE THE CONTENTS OF YOUR ANSWER FILE THAT YOU USE TO SYSPREP WITH THE GENERALIZE SWITCH, HERE... FOR VOLUME LICENSING CLIENTS ONLY, WHERE YOU HAD USED SYSPREP AND ANSWER FILE NOTE: THIS EXCERCISE IS NOT APPLICABLE for OEM PREACTIVATED CLIENTS PARDON THE CAPS. SOME ISSUE WITH MOBILE KEYBOARD - thestriver

CAN YOU PASTE THE CONTENTS OF YOUR ANSWER FILE THAT YOU USE TO SYSPREP WITH THE GENERALIZE SWITCH, HERE...- thestriver

CAN YOU PASTE THE CONTENTS OF YOUR ANSWER FILE THAT YOU USE TO SYSPREP WITH THE GENERALIZE SWITCH, HERE... PARDON THE CAPS. SOME ISSUE WITH MOBILE KEYBOARD - thestriver

OEM_SLP CHANNEL SHOWS IN ALL OEM PREINSTALLED OS. SO THIS MEANS THAT THIS INSTANCE IS ALREADY PREACTIVATED AND YOU DONT NEED TO REACTIVATE IT AS OEM PREACTIVATED OS DOES NOT NEED REACTIVATION. AND THEREFORE IT WILL NOT SHOW THE CMID AS WELL. VOLUME_KMSCLIENT CHANNEL SHOWS ON.Y IN SYSTEMS THAT FALL UNDER VOLUME LICENSING AND SHOULD SHOW THE CMID AS WAS IN YOUR CASE- thestriver

Hi, As I mentioned previously only LAB2 computers preinstalled and activated by Dell. But same problem with my Volume_kmsclients as well. My VL installations also does not give CMID aswell (Sysprep generalize command also not changing CMID but changing SIDs). I just copied my sysprep below. (To run sysprep I ve used the follwoing command sysprep.exe /oobe /generalize /unattend:unattend.xml ) and succesfully finished. This sysprep for Volume License Disc! <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DisableFirstRunWizard>true</DisableFirstRunWizard> <Home_Page>http://www.google.com.au</Home_Page> <LockToolbars>true</LockToolbars> <CompanyName>ITC</CompanyName> <SuggestedSitesEnabled>false</SuggestedSitesEnabled> <DisableAccelerators>true</DisableAccelerators> <PrivacyAdvisorMode>2</PrivacyAdvisorMode> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <CopyProfile>true</CopyProfile> <RegisteredOrganization>ITC</RegisteredOrganization> <TimeZone>(UTC+10:00) Brisbane</TimeZone> <ComputerName>ITC-XX-7SX</ComputerName> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OEMInformation> <Model>Dell Optiplex SX280</Model> <Manufacturer>Dell</Manufacturer> <SupportPhone>105</SupportPhone> <SupportURL>www</SupportURL> </OEMInformation> <OOBE> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>2</ProtectYourPC> <HideEULAPage>true</HideEULAPage> </OOBE> <RegisteredOrganization>ITC</RegisteredOrganization> <TimeZone>(UTC+10:00) Brisbane</TimeZone> </component> </settings> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-au</UILanguage> </SetupUILanguage> <InputLocale>en-au</InputLocale> <SystemLocale>en-au</SystemLocale> <UserLocale>en-au</UserLocale> <UILanguage>en-au</UILanguage> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserData> <AcceptEula>true</AcceptEula> <Organization>ITC</Organization> </UserData> </component> </settings> <cpi:offlineImage cpi:source="catalog:c:/waik ITC/32/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>

Your answer file looks ok. Are you talking about the kms client system with partial pk GPDD4? If it is not, then can you paste the slmgr -dli output of the system here... - thestriver

Hi the dlv screenshot below belong to VL KMS client not to the third party manufacturer and getting same result.

Hi From the slmgr.vbs /dli screenshot of Windows 7 Professional client, the computer is pre-installed with the OEM_SLP key. OEM_SLP keys are preinstalled by the OEM on the machine. SLP keys will work with OEM SLP system, they are the only keys that are able to perform offline activation instantly and locally without going online or connecting to Microsoft server. OEM SLP keys are only issued to big manufacturers such as Dell, Asus, Sony, etc. Each product key for all editions of Windows in a distribution channel from Microsoft is associated with a Same Group ID or Cryto ID. Generally, the product usage rights for OEM-licensed products prohibit conversion of an OEM installation of an operating system to a Volume License installation. However, there are exceptions. If one of the exceptions applies, an OEM version of Window 7 or Windows Server 2008 R2 can be changed to a Volume License version. One exception that allows changing an OEM installation to a Volume License installation is if Software Assurance is purchased within 90 days of purchasing the OEM product. This exception applies only to Windows 7 or Windows Server 2008 R2. Another exception is if the OEM product is the same product for which a Volume License agreement already exists. Volume License customers have reimaging rights and may be eligible to upgrade an OEM installation using Volume License media. For more information about imaging rights, see the Microsoft Volume Licensing brief “Reimaging Licensed Microsoft Software by Using Volume Licensing Media,” at and “Customizing Windows Vista Business Edition”. Computers obtained through OEM channels that have an ACPI_SLIC table in the system basic input/output system (BIOS) are required to have a valid Windows marker in the same ACPI_SLIC table. The appearance of the Windows marker is important for Volume Licensing customers who are planning to use Windows 7 Volume License media to re-image or upgrade an OEM system through the re-imaging rights they have in their Volume Licensing agreement. Computers that have an ACPI_SLIC table without a valid Windows marker generate an error when a volume edition of Windows 7 is installed. For more information, see “You receive an error message when you try to activate Windows Vista on a computer that was obtained from an OEM”. These systems cannot be activated with KMS, but they can be activated using a MAK or a retail key. Thus please contact the OEM manufacturer to confirm if either of the above exception meets. Best Regards DalePlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Dale, Thanks for the details for OEM. How about my VL installations which 1 message before than yours and shown dlv screenshot. Update: A couple of minutes ago I installed brand new machine with the VL Disc (not imaging) and I see the same screen with the below one.

My thought is since cmid is a subset of KMS, you should try and activate this client with your kms server and see if after activating does the cmid get created. Right now this client is in Inital Grace period beacause it is normal for all clients to show the same output just after install from a sysprep'd image. It is also true for installs with the VL disk Try running below commands on the client after installing with a freshly sysperep'd image:(not the vl disc). Note: syspreping system should not be a oem one slmgr -upk slmgr -ipk and the correct generic key for the version of OS slmgr -skms kmsserverfqdn:1688 slmgr -ato Paste here the errors if any- thestriver

Hi, slmgr -ipk and the correct generic key for the version of OS for this whihc key I am gonna use? Is it the one that Ive put in KMS server or from the MSDN for Windows 7?

Please refer post of SJB99 ABOVE. GOTO THAT WEBSITE AND GET THE GENERIC PRODUCT KEY FOR YOUR VERSION OF OS NOTE: DON.T USE THE KMS HOST KEY ON ANY OS THAT YOU FEEL SHOULD BE A KMS CLIENT - thestriver

Hi, slmgr -upk (Successful) slmgr -ipk and the correct generic key for the version of OS (Successful) slmgr -skms kmsserverfqdn:1688 (Successful) slmgr -ato (Activating Windows(R)7, Professional edition (b92e9980-b9d5-4821-9c94....... Error:0xC004F074 The software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable.) Note: I just installed Windows 7 Enterprise edition and KMS activated it with no problem.

Check the Windows Firewall on the KMS Host and make sure Port 1688 (or if they changed the port is allowed traffic). Check the Windows Firewall on the KMS Clients to make sure Port 1688 is allowed outbound traffic. You will need to enable these ports on the Firewall in order to successfully be able to activate Windows to the KMS Host Open Network and Sharing Center Click Windows Firewall Click "Allow a program or feature through Windows Firewall" Look for the following entry: Key Management Service. Port 1688. Enable the exception You can verify connectivity by using Telnet from the Client machine and running "telnet <fqdn or ip address> 1688" and if it comes up with a blank screen then you are successfully connected to the system. And, then retry slmgr -ato command Only on the client and let me know what happens - thestriver

Check the Windows Firewall on the KMS Host and make sure Port 1688 (or if they changed the port is allowed traffic). Check the Windows Firewall on the KMS Clients to make sure Port 1688 is allowed outbound traffic. You will need to enable these ports on the Firewall in order to successfully be able to activate Windows to the KMS Host Open Network and Sharing Center Click Windows Firewall Click "Allow a program or feature through Windows Firewall" Look for the following entry: Key Management Service. Port 1688. Enable the exception You can verify connectivity by using Telnet from the Client machine and running "telnet <fqdn or ip address> 1688" and if it comes up with a blank screen then you are successfully connected to the system. And, then retry slmgr -ato command Only on the client and let me know what happens P.S.: I hope you had used your kms host fqdn in place of "kmsserverfqdn" in the command "slmgr -skms kmsserverfqdn:1688" - thestriver

Hi thestriver, On the client machine firewall exceptions inbound and outbound is open for 1688. But still having same error. Just make sure I used kmsserverfqdn as servername.itc.local:1688

Error 0xC004F074 Only comes when kms client is not able to reach kms host vice-versa. As another Win7 Enterprise client had activated with the kms host, I think you have issues with this client and not the host Is this kms client on same subnet as kms host? How many kms hosts are there in your environment? Can you ping kms host from this kms client? Is windows firewall enabled and running on kms host? If yes, is inbound and outbound traffic open on port 1688 on kms host? (Verify) How did you verify port 1688 is open on client? Do you see the cmid on the other Win7 Enterprise client?- thestriver

Hi, Client and server on same subnet. I have only 1 KMS server. I can ping the server with no problem. Inbound outbound traffic is open for port 1688. Disabled firewall and tested no change. Note: A couple hours ago I installed same machine with "Windows 7 Enterprise" and its activated itself within a couple of minutes. I did not do anything! Now I formatted same machine adn installed Windows 7 Professional and it cannot activate itself. I checked thousands time and I am sure that I am using VL Windows 7 Pro. I will donwload it again and give it try. If problem still persist what I am gonna do?

Downloaded 32 bit Windows 7 Pro VL this time and installed same machine. Again no activation. Now its very clear VL Windows 7 Pro editions not activating. What would be reason?

Thanks for the information After activation of the latest Win7 Ent OS, do you see the CMID?- thestriver

Try activiting the same win7 pro machine with a MAK key and please report what happens- thestriver

Hello ICBL, First check to make sure you are using VL media, run slmgr /dlv. The Description line would need to contain kms client. If not what is on that line? The professional installation listed above (11-19)where we show that ( dlv output) and you indicate this was a clean install of media, shows a rearm count of 0 which should not be the case on new installation so I am somewhat confused by that post. If the Windows 7 Profesional shows as a KMS client, check the event log on the client and make sure it is pointed to the correct KMS host, The KMS host would be in the details of the event 12288. http://technet.microsoft.com/en-us/library/ff793440.aspx If the KMS host is listed there correctly, then look at the KMS host machine KMS event log and make sure the client name is showing up in the details of the event on the KMS host http://technet.microsoft.com/en-us/library/ee939272.aspx Are there any error codes on the events of the KMS client events of KMS hsot events for this installation? Does the KMS host also have a count of at least 25 machines? Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Hello ICBL, First check to make sure you are using VL media, run slmgr /dlv. The Description line would need to contain kms client. If not what is on that line? T he professional installation listed above (11-19)where we show that ( dlv output) and you indicate this was a clean install of media, shows a rearm count of 0 which should not be the case on new installation so I am somewhat confused by that post. If the Windows 7 Profesional shows as a KMS client, check the event log on the client and make sure it is pointed to the correct KMS host, The KMS host would be in the details of the event 12288. Hi, Your right Ive copied that screen shot from previous post. Beside of rearm count it was identical. After clean install that rearm count was 3, I just didnt want to upload again thats all. I just prepared summary for event logs from both, server and client side according to timing as below. Client machine has sent activation request at 08:55:30am (Event ID 12288) Client machine License Activation Scheduler (sppuinotify.dll)was not able to autmatically activate. Error code: 0xC004F074 at 08:55:30am (Event ID 8196) Server processed that request 08:56:16am (Event ID 12290) No further logs on both side (server and client)

Therefore, the client is able to contact the host per event 12288 On this client, could you run the command "slmgr /skhc" from an elevated prompt and then run "slmgr /ato" immediately after that, and update us please - thestriver

Unfortunately did not work. slmgr /skhc (Cashing enabled) slmgr /ato (Activating Windows(R)7, Professional edition (b92e9980-b9d5-4821-9c94....... Error:0xC004F074 The software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable. ) Client machine has sent activation request at 03:51:42pm (Event ID 12288) No event 8196 logged this time!!! Server processed that request 03:52:27pm (Event ID 12290)

What is the time on the KMS host and on this client. If there is any time difference, please get the times synched. Please also run the following command on this client and revert with output: "nslookup -type=all _vlmcs._tcp" - thestriver

Time is correct. Nslookup result as below. C:\>nslookup -type=all _vlmcs._tcp Server: vegemite.itc.local Address: 192.168.0.20 _vlmcs._tcp.itc.local SRV service location: priority = 0 weight = 0 port = 1688 svr hostname = vegemite.itc.local vegemite.itc.local internet address = 192.168.0.20

Hello ICBL. The error message is 0xC004F074 can indicate different things however we seem to have covered most of them. So far everything appears correct, which is confusing But let's verify them all at least one more time. 1) Mismatch between client OS and KMS host( the KMS host cannot activate the client being used. this appears fine, however check the version as well, just to be safe of the KMS client. 2) Time difference, this is based on UTC time but check the timezones of each machine to make sure they are set correctly; the event log entries makes the time appear correctly but the timezone may not be accurate. 3) Firewall\proxy issues where the client cannot communicate to the KMS host. Since we are seeing the traffic in the KMS host event logs, this seems unlikely. Note the output from slmgr /dlv can be captured as text using a control+C on the dialog box so you do not have to post images of the output Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Hi, I will do 2 different installations more to test scenarios and will get back to here.I checked time and other possiblilties that you have mentioned they all ok. By using same installation disc; 1-Installation of same machine with formatting 2-Installation of different machine with formatting