Configuration Manager technical preview version 2401

@Bala_Delli So, if the CMG Auto-Patching is not included in 2403, what is the correct way to update the image manually? By creating a new CMG and removing the old one? I started getting requests because of the advisor recommendations (VMSS in your subscription are running on images that have been scheduled for deprecation).

Thank you.

Bala_Delli  There's no reboot required but it's being interpreted as such because there are i presume locked files needing updates presumably because it's setting that reg key you mentioned and there's no distinguishing between "close the app" and "reboot the system". Once the user closes and reopens office the updates take effect but if a reboot has been prompted for already, the user may go and do it anyway.

I suspect this is more of an office thing than an SCCM thing but since you have the O365 update integration and ADRs it would be nice to have some facility to suppress it somehow. For example if we could see the update in software centre, but have it show a status of reboot required but not actually pop up a notification saying that, that would be a good compromise. I.e. if user goes looking into software centre and nosing around they would see a spurious "please reboot" but it wouldn't actually prompt for one interactively through the normal software centre toast / popup notifications.

Co-management requires Azure Hybrid registration right? Which happens at system / machine level. So when we use proxies, which we do, this goes looking for a system level proxy. Which is fine and all, except setting a system level proxy then went and broke WiFi captive portals etc. because they went trying to find our proxy before they'd actually connected to our DirectAccess.  So we abandoned any plan to softly move into a hybrid joined world I'm afraid.

On another semi-related topic in the sense that it's SCCM related but probably not SCCM's fault.....have just discovered we can't offline service Windows 11 images anymore using SCCM, because of the switch to UUPs? I've seen elsewhere that the recommendation is to just download updated ISOs every month but for orgs like ours where we still customise the image to do things like zap store apps and add language packs and so on, this isn't a runner. Any plan for this much needed automation facility to return?

lexcyn - Yes, this is tested and it will work. We can install CM console on Win 11 Arm device.

sutliff1805 - Yes, CMG VMSS has an option to Auto update the image. But we might revert this change in CB as we found few regression.

Ronan_Fahy - This seems to be by design behavior as  some of the application requires reboot so it checks the registry key and notify the same. Lets take this feedback and check what enhancement can be made. Can you move towards Co-management and this behavior will not be observed.

Will the Configuration Manager Console install and run on a Windows 11 ARM device as well? Or does it at least have emulation support?

Off topic but an SCCM question. Office 365 updates via SCCM, using ADRs, work great. However, software centre prompts the user to restart their PC afterwards, which isn't required with office. Conventional wisdom based on multiple blogs etc, would say the solution is to set the deployment's user experience settings to "hide in software center and hide all notifications". That has the desired effect of stopping the reboot prompt BUT it means there's no visual indicator in Software Center of the status of the update, or even anything to indicate whether the device even sees the update. So without trawling logs it's not possible to see if the update wasn't found as available, tried and failed, is waiting for something etc.  Has any thought been given to a middle ground option. e.g. "show in software centre, don't show any notifications" or something. Incidentally the relatively recent "enable update notifications from microsoft 365 apps" has no effect on this behaviour as these are software centre level restart prompts, not office.

Can you elaborate on "Enabling Auto-Image Patching for CMG Virtual Machine Scale Set"

I do not understand - is this saying the CMG VMSS itself is being auto-updated?  What image is being auto-updated?

As for "Automated diagnostic Dashboard for Software Update Issues", I look forward to that!  There are so many reasons an error can be created (power down during scan or lost network connection) that hopefully this can fix or help fix the real errors.