The Windows log on the client machines is also now showing the following event. Jason - slmgr on the KMS host shows details about Windows 7 but nothing about Office 2010. I thought a client machien ID (CMID) was unique to the client machine, not to the applications.Īndrew - Yes (at least that's what my network guys said). For KMS volume activation, there are two different CMIDs - one for Windows and one for Office 2010. This process also served to correct a misconception on my part. The moral to the story - when building the customized installation for deployment make sure no Office 2010 apps are launched before the image is captured. Thus, the KMS host did not increment the counter.
Same client every time any of those machines hit the KMS host to attempt to activate Office 2010. The CMID then was the same for every machine to which the image was deployed. That action created the Office CMID on the reference computer and I went on my merry way and created my deployment image from that computer. Office 2010 installation by launching a couple of the Office apps. When I built the customized installation for the Windows 7 LTI deployment (on the reference computer) I tested the
Unlike Windows 7, the CMID for Office 2010 is created on the client machine when any Office application is launched the first time.