B
BrianChernish1
We have been mass deploying new Lenovo Windows 10 PCS, using the Sysprep utility to prepare the image for mass deployment. The biggest concern we had going in was that we preserve the OEM license key.
This seemed to be working fine, we created our base image, sysprep'd the machine and captured the image. After deploying the image to a new PC, we went through the setup wizard, licensing, personalization, etc. and checked to make sure the OEM key was still in place (it was). After initial deployment we inevitably had additional Windows Updates which we applied before putting them into production.
We deployed 25 or so PCs in this manner and without warning the 5 most recent roll outs are reporting a Microsoft License Key which is different than the BIOS stored OEM key. The one thing we did differently on these 5 machines was that we connected to them with RDP to do the final setup before putting them into production.
When I tried to recreate this issue to see what step was causing the License key to change I was unable to recreate the failure. I followed the same steps we used on previous deployments, stopping at each step along the way to check and compare the license keys. I did these tests directly on the PC as opposed to RDP.
Does anyone have any idea what would cause this, how to prevent it or is there any cause for concern?
Thanks,
Brian
Continue reading...
This seemed to be working fine, we created our base image, sysprep'd the machine and captured the image. After deploying the image to a new PC, we went through the setup wizard, licensing, personalization, etc. and checked to make sure the OEM key was still in place (it was). After initial deployment we inevitably had additional Windows Updates which we applied before putting them into production.
We deployed 25 or so PCs in this manner and without warning the 5 most recent roll outs are reporting a Microsoft License Key which is different than the BIOS stored OEM key. The one thing we did differently on these 5 machines was that we connected to them with RDP to do the final setup before putting them into production.
When I tried to recreate this issue to see what step was causing the License key to change I was unable to recreate the failure. I followed the same steps we used on previous deployments, stopping at each step along the way to check and compare the license keys. I did these tests directly on the PC as opposed to RDP.
Does anyone have any idea what would cause this, how to prevent it or is there any cause for concern?
Thanks,
Brian
Continue reading...