I can't find entg in 19044.1348 and above for online account issues. Nothing to do with entg-related components. If this is a feature, I will abandon this version.
I can't get any idea about it. I have uesed "Microsoft-Windows-EditionSpecific-EnterpriseG-Package-amd64-10.0.19041.1348.cab" to test "19044.1237". It's normal.
Test pure 19044.1348. Or the latest. e.g. 19044.1237 and 19044.1348 19043.1348 and 19044.1348 I would compare Product policy, the first thing.
Product policy from "EnterpriseGEdition.xml" right? Based on your suggestions, I will compare product strategies and find a time
What will be the difference between the old an new pack ? Just did an new image with the updated 1.xml, 2.xml and 3.xml from huynhlam2 Dism failed for me to with 1.xml & 3.xml
-Yeah It's failed. I have tested, And fixed the 3.xml -Yeah It's failed. I have tested, And fixed the 3.xml -But the configuration for an unattend.xml is not matter. It's just always keep at least one edition live or staged for keep this package Windows-Defender-AM-Default-Definitions-Package-amd64-10.0.19041.1 alive
I Don't think this will work with your packs as they are , i had to repack your packs with SxSv1. But you can use them as a hint on how to get it to work for you. 1.xml Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-EnterpriseSEdition-Package-amd64-10.0.19041.1.cab" /> </package> </servicing> </unattend> 2.xml Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend> 3.xml Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend>
I did simply added the Windows-Defender-AM-Default-Definitions-Package-amd64-10.0.19041.1 package to it to complete the image. Although the reconstructed image produces a LTSC 2021 19041.1 without Edge Legacy or Edge Chrome but there's one issue when the Cumulative update is added to it, it restores and disables the Edge Legacy package.