Hi..

We're deploying a new WIM that has Office 2013 ProPlus installed, and the product key has been verified as the generic one listed at:  http://technet.microsoft.com/en-us/library/dn385360.aspx

The problem we're seeing is that it, while Windows is activating via KMS without issue, Office is not activating unless is triggered manually from the KMS server console. 

Keeps saying that it's out of tolerance.

Question is..how long should it take for Office to contact the KMS server?  Maybe we're just not waiting long enough????

Activation works as expected on the source machine prior to sysprep, so did I sysprep it wrong?

Thanks

-A

• Edited by Adam at CB 16 hours 14 minutes ago

Office 2010/2013 "attaches" itself to the existing Windows sppsvc (slsvc on older platforms like WinVista/WS2008), so it should discover & activate without any intervention.

I have sometimes seen it take a few more minutes than usual, but launching an Office application is sometimes needed to "trigger" the conversation with KMS, e.g. first-launch of an Office application might show as grace period, in the background activation occurs, at second launch of an Office application it's activated ok.

I would expect that if you did have an issue with your sysprep/imaging routine (e.g. you hadn't used ospprearm) then it would not activate at all due to duplicate CMID at the client machine.