kenlotterman
asked on
Activating Windows 10 and Office on cloned computers
I set up one Windows 10 computer just the way I wanted it with antivirus, proprietary software, updates, and the like. I then used EASEUS disk copy to do a bit-by-bit clone to the hard drives of 11 other (identical) computers. The first time I start one of the other 11 Computers, it checks the hard drive for errors, repairs them, then boots into windows 10 perfectly. So there is that.
After a while (I'm not sure how long, because it happened overnight), the cloned computers tell me to activate windows. I need to make it clear at this point that I have done nothing to activate windows yet. I'm afraid to based on horror stories I can tell you about Microsoft activations.
What do I have to do to activate windows successfully on the 11 CLONES? And/or what should I do BEFORE activation? I seem to recall that with Windows up to Windows 7, I could use a utility to change the product key and then it would be happy, but I have also heard that Windows 10 does not use a product key.
If activation requires a Microsoft account, it is important for you to know that these computers will be used at six different locations – two per location. They do not belong to me, so I don't really want my email address associated with them. There are corporate email addresses that can be used, but the corporate email addresses are not associated at this point in time with a Microsoft address or account.
Then there's THIS, too: I purchased 12 "copies" of Microsoft office directly from Microsoft and got 12 product keys from them. I was told by a Microsoft tech support agent that I could purchase them all using one microsoft account, then install them using that account, but then sign in with a different account later. On the "master" computer, I clicked on the install link on the email they sent me and then chose to download the image file to install later. I am fearful that the Microsoft Office image that I downloaded (and is now on each of the cloned hard drives) somehow includes the product key, and when I install office on each of the 11 clones, Office will think that it has already been installed and will not activate. I need to know how to overcome that if that is indeed the case. Can I install office and then change the product key? I also know that Microsoft provides two different product keys and they are not the same, So I will not know which key to use or where to get the proper key if it is not the one that they emailed me.
Thanks.
After a while (I'm not sure how long, because it happened overnight), the cloned computers tell me to activate windows. I need to make it clear at this point that I have done nothing to activate windows yet. I'm afraid to based on horror stories I can tell you about Microsoft activations.
What do I have to do to activate windows successfully on the 11 CLONES? And/or what should I do BEFORE activation? I seem to recall that with Windows up to Windows 7, I could use a utility to change the product key and then it would be happy, but I have also heard that Windows 10 does not use a product key.
If activation requires a Microsoft account, it is important for you to know that these computers will be used at six different locations – two per location. They do not belong to me, so I don't really want my email address associated with them. There are corporate email addresses that can be used, but the corporate email addresses are not associated at this point in time with a Microsoft address or account.
Then there's THIS, too: I purchased 12 "copies" of Microsoft office directly from Microsoft and got 12 product keys from them. I was told by a Microsoft tech support agent that I could purchase them all using one microsoft account, then install them using that account, but then sign in with a different account later. On the "master" computer, I clicked on the install link on the email they sent me and then chose to download the image file to install later. I am fearful that the Microsoft Office image that I downloaded (and is now on each of the cloned hard drives) somehow includes the product key, and when I install office on each of the 11 clones, Office will think that it has already been installed and will not activate. I need to know how to overcome that if that is indeed the case. Can I install office and then change the product key? I also know that Microsoft provides two different product keys and they are not the same, So I will not know which key to use or where to get the proper key if it is not the one that they emailed me.
Thanks.
Your first problem is that you've likely violated Microsoft licensing for Windows 10. The second is that the computers themselves are probably in an unsupported state and if they belong to a business, that could be VERY bad instead of just bad. The third problem is that, if I remember correctly, you're also probably violating Office licensing.
What do I mean?
Microsoft prohibits end users (or agents on their behalf) from cloning (proper term is imaging) workstations *UNLESS* done in a very specific manner. Specifically:
1. The image MUST be built using a Volume License and activated using a Volume License key.
2. The reference computer (the proper term for the system you customize before imaging) should be built in Audit mode.
3. You *MUST* run SYSPREP to seal the image when you're done building it. This is NOT OPTIONAL. This ensures the computer is seen as unique on the network and prepares and configures it to be deployed and setup appropriately.
Failure to do the above is almost certainly why "The first time I start one of the other 11 Computers, it checks the hard drive for errors, repairs them"
WHAT you use for imaging is entirely up to you... though it's a waste of money in my opinion to use anything other than Windows Deployment Server (role available in Windows Server) and combine that with the Microsoft Deployment Toolkit (free)
As for Office, to deploy it through imaging (I'm 98% certain) you must use a Volume License version of Office as well. If you had purchased the correct version of Office, you'd only have one key for all copies.
If you're a Microsoft approved OEM then you have specific tools that allow you to do this instead of the ones I mentioned...
What do I mean?
Microsoft prohibits end users (or agents on their behalf) from cloning (proper term is imaging) workstations *UNLESS* done in a very specific manner. Specifically:
1. The image MUST be built using a Volume License and activated using a Volume License key.
2. The reference computer (the proper term for the system you customize before imaging) should be built in Audit mode.
3. You *MUST* run SYSPREP to seal the image when you're done building it. This is NOT OPTIONAL. This ensures the computer is seen as unique on the network and prepares and configures it to be deployed and setup appropriately.
Failure to do the above is almost certainly why "The first time I start one of the other 11 Computers, it checks the hard drive for errors, repairs them"
WHAT you use for imaging is entirely up to you... though it's a waste of money in my opinion to use anything other than Windows Deployment Server (role available in Windows Server) and combine that with the Microsoft Deployment Toolkit (free)
As for Office, to deploy it through imaging (I'm 98% certain) you must use a Volume License version of Office as well. If you had purchased the correct version of Office, you'd only have one key for all copies.
If you're a Microsoft approved OEM then you have specific tools that allow you to do this instead of the ones I mentioned...
It's unlikely you'll see any real enforcement from that policy on imaging, as it would put repair shops damn near out of business and cost businesses the world over multitudes more in cost if they had to follow the Microsoft no-no list. As for Office, these are after the fact installations if I interpreted his original post correctly. So it still stands that he should be perfectly fine so long as he has separate licenses for each instance of Office and Windows 10.
Agree with Lee. You just can't clone. Instead you need to create a real "image" of a PC that was customized in audit mode using Windows MDT or some other imaging tool (ghost, etc). then right before you grab the image, you run sysprep. Sysprep generalizes the PC and removes things like the unique identifiers that identify that specific PC that you cloned. If you have duplicated those identifiers that are unique to the original machine that you cloned? And you plug all of them in on the same network? Well then, you are in for a nightmare.
If I were in your position i would ask my customer for a list of their licensing keys and what type of keys they are and how you want the PCs to be license BEFORE you even start your loads. The type of license is important because the key always has to match the installer you use, otherwise you have to get on the phone to Microsoft for every activation. So you might even be using the wrong installer, you wouldn't know until asking your customer what licensing they have on hand and want you to use. But for only 10? I would burn the iso to a DVD and load them by hand. I would personally see no need to image for such a small number.
One thing @ Lee: I remember using a MAK key with a volume installer ISO, just here and there, and I'm pretty sure that's OK as long as it came with your volume license. I was told long ago that the reason you always get a small number of MAK keys when you buy a volume license (along with the normal KMS key) is for those weird situations when you are working on a computer that is not attached to the network or for some other reason can't reach the KMS server to get the key.
Also, there have been numerous times that I've heard of the situation where people have installed a version of Windows using the wrong installer and therefore couldn't use the key they had, but then were able to call Microsoft and get a new, converted key (over the phone) that worked. But i'm sure that this isn't possible when there is too big of a difference between the version of the installer versus the version covered by the license key.
If I were in your position i would ask my customer for a list of their licensing keys and what type of keys they are and how you want the PCs to be license BEFORE you even start your loads. The type of license is important because the key always has to match the installer you use, otherwise you have to get on the phone to Microsoft for every activation. So you might even be using the wrong installer, you wouldn't know until asking your customer what licensing they have on hand and want you to use. But for only 10? I would burn the iso to a DVD and load them by hand. I would personally see no need to image for such a small number.
One thing @ Lee: I remember using a MAK key with a volume installer ISO, just here and there, and I'm pretty sure that's OK as long as it came with your volume license. I was told long ago that the reason you always get a small number of MAK keys when you buy a volume license (along with the normal KMS key) is for those weird situations when you are working on a computer that is not attached to the network or for some other reason can't reach the KMS server to get the key.
Also, there have been numerous times that I've heard of the situation where people have installed a version of Windows using the wrong installer and therefore couldn't use the key they had, but then were able to call Microsoft and get a new, converted key (over the phone) that worked. But i'm sure that this isn't possible when there is too big of a difference between the version of the installer versus the version covered by the license key.
william the problem isn't the imaging the problem is the SIDs for the hardware .. it's all going to be duplicated from the cloned machine. Isn't it? Maybe i don't know enough about the tool the asker is using.
It's unlikely you'll see any real enforcement from that policy on imaging, as it would put repair shops damn near out of business and cost businesses the world over multitudes more in cost if they had to follow the Microsoft no-no list.
So you advocate theft of rights? Just because they don't often go chasing down businesses doesn't make it less a violation or somehow not theft. You are stealing capabilities that have not been granted you. THEFT.
Further, I said the installation requires the image be built using a volume license. You don't need a volume license for EVERY copy of Windows. You need ONE. PERIOD. Microsoft grants re-imaging rights on systems with Pro installed when you buy even a single Pro VL license. The net cost - *IF* you don't already have a volume license - is $180 or so. MAYBE $220 if you have to buy throwaway licenses to open a VL agreement. Cheaper than most deployment software and definitely cheap enough that you don't have a good excuse for violating licensing in my opinion.
Assuming that the licenses are corporate VLK ones, you can Run slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xx
The XXXXX's represent your unique keys required for MS Windows.
For office just load all licenses onto 1 account, download the installer, and run it on all 12 machines.
When audited MS will be able to see that you own the 12 licenses under your account.
If OEM then you can get burned if MS audits corporate and they show you deployed it if they do not have adequate licensing to cover their systems legitimately. Cloning OEM is technically a No-no, but as long as licensing adds up MS does not really care.
The XXXXX's represent your unique keys required for MS Windows.
For office just load all licenses onto 1 account, download the installer, and run it on all 12 machines.
When audited MS will be able to see that you own the 12 licenses under your account.
If OEM then you can get burned if MS audits corporate and they show you deployed it if they do not have adequate licensing to cover their systems legitimately. Cloning OEM is technically a No-no, but as long as licensing adds up MS does not really care.
ASKER
To address some of the comments above, I will clarify the question. The PCs all came with "Windows 7 preinstalled through downgrade rights of the Windows 10 Pro license." (Quoted from the "Recovery Media Entitlement" instruction sheet included with each of the PCs.)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi,
Everything Lee said is correct.
Cloning software is for HOME use. If you have a business you need to do it the correct way because:
a) you can get support from MS in future
b) you hardware will behave as expected - if you clone sometimes bad things happen that you can't explain and because of (a) you will be on your own
c) the license ability to clone is for OEMs only
You need MDT + WDS + KMS. That is the professional, supported way. Anything less is playing roulette with the business and the law - FAST still offer a cash bounty for improper licensing.
Mike
Everything Lee said is correct.
Cloning software is for HOME use. If you have a business you need to do it the correct way because:
a) you can get support from MS in future
b) you hardware will behave as expected - if you clone sometimes bad things happen that you can't explain and because of (a) you will be on your own
c) the license ability to clone is for OEMs only
You need MDT + WDS + KMS. That is the professional, supported way. Anything less is playing roulette with the business and the law - FAST still offer a cash bounty for improper licensing.
Mike
ASKER
While everyone else told some how I was doing it wrong, Jackie gave the best answer - I was able to get W10 install media from Lenovo and use it on all 12 computers. I had to do it the "long way", but it's in accordance with license and stable.
As to the first question, you can likely do the same across all machines - A phone activation. Windows 10 does indeed still use a product key and you can change it as needed. You do so by navigating to Settings > Activation > Change Product Key (Unless this has changed as of the Creator Update).