Hi, You can refer to a previous post:. Obviously Windows 1709 feature update name in SCCM has a new change: The name of 'Feature update to Windows 10, version 1709, en-us' has been replaced by 'Feature update to Windows 10 (business editions), version 1709, en-us' or 'Feature update to Windows 10 (consumer editions), version 1709, en-us'. 'business' means volume version; 'consumer' means retail version. Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Hi, You can refer to a previous post:. Obviously Windows 1709 feature update name in SCCM has a new change: The name of 'Feature update to Windows 10, version 1709, en-us' has been replaced by 'Feature update to Windows 10 (business editions), version 1709, en-us' or 'Feature update to Windows 10 (consumer editions), version 1709, en-us'. 'business' means volume version; 'consumer' means retail version. Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Windows 10 Business Edition Vs Pro

This makes it tricky to deploy upgrades in SCCM because CONSUMER (OEM/RETAIL) needs the consumer editions update and VOLUME needs the business update. SCCM does know somehow because the windows 10 servicing / all updates list - shows how many endpoints need the consumer or business updates in the required column. When I was deploying the business update, consumer editions would come back as successful but the update was not applied. I created a separate collection for consumer editions. If you open a remote command prompt and run C: windows system32cscript slmgr.vbs -dli it will report VOLUME, OEM or RETAIL Network Administrator.