Now it is time to talk about volume licensing. You cannot use Windows Deployment Services, You cannot use cloning tools or other solutions. The important thing for a system administrator to know is this: when buying OEM, you do not have rights to create disk images or do something similar with these computers. OEM - this licence cost you less but is tied to that particular computer.Retail - this licence is most expensive but allows you to transfer it from one computer to the other one.This is not a problem, but here we have to introduce the topic of licences, especially client licences such as Windows 7. Your goal must be to do away with manual product key input and activation. You want a single key, embedded in the deployment image or script and run with that, or some other solution. When creating an automated deployment environment, one thing you definitely don't want to be doing is having to enter each individual Windows product key as found on the sticker somewhere on the chasis. All customization and automation is done with answer files using the Windows Automated Installation Kit. With WDS and some driver packs I can support as many different computer brands and models as I want with a single vanilla Windows 7 base image. WDS can also be used for creating images, but using images doesn't scale as you need too much manual intervention with the devices themselves and you need to update images constantly. I used WDS to create a fully automated installation of PCs. You may implement something like Windows Deployment Services. If you have to administer a large number of PCs running Windows, you will end up creating an automated deployment platform for your Windows clients.

What is a mak key