K2000 Scripted install - Windows 10 version weirdness (Windows 10 Pro/Windows for Workstations)
Short version:
Scripted install for Windows 10 Pro (1709 at the moment) - we use a VLK embedded in the answer file and since win10 has "all the versions" on one single ISO, your answer file also needs to specify which OS version you are loading, re:
Scripted install for Windows 10 Pro (1709 at the moment) - we use a VLK embedded in the answer file and since win10 has "all the versions" on one single ISO, your answer file also needs to specify which OS version you are loading, re:
<InstallFrom>
<MetaData wcm:action="add">
<Key>/image/index</Key>
<Value>5</Value>
Recently (as in the last 3 months) when we image Dell Precision systems based on Xeon CPU's, the scripted install appears to complete and "activate" normally, with our VLK and all that, except the windows OS version is "Windows 10 Pro for Workstations" (meaning my installs from the K1000, which are OS specific, don't run). Manually re-entering the VLK via "change product key", and re-activating instantly changes the OS version to the correct SKU
Any ideas how/why? I'm at a loss. We've never seen this behavior prior to 1709, and all non-Xeon CPU machines image correctly. It's a mild annoyance to have to manually pop a key on on random machines.
Any ideas how/why? I'm at a loss. We've never seen this behavior prior to 1709, and all non-Xeon CPU machines image correctly. It's a mild annoyance to have to manually pop a key on on random machines.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
Pressanykey
6 years ago
Hi,
as you say you've never seen this behaviour prior to 1709 the logical conclusion is that it is a problem with the 1709 build...
As this is the case the only option you have is to script (it's a few command lines calling vbs scripts) that change / re-enter the product key and attempt to reactivate post deployment for these HW models.
Cheers
Phil
p.s.
Use LTSC (the OS formerly known as LTSB), really, it's a lot less hassle unless you really need all the bells and whistles (and other c*ap)... but if your using Pro that can't be the case.
Comments:
-
Don't use Pro, thumbs down
LTSB and Enteprise LTSB for the win.
Anyway, you could add a post installation task to re enter and re-activate the key.
see:
https://support.quest.com/kace-systems-deployment-appliance/kb/226326/unable-to-activate-windows-10-with-post-installation-task - Channeler 6 years ago
