If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
KMS Server issue
Got a potential problem that I can't figure out. I have a KMS server in my environment that serves out licenses for Office and for Windows 7. We have a VMWare View environment for virtual desktops. I have one pool that has suddenly started asking for a reactivation of the license - which it should not - because of some driver change. It's not happening on my other desktop pools, so perhaps I just need to reactivate the master and that may solve that.
But when this started to happen, I initially thought something was wrong with the KMS server. I looked in DNS to make sure the DNS pointer to the KMS was there, that there was only one and that it pointed to the right place. That tuned out to be OK.
Then I went to the KMS server itself and ran the slmgr.vbs script with the /dli switch. It is reporting all is OK for Windows, but I see no evidence that the Office license is even installed on the KMS server. I know that it is/was as I did it myself some months ago and would have double-checked to make sure that I could see it and the counts go up as I added Office to my computers. What would cause Office number not to appear on the server?
But when this started to happen, I initially thought something was wrong with the KMS server. I looked in DNS to make sure the DNS pointer to the KMS was there, that there was only one and that it pointed to the right place. That tuned out to be OK.
Then I went to the KMS server itself and ran the slmgr.vbs script with the /dli switch. It is reporting all is OK for Windows, but I see no evidence that the Office license is even installed on the KMS server. I know that it is/was as I did it myself some months ago and would have double-checked to make sure that I could see it and the counts go up as I added Office to my computers. What would cause Office number not to appear on the server?
Asked:
Who is Participating?
Then it is configured for Office 2013 activation.
Do you see something like this?
Key Management Service cumulative requests received from clients
Total requests received: 14276
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 13840
Requests with License Status Initial grace period: 352
Requests with License Status License expired or Hardware out of tolerance: 76
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 8
Do you see something like this?
Key Management Service cumulative requests received from clients
Total requests received: 14276
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 13840
Requests with License Status Initial grace period: 352
Requests with License Status License expired or Hardware out of tolerance: 76
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 8
Yeah... any idea why I'm not seeing it when I just do the /dlv or /dli? I'm pretty sure that's what I've done in the past... I've never executed the command you did with that number.
No, DLV doesn't show you that.
Look at this reference guide from MS.
To see all you must type the command like this:
cscript slmgr.vbs /dlv all
Look at this reference guide from MS.
To see all you must type the command like this:
cscript slmgr.vbs /dlv all
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.
cscript slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61
This is for Office 2013.