Windows licensing question

[Patch22]

Hi,

I have a potential client who supplies laptops pre-loaded with custom software to law enforcement agencies. All laptops supplied are the same make and model. They have standard Windows 7 Pro OEM licenses. The client is currently imaging the hard drives before shipping. If something goes wrong with Windows, the system is returned, the drive image reloaded and all is well again. The client has asked me if they can legally keep only one good hard drive image to be potentially reloaded on multiple laptops? They are currently keeping an image per laptop. I know that this is technically no problem but I am not sure on the legal licensing side of things with Microsoft? Technically, a single activated OEM installation of Windows 7 Pro. would be duplicated across multiple laptops. Each laptop has its own COA and so is this a problem at all?

Thanks for any help with this.

 

[FoolishTech]

I'm pretty sure that's completely against Microsoft's license.

What you should be doing is sysprepping the image to 'reseal' it before finalizing your image - so it prompts you for the product key after re-imaging on the different machines.

Also this way you can "generalize" it so each machine doesn't end up with the same SID - granted I believe what I read in a pretty good article by a Microsoft MVP or employee, don't remember which and from somewhere I don't recall, that basically debunks the idea that identical SIDs on the same network will cause some 'issues' - still for me it's good practice to do so.

 

[YeOldeStonecat]

I agree with FT....
Proper way is to run sysprep, seal it for end user, power down...and then clone the image (or clone to the rest of the fleet if you're doing a fresh deployment).

Upon first bootup, it will seek the key...and..you know the rest.

This way is will be proper and "neutral" no matter what your destination clone is...and will need a license upon first bootup.

And yeah...in real life you can unbuckled a bunch of cloned images that were not sysprepped...and run just fine. They'll actually generate new SIDs once you give them unique names...rename computer, reboot...NOW you can join error free. BUT...I still like to sysprep, because it's the right way to do it. And sometimes...you'll see some SID error years down the road. Hmm...wonder if that was caused because this machine is an image that was never sysprepped. Why ask why! Guinness for Strength!

 

[Patch22]

Ahh yes, just been using Sysprep to reseal a refurbished laptop. Could we get away with sysprep /oobe as this also prompts for the product key? In this way we could avoid using sysprep /generalize which removes p+p drivers. Otherwise we will have to make answer files with sysprep.

The SID issue isn't a problem as the laptops all go to different locations, but I've also read that same article, I think it was part of systernals stuff.

Thanks

 

[YeOldeStonecat]

I just click that 3rd button...I never profile any answer file.

Quick 'n easy...watch the hourglass for 30 seconds, it shuts down..and go clone.

 

[Patch22]

I just click that 3rd button...I never profile any answer file.

Quick 'n easy...watch the hourglass for 30 seconds, it shuts down..and go clone.

Yep, I do the same but just wanted to make sure this was adequate from the Microsoft licensing/legal point of few.

Thanks