 |
 |
After playing around some, I've managed to find a way to work around this problem, figure I'd share it in case anyone else comes up with the same issue. Apparently the key is to use the default product key that MS has provided for Win 10 pro, update from home to pro with that, and then enter the key for enterprise (or presumably, the pro key from the computer store too). The key from MS is: VK7JG-NPHTM-C97JM-9MPGT-3V66T Note, this key will upgrade the home machine to pro, but it will *not* activate the system with this key (so I'm not giving you anything you can do something nefarious with). After you've done that initial update to pro, you still have to put in a valid pro or enterprise license key, and after you've done that, you'll be able to properly activate. So basically, you have to change the product key on the system twice, but that's still better than trying to do a fresh install. So hopefully, if anyone else happens to be doing things the same way I have, hopefully this will save them a little aggravation and time. Gary ---------- Forwarded message ---------- From: Gary Schrock <[log in to unmask]> Date: Thu, Mar 31, 2016 at 12:57 PM Subject: windows 10 oem home to enterprise errors To: [log in to unmask] Not sure if anyone else has run into this, but with the latest batch of computers we've tried doing this on, it's become an issue. Because of our license with MS, I've seen recommendations that one can order the home version of the OS, and then upgrade it with the product key to either pro or enterprise as needed. I've had a number of machines that I've upgraded to the enterprise license without any problems (although I have to admit, at least some of them started at pro, but I *thought* I'd done some from home). However, with our latest batch of machine (Dell Optiplex 7040's), I'm finding it's not as simple as just changing the product key. We get an error about activating when doing that (0xc004f014), with slui reporting that the product sku is not found. Doing some research, it seems that there might be issues with trying to do this on machines that have the windows 10 oem home key embedded. Haven't found a real way around this so far, although I suspect just reinstalling the OS from the enterprise media should hopefully get us around this, just something of a nuisance. Just figured I'd pass along a heads-up in case anyone else out there has been doing this.