Need help with KMS on Windows Server 2008 R2

I downloaded and installed Office Professional Plus 2010 Key Management Service Host and when it prompted for my product key I entered the KMS volume license key that I got when purchased Office 2010 Pro.  It seemed to install and activate, but I installed Office on a Win 7 client and waited a little while for it to activate.  I then tried running it manually with the following command, and got the resulting error.

cscript ospp.vbs /act

Error Code: 0xC004F038
Error Description: The software licensing service reported that the computer could not be activated.  The count reported by your Key Management Service (KMS) is insufficient.

I also noticed where it lists the last 5 characters of the product key don't match the product key I put in the KMS host, but it was my understanding the KMS key was pre-installed with Office 2010.

I also know we hit the minimum number for the license is for 37 copies, which I verified on Microsoft's site.  Did I put the wrong key in the KMS host?
Go-GBSAsked:
Who is Participating?
 
Go-GBSAuthor Commented:
I think I found the issue.  Must have to do with the cmid.  I found a utility that can generate activation requests, and now it's working.  I'll have to look into fixing the cmid issue though.
0
 
Go-GBSAuthor Commented:
Ok, not I'm starting to see some info that you have to have at least 25 machines try to activate before it will work.

I still don't understand when I run on the KMS host, "cscript slmgr.vbs /dli" why it won't show me the count?
0
 
Cliff GaliherCommented:
The /dli flag queries for the number of hosts that have been activated, NOT the number of hosts that have requested activation. Since you have not yet met the threshold, the number of activated hosts is still zero, hence you won't get what you are looking for.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
ChrisCommented:
i think it should only be 5 for office and then it should start activating

this will show the specific KMS stuff for Office

cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864
0
 
Go-GBSAuthor Commented:
I see, so once I have 5 different machines try to connect it should work?
0
 
ChrisCommented:
yes then it should start working.

If you try and setup OS KMS the activation count is 25.
0
 
Go-GBSAuthor Commented:
Got it.  Well I'm hoping to get an image of this laptop today and push it out, so we should see shortly.
0
 
ChrisCommented:
on a client you should be able to get the error saying KMS count insufficient
0
 
Go-GBSAuthor Commented:
Yep, the error I noted in my original post says that.
0
 
ChrisCommented:
sorry completely blanked there, read it and then plain forgot it
0
 
Go-GBSAuthor Commented:
Well, we've had at least 5 machines try, and we still get the same message.
0
 
Cliff GaliherCommented:
View the number of requests with the /dlv flag.
0
 
Go-GBSAuthor Commented:
When I run "cscript slmgr.vbs /dlv" it isn't giving me the number of requests.
0
 
Go-GBSAuthor Commented:
At the bottom it says "Remaining Windows rearm count: 3"
0
 
Go-GBSAuthor Commented:
Okay, I ran it with "/dli all" and got some more info.  Total requests received is 54, it says it's enabled, and the current count is 4.  What am I missing, it seems like it should be working?
0
 
Go-GBSAuthor Commented:
This has it resolved for now, plus there hasn't been any suggestions made.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.