Jump to content

Recommended Posts

Posted

Hi folks, I know some of this should be basic stuff but it's been years since I've looked at this...

We've got an influx of Windows 10 Pro laptops - they are HP and I've noticed that they don't have Product Code stickers, apparently it's hard coded onto the motherboard!

I'm trying to set up WDS on our now rather ancient 2008 R2 servers. My concerns are these:

Should I be using MDT or something else instead?

I'm planning on capturing the image from one of the HP laptops, the pre-installed Windows 10 Pro. I have made my tweaks and installed some of our software on it - if I try to install the sysprepped image onto another one of the HP laptops, will it automatically re-activate WIndows with the hard-coded product key or am I screwed with that??

 

Please help if you can....

 

thanks!

Posted

If your site does not have a site licence for windows what I had to do with similar HP laptops was contact HP and get the correct windows 10 install disk this includes auto activating windows. When I tried creating the image from one of the laptops and pushing it out to others it didn’t like certain bits.

 

We moved onto MDT about 3 years ago so much easier for yourself to use than just WDS.

  • Thanks 1
Posted
I'd think that as long as you install the correct version of Windows 10 (home or Pro) then the slmgr.vbs /ato would use the local key and work. Not sure how to automate that.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...