I see both in updates. I assume that in 2022 there are both full and core for Turbine. The update.mum of any Rollup proves that: Code: <assemblyIdentity name="Microsoft-Windows-ServerTurbineCorEdition" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> <assemblyIdentity name="Microsoft-Windows-ServerTurbineEdition" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
No offend at all. I really study a lot from you. But in case of Desktop Experience --> ServerTurbine I think you are wrong and there is a Core -->ServerTurbineCor
OK. Nice information. Thanks. (I do not use it, hence I do not pay much attention to it. Have a good sleep! No worries.)
Thanks. If you need VHD/WIM for 2022 or VHD for 2019, PM me. Can't post it here, would be banned. We don't use ServerTurbine yet because Hotpatch technology (server-side) has not yet been documented for AzureStackHCI. When we would be able to update Windows VMs without reboot (and Hotpatch, as was demonstrated on TechReady comes to Linux VMs in future too), we would switch from normal STD/DTC 2019/2022 VMs to Turbine VMs. They are free to use when you have subscription, and MSFT doesn't care if they are run in Azure or on-prem in HCI. That is the last step to sink VMware.
20348.112 LCU --> OK 20348.143 LCU --> NOT OK Q: Restriction to non-Azure? PS. New Child-package microsoft-client-license-flexible-platform-package~31bf3856ad364e35~amd64~~10.0.20348.143 of microsoft-windows-editionpack-serverturbine-package~31bf3856ad364e35~amd64~~10.0.20348.143 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-EditionPack-ServerTurbine-Package" version="10.0.20348.143" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="Microsoft-Windows-EditionPack-ServerTurbine" releaseType="Feature Pack"> <update name="09425fc3eb9e392e379df5fd66702fd3"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Client-License-Flexible-Platform-Package" version="10.0.20348.143" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="4832186a011c87c693169e239e0d998c"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Hotpatch-Payload-Package" version="10.0.20348.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="ff2ba25614aabd08f1cd58b72ec16273"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Hotpatch-Targeting-Gated-Package" version="10.0.20348.143" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="83c05787b3cf97dd4cec091eddff7f1b"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Hotpatch-Utility-Package" version="10.0.20348.143" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> </package> </assembly> IMHO, Any original image + Sysprep = Best policy (all for PSFX) Tomorrow, I'll try original updated package without renaming build. But, only this one is really updated for 20348.112: Microsoft-Windows-Editions-ServerTurbine-Package-amd64-10.0.20348.112.cab See you tomorrow.
If you run it on vSphere or Windows Server Hyper-V, Admin Center shows warnings. If you run on HCI, everything is fine.
Let alone platform. For LCU, it needs f\n\r in WinSxS? (But initial build does not have those.) Conjecture is useless. Tomorrow.
I don't undesrstand the question. I miss some files for ServerTurbineCor 2022 reconstruction With 2019, another problem, that I was too late to get original Azure image of .1068, and miss some files. Had no time to dig into, as don't consider 2019 something important now. ServerTurbineCor 2022 is more interesting
No original source = PSFX update failed Code: C:\windows\system32>dism /English /image:F: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.1151 Current edition is: Current Edition : IoTEnterpriseS The operation completed successfully. C:\windows\system32>dism /English /image:F: /get-targeteditions Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.1151 Editions that can be upgraded to: Target Edition : EnterpriseS The operation completed successfully. C:\windows\system32>
By the way, the EditionMatrix.xml show interesting things (I removed what is well known): Spoiler <?xml version="1.0" encoding="utf-8"?> <TmiMatrix xmlns:e="urn:schemas-microsoft-com:windows:editions:v1"> <Edition ID="ServerAzureCor" name="Microsoft-Windows-ServerAzureCorEdition" processorArchitecture="amd64" buildType="release" publicKeyToken="31bf3856ad364e35" version="10.0.20348.143"></Edition> <Edition ID="ServerDatacenterACor" name="Microsoft-Windows-ServerDatacenterACorEdition" processorArchitecture="amd64" buildType="release" publicKeyToken="31bf3856ad364e35" version="10.0.20348.143"></Edition> <Edition ID="ServerStandardACor" name="Microsoft-Windows-ServerStandardACorEdition" processorArchitecture="amd64" buildType="release" publicKeyToken="31bf3856ad364e35" version="10.0.20348.143"> <Target ID="ServerDatacenterACor"/> </Edition> <Edition ID="ServerTurbineCor" name="Microsoft-Windows-ServerTurbineCorEdition" processorArchitecture="amd64" buildType="release" publicKeyToken="31bf3856ad364e35" version="10.0.20348.143"></Edition> <Edition ID="ServerTurbine" name="Microsoft-Windows-ServerTurbineEdition" processorArchitecture="amd64" buildType="release" publicKeyToken="31bf3856ad364e35" version="10.0.20348.143"></Edition> <Edition ID="ServerHyperCore" name="Microsoft-Windows-ServerHyperCoreEdition" processorArchitecture="amd64" buildType="release" publicKeyToken="31bf3856ad364e35" version="10.0.20348.143"></Edition> </TmiMatrix> So, there are both ServerTurbine and ServerTurbineCor Hyper-V Server (aka ServerHyperCore) still exist Semi-annual versions ServerStandardACor and ServerDatacenterACor exist too. There is something more Azure then "Azure Edition", aka ServerTurbine - ServerAzureCor Good to know. Plenty of practice! Once again, thank you for valuable knowledge!
Am faced with an interesting question. I am trying to create Azure Stack HCI (Full), following your receipt from last year when you created ServerHyperCore Full. Modified the Microsoft-Windows-ServerAzureStackHCICorEdition~31bf3856ad364e35~amd64~~10.0.20348.1.mum to include Full features, and applied unattend from full ServerDatacenter to HCI full (modified mum) Everything is fine, I can install, boot and even update. But if I install cumulative update, that updates Microsoft-Windows-ServerAzureStackHCICorEdition component, system rolls back to Core. What is a solution - not to update this component, while using rollups for all others?
Very strange phenomenon, EnterpriseS can be updated to 19044.1151 with Windows10.0-KB5004296-x64-baseless.cab+Windows10.0-KB5004296-x64-baseless.psf, but Windows10.0-KB5004296-x64 downloaded directly by UUP does not work. Code: Microsoft Windows [版本 10.0.19044.1110] (c) Microsoft Corporation。保留所有权利。 C:\Windows\system32>dism /image:D:\1 /add-package:D:\19044.1151\windows10.0-kb5003791-x64.cab 部署映像服务和管理工具 版本: 10.0.19041.844 映像版本: 10.0.19041.1151 正在处理 1 (共 1) - 正在添加程序包 Package_for_KB5003791~31bf3856ad364e35~amd64~~10.0.1.2 [==========================100.0%==========================] 操作成功完成。 C:\Windows\system32>Dism /image:D:\1 /get-CurrentEdition 部署映像服务和管理工具 版本: 10.0.19041.844 映像版本: 10.0.19044.1151 当前版本为: 当前版本 : EnterpriseS 操作成功完成。 C:\Windows\system32>Dism /image:D:\1 /get-targeteditions 部署映像服务和管理工具 版本: 10.0.19041.844 映像版本: 10.0.19044.1151 可以升级的版本: 目标版本 : IoTEnterpriseS 操作成功完成。 C:\Windows\system32>DISM /Image:D:\1 /Set-Edition:IoTEnterpriseS 部署映像服务和管理工具 版本: 10.0.19041.844 映像版本: 10.0.19044.1151 开始升级组件... 开始安装产品密钥... 产品密钥安装已完成。 开始应用特定于版本的设置... 特定于版本的设置应用已完成。 操作成功完成。 C:\Windows\system32>
Time is passing away, man is getting old. And Windows is changing... Good old way work, but really help? Good medicine is always bitter.