I can use OSPP to activate Office against KMS and dstatus shows the KMS license information we all expect. Prior to sysprepping the image, when I run OSPP /dstatusall, I see that Office 2016 has two licenses, MAK or KMS, and that's what we all expect. The symptoms are similar to what is described in this post: We think we understand and have resolved this. Ospp.vbs /rearm does, or ospprearm.exe rearms Office prior to actually invoking Sysyprep on the reference image. Sysprep doesn't re-arm Office, only the OS. The bizarre this is that if I image the very same image to a brand new VMWare VM, office works perfectly.ĭonPick: You are correct. If I un/re-install Office 2016 Pro Plus KMS on the broken machines, it works perfectly. On the broken physical machines, if I try to enter the Office 2016 Pro Plus KMS GVLK key using opss, I'm told the product key is invalid. Windows 10 also does not come up activated, although it will if I manually activate it. After I deploy the same image to a physical workstation, OSPP tells me that there is "no installed product key detected" for OfficeĢ016. Prior to sysprep OSPP tells me that Office is activated, after I rearm it, I see that it's in the grave period.
We're building a Windows 10 Pro KMS deployment using VMWare Workstation, installing all our software (Autodesk 2017, Office 2016, etc.), rearming office, sysprepping, capturing the WIM an deploying with a WDS server.
0 kommentar(er)
