Aller au contenu principal

Using ASD to deploy OEM Clients

Thread needs solution

Hello everyone
we purchased 100 lenovo pc (each pc comes with its own license Windows 10 Pro OEM downgraded to Windows 7 Pro)(Without COA, i believe that the code is in the bios)
We would like to use ASD to create one master image and distribute it to other pc
We can do this with ASD?
What should I do with Microsoft Licensing?
I read in some forums that I should buy a single VL license. It's right?

After we deploy the pc, we have to do some procedure for Windows Reactivation?

After we deloy the pc, we have to do some procedure for Sysprep?

 

Thx to all

0 Users found this helpful

antonio lubrano wrote:

Hello everyone
we purchased 100 lenovo pc (each pc comes with its own license Windows 10 Pro OEM downgraded to Windows 7 Pro)(Without COA, i believe that the code is in the bios)
We would like to use ASD to create one master image and distribute it to other pc

We can do this with ASD?

Yes, it should work.  

What should I do with Microsoft Licensing?

However, you would be deploying OEM licenses which are tied to the original hardware and since this is Window 7 and not 10, you would most likely need to go into each system after deployment and enter the proper registration key again... ther's a chance that you may have to call Microsfot to do this, but if you have the OEM keys (on the PC, or disc) and can enter those after the image, that will most likely work the first time for each one.

I read in some forums that I should buy a single VL license. It's right?

That would make it much easier since you're currently going to be dealing with OEM licenses and Windows 7 is not as friendly as Windows 10 when it cmoes to licensing  Using a VL will also be much more costly though.  

After we deploy the pc, we have to do some procedure for Windows Reactivation?

Yes, see above since you're using OEM licenses instead of a VL. 

After we deloy the pc, we have to do some procedure for Sysprep?

You can sysprep on the fly in the Acronis deployment, so no need to do that to your image first

Thx to all

Answers in bold in your quote.  FYI, you can grab a trial and test the process.  When using the offline bootable recovery media, you don't burn any deployment licenses either (good for testing).  You should have a license for each system being deployed to, but there is nothign preventing the use of bootable recovery media.

There are some caveats with drivers for new systems that have PCIE NVME hard drives. The public version of SD5 is still 1660 and does not have these drives baked in yet.  You will need the 1666 beta which is a driver update, but not officially released yet.  I can send you the link via PM.  

Keep in mind that the default LINUX recovery media, still lacks RAID drivers though.  Many of the new systems that have just a single PCIE NVME drive are still being set in the bios with a SATA mode of RAID, as this provides better performance than AHCI (deeper queue depth).  Should that be the case on any of your systems, you can temporarly switch the bios to AHCI mode, back and/or deploy adn then switch the bios back to AHCI. However, not all OEM bios firmware allows us to do this - some are hard set by the OEM with no option for the user to change. 

Or, you can create WinPE and inject the IRST (Intel Rapid Storage Technolgy) drivers.  The downside with the WinPE is that it does not include "stand-a-lone" deployment though :(