@m0bilej0n@acjuelich The unfortunate thing is that, last time I checked, this doesn't support or exist (yet) for GCC and higher tenants (like me). So not all customers can leverage all the bells and whistles commercial tenants can.
@bdam555@PaulEAndrews Looks like it may address issues with RSAT/FoD installs that many folks have had challenges with and discussed on SCCM sub-Reddit. If so this would benefit even non-Co-Managed/WUfB devices I think. @PotentEngineer
@BaconActual @AdamGrossTX@brookspeppin I see them in the XML all the time too, but has never actually blocked an upgrade for us via TS, but just looks as if it is a problem when it isn't for us.
@cumbrianbluess@panusaukko@cBenammar Still he is right about 1909. I have a few 1803 left for me that didn't detect CU this month without SSU installed. (Yes they will be upgraded by June.)
@fadedmac@panusaukko That is what I'm doing. We deploy SSU very quickly after release and then by time clients scan for rest of updates the CU will be detected correctly for months like this and last month I think too for some builds. May not work for all environments though.
Anyone seen this error with IPU TS? Happened during TS after Upgrade OS step completed. "Task Sequence Manager could not initialize Task Sequence Environment. code 80040154" Points to something with WMI maybe, but client was working fine before.
#MEMCM#ConfigMgr#SCCM
@0daydorpher @AdamGrossTX This. It has been a while since I've looked at it but in past versions it creates a local docker-users group the user must be in. Also there is one user right (forget) that group must have if you have hardened security in place.