[ARCHIVED] Windows Editions Reconstruction Project

Discussion in 'Windows 10' started by whatever127, Jan 10, 2020.

Thread Status:
Not open for further replies.
  1. JeepWillys58

    JeepWillys58 MDL Addicted

    Nov 6, 2010
    603
    379
    30
    I completely agree, for those who know that "good taste" means always doing the best, so that the universe gives you back the best too, this is really mandatory, (and since Italian blood runs through my veins lol) "Good taste" is also make the best Carbonara for lunch! lol:chef:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,920
    150
    Not a shocking news, hard to find a Brasilian w/o at least some drops of Italian blood, (I have a couple of cousins in Belo Horizonte).
     
  3. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,280
    593
    60
    I agree 25398 is an extremely solid OS. I'm using the IoTEnterpriseSK flavor. But to be honest my ultimate version would be DataCenter. I've tried for weeks and just cannot get 'er done.
     
  4. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,047
    90
    #15924 LiteOS, May 8, 2024
    Last edited: May 8, 2024
    in which step u are stuck ? or part not work
     
  5. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,280
    593
    60
    I've got ServerDataCenterCor mounted but when trying to apply the .xml I get error messages.

    Here's the command I'm using:

    Dism /Image:C:\mount /Apply-Unattend:C:\sxs\1.xml

    Actually I have 4 .xml to apply:

    Dism /Image:C:\mount /Apply-Unattend:C:\sxs\1.xml
    Dism /Image:C:\mount /Apply-Unattend:C:\sxs\2.xml
    Dism /Image:C:\mount /Apply-Unattend:C:\sxs\3.xml
    Dism /Image:C:\mount /Apply-Unattend:C:\sxs\5.xml
     
  6. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,280
    593
    60
    One of the .mums I'm using is what you suggested earlier.

    <?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-ServerDatacenterEdition" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <package identifier="Windows ServerDatacenter Edition" releaseType="Product">
    <update name="Microsoft-Windows-Client-Desktop-Required-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Runlevel-Win4-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Runlevel-Win4-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Runlevel-Win4-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Runlevel-Win4-WOW64-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Client-Features-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Client-Features-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Client-Features-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Client-Features-WOW64-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-EditionPack-Professional-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-EditionPack-Professional-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-WOW64-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-RegulatedPackages-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-RegulatedPackages-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-WOW64-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Not-Supported-On-LTSB-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Not-Supported-On-LTSB-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Not-Supported-On-LTSB-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Not-Supported-On-LTSB-WOW64-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
     
  7. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,047
    90
    u didnt append
    u need the other packages
    like edition specific

    edit
    also keep the edition ServerDatacenterCor
     
  8. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    Are you using DataCenter packages ?
    If so which versions ?
    Can you list the packages needed to build DataCenter ?
     
  9. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,280
    593
    60
    Yes according to teacher xinso :worthy:

    This is what is needed:

    5-1. Microsoft-Client-License-Platform-Device-Licensing-Service-Package (which is lacking in Azure editions)

    5-2.
    Microsoft-Windows-Branding-ServerDatacenter-Package
    Microsoft-Windows-Editions-ServerDatacenterCor-Package
    Microsoft-Windows-Security-SPP-Component-SKU-ServerDatacenter-Package

    5-3.
    a. Microsoft-Windows-EditionSpecific-ServerDatacenterCor-Package in Microsoft-Windows-EditionSpecific-ServerDatacenter-Package structure
    b. Microsoft-Windows-ServerDatacenterCorEdition in Microsoft-Windows-ServerDatacenterEdition structure

    5-4. ServerTurbine image (as source)

    5-5. Modify Server Language Pack accordingly
     
  10. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    if this is the mum you will use, looks like you just need to add Microsoft-Windows-EditionSpecific-ServerDatacenter-Package
     
  11. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,920
    150
    I would like to have it as well.

    Now I have no time but maybe is possible to follow the way I used for server 2017/2018/2020.

    (not a proper reconstruction, but just the addition of client packages + rsat to the server core w/o removing anything from it, it may be not as elegant but they never failed me)
     
  12. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,280
    593
    60
    This is the modified Microsoft-Windows-EditionSpecific-ServerDataCentre-Package I am using.

    <?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-EditionSpecific-ServerDatacenter-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    <package identifier="Microsoft-Windows-EditionSpecific-ServerDatacenter" releaseType="Feature Pack">
    <update name="549efc7afb2d1797a7daa40c9c07bfb9">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Branding-ServerDatacenter-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="023bab96b6aca6953ae52ab8ce55bb4a">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Editions-ServerDatacenter-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="4119f4be3b737487e10b85319f65bd78">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-ServerDatacenter-Package" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    <update name="fd8891376f42cd98ae9f7a5335b4700f">
    <package contained="false" integrate="hidden">
    <assemblyIdentity name="Server-Help-Package.ServerDatacenter" version="10.0.25398.830" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </package>
    </update>
    </package>
    </assembly>
     
  13. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    which client packages to get desktop working ?
     
  14. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    what version are the Packages before they are modded ?
     
  15. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,280
    593
    60
  16. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    Cor what do you mean ?

    How did you make ServerDataCentre-Package from Cor ?

    Deployment will still be Cor.
     
  17. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,280
    593
    60
    I don't know Ace2....I'm at the point where I'm not sure what's up or down. I just tried to follow this format to the letter.

    5-1. Microsoft-Client-License-Platform-Device-Licensing-Service-Package (which is lacking in Azure editions)

    5-2.
    Microsoft-Windows-Branding-ServerDatacenter-Package
    Microsoft-Windows-Editions-ServerDatacenterCor-Package
    Microsoft-Windows-Security-SPP-Component-SKU-ServerDatacenter-Package

    5-3.
    a. Microsoft-Windows-EditionSpecific-ServerDatacenterCor-Package in Microsoft-Windows-EditionSpecific-ServerDatacenter-Package structure
    b. Microsoft-Windows-ServerDatacenterCorEdition in Microsoft-Windows-ServerDatacenterEdition structure

    5-4. ServerTurbine image (as source)

    5-5. Modify Server Language Pack accordingly
     
  18. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    From what i have read there maybe two method's

    1.Edition Specific switch in client build.

    2.acer-5100 said add client packages + rsat to server build, just need to know which client packages to use to get desktop working ?
     
  19. RobrPatty

    RobrPatty MDL Expert

    Jul 23, 2009
    1,280
    593
    60
    Up until now the only reconstruction process I have used is the auto conversion with 25398.1_ServerDatacenterCor_to_Client_amd64. So this manual method is way above my paygrade. I'm trying but I'm below amature right now I'm must admit.
     
  20. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,920
    150
    #15940 acer-5100, May 8, 2024
    Last edited: May 8, 2024
    I need to find my old batch, I lost track of where I placed them.

    But more or less they were based on the thread on server room about adding the gui to a core server.

    Edit found them

    At the end I needed to SKUwithch back to server because the packages forced the installation to a Client SKU

    Also may be needed to remove anything from

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\AlternateShells

    to get explorer.exe as the default shell (hence the proper GUI started)

    Code:
    cd /d U:\19041.1
    
    
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-Features-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-Features-WOW64-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Enterprise-Desktop-Shared-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Enterprise-Desktop-Shared-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Enterprise-Desktop-Shared-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Enterprise-Desktop-Shared-WOW64-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    dism /image:d:\  /add-package:"Microsoft-Windows-Desktop-Shared-Drivers-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\  /add-package:"Microsoft-Windows-Desktop-Shared-Drivers-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    
    
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-ShellExperienceHost-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-ShellExperienceHost-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-ShellLauncher-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-ShellLauncher-Package~31bf3856ad364e35~it-IT~10.0.19041.1.mum"
    
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-EmbeddedExp-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-EmbeddedExp-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-EmbeddedExp-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum"
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-Client-EmbeddedExp-WOW64-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    dism /image:d:\ /add-package /packagepath:"HyperV-UX-UI-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum
    dism /image:d:\ /add-package /packagepath:"HyperV-UX-UI-Client-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum
    dism /image:d:\ /add-package /packagepath:"Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    
    dism /image:d:\ /add-package /packagepath:"Multimedia-RestrictedCodecsCore-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum
    dism /image:d:\ /add-package /packagepath:"Multimedia-RestrictedCodecsCore-Package~31bf3856ad364e35~amd64~it-IT~10.0.19041.1.mum"
    
    dism /image:d:\ /add-package /packagepath:WindowsTH-KB2693643-x64.cab
    
    
    rem dism /image:d:\ /add-package /packagepath:"microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab"
    
    
    
    
    Obviously this is for 19041, I have no idea (yet) about changed package names and alike but you get the idea