Hope, we would get an answer. Doing reconstruction of same SKUs for each new build of W11 starts to be boring, the server task looks fresh. And if CUs are applicable, - even more interesting. I don't hate HCI, - not at all. Probably I know it not that good, as never administered it in real scenarios. In any case, I'd love to see it with Desktop Experience. xinso once showed how he made 17763.1_Hyper-V_Server_2019_Desktop_Experience - I was impressed, and am interested in repeating the lesson, to study that for myself. Once again, - modifying HCI is not that interesting as creating ServerDatacenter (not Core), - as modified Edition would be broken after some major CU, that would remove packages. And full Desktop Experience ServerDatacenter seems to be promising.
It's like HyperCore (no activation needed), its the core version with the richest set of roles / features, and can be reduced If your point is the wim size, with a single command to the HyperCore level. For me It's a sort of holy grail of no GUI servers Xinso do things for learning and for fun, While I personally prefer to learn on something I actually need/use. Personally I find practically pointless to build form scratch something that already exist (and that can be turned in a activationless Hypercore in 2 minutes) like Server 2019 with GUI. BUT I was all in in building GUI servers "2017" / 2018 / and 2020. Given they don't existed and given for various reasons I needed them. Like I explained in the dedicated thread especially my server 2020 has (again) a combination of features that you can only dream of on official ones (no matter what you pay for them) https://forums.mydigitallife.net/threads/guide-adding-gui-to-server-core-1-22v.76023/page-65 Who said you need to modify it? You *CAN* reduce it's size if you want, if you care about the storage. If you don't care, leave it untouched, a disabled role does nothing to RAM/CPU resources Removing the payload is something officially supported, MS itself does that with .net3.5
True. Just it happened, that for two years I was offline and missed it. As well as your project. I am quite interested in what you succeeded to do with ServerDatacenterCore 25398.1 I hope we may both try to do ServerDatacenter Desktop Experience with 25398 I do understand that 26100 comes in LTSC, but 200% sure that next year HCI gets update to 26200, ServerDatacenterCore gets its own AC build 26200, without Desktop Experience. Would be nice to know how to deal with it in advance. Starting with making 25398.1. Updatable SKU with Desktop Experience. Without custom updates. Sounds interesting.
ge_prerelease (262xx) will not have any production signature build. The next production signature build should come from se_release (or Dt/Br)
Q: What are these packages? Microsoft-Windows-Management-SecureAssessment-Package Microsoft-Windows-Management-SecureAssessment-WOW64-Package They are "Removable Package" for EnterpriseG.
gailium119 has made ServerDatacenter 25398.1, but due to some components being unavailable, he used other builds to replace it and was unable to install CU.
My 25398.830 Core series do not have "BCD-Template". e.g. Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.25398.830.mum Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.25398.830.mum Code: <update name="017db9b3d2d84badc56c70bbd5452e05"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Desktop-BCDTemplate-Client-Package" version="10.0.25398.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> Q: Where is it on Core? A: Microsoft-Windows-EditionPack-Core-Package~31bf3856ad364e35~amd64~~10.0.25398.763.mum.
I see. Anyway I don't consider the (lack) of updates a major problem. Obviously I use custom builds for my own infrastructure, not on mission critical scenarios, so .1 build would be more than enough. Speaking of which, like I said .763 already breaks things (even the untouched one), so patching the .830 may be interesting academically, but practically I prefer a .1 perfectly working over a updated one with a share of problems.