You can try this: 1)Add these packages to server: Microsoft-Windows-EditionSpecific-EnterpriseS-Package Microsoft-Windows-Client-Desktop-Required-Package Microsoft-Windows-Client-Desktop-Required-WOW64-Package Microsoft-Windows-Client-Features-Package Microsoft-Windows-Client-Features-WOW64-Package Microsoft-Windows-EditionPack-Professional-Package Microsoft-Windows-EditionPack-Professional-WOW64-Package Microsoft-Windows-Common-RegulatedPackages-Package Microsoft-Windows-Common-RegulatedPackages-WOW64-Package Microsoft-Windows-Required-ShellExperiences-Desktop-Package Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package 2) Set windows edition to EnterpriseS (Change server key to EnterpriseS) 3) Remove these packages: Microsoft-Windows-EditionPack-Professional-Package Microsoft-Windows-EditionPack-Professional-WOW64-Package Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package 4) Modify branding OR this: https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-91#post-1875246
You want 20348.1 Client "up to date" by Client and Server "two Editions combined in one image", NOT Client and Server two Editions in one install.wim. Then Skylined's solution is just for you. NOT easy though: 1. Branding 2. EditionID These two things, if not properly handled, next CU will fail easily. And if "Windows Update" is not disabled, hassle when Microsoft pushes new updates. Potentially, if this happened, coming CU update will fail forever. Q: What are you after? If for stable 20348 System, the easiest way is to add Client ServerRdsh License and Key, and forget about EditionID display. In this way, both System and you are happy. If you want it as lite as possible without update hassle, you can 1. remove Microsoft-Windows-EditionPack-Server-Roles-Full-Package from Edition mum. 2. use custom update without Microsoft-Windows-EditionPack-Server-Roles-Full-Package in CU Edition mum. 3. install the custom CU "offline". e.g. ServerStandard.mum without optional Roles and Features. Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-ServerStandardEdition" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="Windows ServerStandard Edition" releaseType="Product"> <update name="Microsoft-Windows-Foundation-Package"> <package contained="false" integrate="visible"> <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-ServerCore-Package"> <package contained="false" integrate="visible"> <assemblyIdentity name="Microsoft-Windows-ServerCore-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionSpecific-ServerStandard-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionSpecific-ServerStandard-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionPack-Server-Full-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Server-Full-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionPack-Server-Full-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Server-Full-WOW64-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Server-DesktopUX-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Server-DesktopUX-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Server-DesktopUX-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Server-DesktopUX-WOW64-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionPack-Server-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Server-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionPack-Server-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Server-WOW64-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> </package> </assembly> Open the mum in CU, and delete\save likewise, it is custom CU. Why ServerRdsh? It is both Client and Server 2-in-1. It can do Client jobs, and Server jobs as well. As a matter of fact, it is tiny Server Microsoft made exclusive to SOHO or Professionals who need Remote Session Environment.
Retrieving list of package ids for edition [EnterpriseS]... - CTransmogManager::OpenPackageFromEditionId Failed opening package for edition id [EnterpriseS]. hr = [0x800f0805] - CTransmogManager::GetCurrentEdition GetCurrentEdition: Error [0x800f0805] retrieving current EditionId value. - CTransmogManager::GetCurrentEdition Failed to get current edition! - CTransmogManager::ExecuteCmdLine(hr:0x800f0805)
That's it - it will behave like a client and has the aesthetics of client. Windows update will only offer you drivers. To upgrade you have to use the switch and switch back to server and reboot - then you will get the server updates. After you can switch back to the client mode. Dism will always give this error in client mode - if you switch to server mode dism will give you the server edition. As xinso also said you cannot have Client and Server two Editions in one install.wim Is this what you were looking for - the 20348.681 iso is based on this.
I was looking forward to working EnterpriseS DISM cause I know It's possible as Xinso has fixed it and has done a 20348 build with working DISM and he knows how to make DISM work just doesn't want to share how to fix it. I appreciate you spending time here with me debugging whilst xinso is unfortunately laughing his a** at us knowing the solution but not sharing Good night. Thank you.
I do not agree with you. xinso has successfully made 20348 client versions and dism does work with them. But it's different when you try to blend client and server - remember you removed some components to make the iso so dism is confused in client mode to get the edition. xinso has been my friend and mentor for a long time and I do appreciate his work.
Don't jump to conclusions - what you are referring to above is a client only EnterpriseS without server.