Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Thursday, October 19, 2017 7:56 AM
Hi,
Downloaded from VL portal Windows 10 Enterprise 1709 (as I understand all other editions like Pro, Edu, N are in one ISO file).
When I try inplace upgrade using downloaded ISO from LTSB 2016 to 1709, installer wants to upgrade only to Windows 10 Pro edition and I cant change or tell somehow to upgrade to Windows 10 1709 enterprise edition. Tried at least on two computers. There is no problem, when i try to upgrade from LTSB 2016 to 1703 Enterprise version.
Friday, October 20, 2017 2:35 AM
Yes, what you are facing is normal.
Windows doesn’t embed the key, the OEM has to do that, your computer should be a pre-install system device.
If you want to use Enterprise 1709, backup data in advance, format C partition and clean install
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Friday, October 20, 2017 6:36 AM
Thanks.
Is there official documentation, that it unsupported to upgrade from Windows 10 LTSB to Windows 10 Enterprise CB. I can only find this:
In-place upgrade from Windows 7 or Windows 8.1 to Windows 10 LTSB is not supported.
But nothing about Windows 10 LTSB to Windows 10 Enterprise CB.
And this:
If an organization has devices currently running Windows 10 Enterprise LTSB that it would like to change to the Semi-Annual Channel, it can make the change without losing user data. Because LTSB is its own SKU, however, an upgrade is required from Windows 10 Enterprise LTSB to Windows 10 Enterprise, which supports the Semi-Annual Channel.
Nothing about, that upgrade is unsupported
After looking in upgrade log:
ProductKey: Looking for product key in Digital Marker.
ProductKey: Product key found in Digital Marker.
ProductKey: Validating Product Key for Image.
SPValidateProductKey: Calling PidGenX
ProductKey: Product key using pkey edition = [Professional].
ProductKey: Matching Install Wim For Exact Editions
ProductKey: Matching Install Wim.
ProductKey: Matching Install Wim: Found [1] matching images.
ProductKey: Extracting Eula
ProductKey: Product key was successfully validated.
ProductKey: Product EditionID = Professional
ProductKey: Product InstallChannel = OEM
i think the problem is that installer found product key embedded in computer BIOS/UEFI and as it is of course for Professional Edition, it automatically selects Pro Edition for installation.
So if there was Windows installation ISO with only Enterprise Edition (like 1703) there will be no problem to do in-place upgrade, like we have done before.
On one old computer (I assume without key in BIOS) after running setup it gives choice which version I want to install, and I successfully upgraded from Windows 10 LTSB 2016 to 1709
Friday, October 20, 2017 9:03 AM
>>i think the problem is that installer found product key embedded in computer BIOS/UEFI and as it is of course for Professional Edition
You are right.
I find out this article:
Assign devices to servicing channels for Windows 10 updates
/en-us/windows/deployment/update/waas-servicing-channels-windows-10-updates
Switch LTSB to CB, we need to have a media to upgrade, and, target CB system must be a higher version.
So, in your last paragraph, upgrade operation succeed.
However, only when you have a current Software Assurance agreement (or similar licensing rights) that grants you rights to use the Current Branch, you can convert your installation from the LTSB to the Current Branch, so we don’t switch LTSB to CB via in-place upgrade generally, simple use the Configuration Manager console to switch from LTSB to Current Branch.
Thanks for your correcting.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Friday, October 20, 2017 12:18 PM
Switch LTSB to CB, we need to have a media to upgrade, and, target CB system must be a higher version.
I have ISO file downloaded from Volume Licensing portal (ISO qualifies as a media, right?), CB 1709 is higher version than LTSB 2016 (right?). We have all licensing rights to use LTSB or latest CB. In my opinion it should work without ConfigMgr or other management solution.
This particular problem could be resolved just by publishing ISO with only Enterprise version inside install.wim (like with version 1703).
Thanks
Monday, October 23, 2017 11:17 AM
Resolved my problem by starting installation from command line:
setup.exe /auto upgrade /pkey {Windows 10 Enterprise KMS key}
Tuesday, October 24, 2017 7:38 AM
Same story with ConfigMgr. Upgrade task sequence is failing. Regardless I set target edition to Windows 10 Ent:
in log files I found that it is trying to install Pro version:
MOUPG MigChoice: Initializing Drive Letter: [C]
MOUPG MigChoice: Initializing Image Index: [5]
MOUPG MigChoice: Initializing Image Name: [Windows 10 Pro]
MOUPG MigChoice: Initializing Wim Ref Count: [0]
MOUPG ProgressHandlerAction: Sending initial progress message for action [5].
MOUPG CompatMigrationChoice: Entering Execute Method
MOUPG CDlpActionCompat::ExecuteMigChoiceScan: Enter
MOUPG Target OS: Edition = [Professional]
MOUPG Target OS: Product Name = [Microsoft� Windows� Operating System]
MOUPG Target OS: Language = [en-US]
MOUPG Target OS: Architecture = [amd64]
MOUPG Target OS: Version = [10.0.16299.0]
MOUPG Target OS: SPVersion = [15.0]
MOUPG Target OS: Detected Source Edition = [EnterpriseS]
MOUPG Target OS: Detected Source Arch = [amd64]
MOUPG Target OS: Detected Source Version = [10.0.14393.0]
MOUPG Target OS: Detected Source SPVersion = [0.0]
MOUPG Target OS: UpgradeFlags = [0x10003]
And of course is failing with 0xC1900204 (migration not available) error.
Thursday, October 26, 2017 1:44 AM
Look at this blog
Windows 10 Pre-Upgrade Validation using SETUP.EXE
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Tuesday, November 14, 2017 4:17 PM
Mareks I am running into the exact same issue. Only on one model of workstation. Even know my inplace upgrade is set to W10 Ent, this machine fails with the log errors you have above. Goes to Windows 10 Pro.
Let me know if you found a solution.
thanks, J
Wednesday, May 23, 2018 12:38 PM
I need to upgrade all my Workstation that are in 1607 LTSB, I would like to use SCCM, can this be done and how?
Dan White