Cannot activate Microsoft Office 2013 KMS clients back to KMS host

I have just set up my Windows Server 2008 R2 domain controller as a KMS host.  I got my Windows 7 clients to activate back to the host, but I am having a problem getting Office 2013 to activate on the same clients.  I have gone through the steps to get the Office 2013 license set up on the KMS host and if I run cscript slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD on the host I see that it is licensed and accepting requests.  But, I only see my current count as 1.  I have verified that the request count increases by one each time I force an activation attempt from a client, using cscript ospp.vbs /act  I have also verified that the license I installed on the KMS host is correct.  I should note that the clients were activated using MAK first and have been converted to KMS clients using the key KBKQT-2NMXY-JJWGP-M62JB-92CD4 (Office 2013 Standard).  What might I be missing here?
Dustin23IT DirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brad HeldCommented:
http://technet.microsoft.com/en-us/library/dn385357.aspx

The client activates at the first launch of Office 2013, provided that there have been at least four previous activation requests to the KMS host. This is because the KMS host requires at least five requests before it begins activating clients.
Dustin23IT DirectorAuthor Commented:
brad-

I am aware of how the KMS activation works, but the current count never increases even though the request count does.  So the clients are contacting the host as they should, but they are not completing activation.  Somewhere there is an issue...
Dustin23IT DirectorAuthor Commented:
Can anyone give me further assistance on this?
Dustin23IT DirectorAuthor Commented:
Ok, I figured out the issue.  All the desktops had been created from a parent image and I hadn't run a rearm on the PI.  Therefore, all the desktops had the same Client Machine ID (CMID).  So, on the parent, I had to run ospprearm.exe from the Office directory (%Program Files%\Microsoft Office\Office15).  This removed the CMID from the parent and forced each child desktop to take a different one.  Once this was done, Office activated successfully.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dustin23IT DirectorAuthor Commented:
I discovered the answer for myself and wanted to post the details for the knowledge base.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.