@[email protected]

IT Systems Admin/Engineer with a Microsoft focus: ConfigMgr, PowerShell, MDT, OSD, App packaging. Formerly in Oil & Gas, currently in Healthcare.

[@[email protected] @kevmjohnston]

@getwired "You're holding it wrong"

[@[email protected] @kevmjohnston]

@miketerrill It's been a perfectly fine strategy...until now. Only one site and client update per year to what is a very stable release by the time the HFRU comes out. Made more sense when there were 3x updates per year instead of 2 though, sure

[@[email protected] @kevmjohnston]

@teroalhonen @mniehaus @maryjofoley Is that the same as the AppID value you get when running Get-StartApps?

[@[email protected] @kevmjohnston]

@armcannon

[@[email protected] @kevmjohnston]

@znackattack @UmairMSFT There are individual hotfixes for CMG and client software update related issues. Beyond that, I don’t know. But for me it’s more a matter of my org doesn’t update to a version until the HFRU is out.

[@[email protected] @kevmjohnston]

@UmairMSFT @znackattack Any chance that a HFRU for 2403 is releasing this month?😊 Or maybe it will coincide with the announcement of 2409 next month?

[@[email protected] @kevmjohnston]

@Chris_Small_85 @PrajwalDesai @NicolaPanora One option is making a collection (assuming you are inventorying the necessary class). Attribute class: Windows app. Attribute: Application Name. Operator: is equal to. Value: MSTeams

[@[email protected] @kevmjohnston]

@cdnk3v @SeguraOSD @gwblok In my experience, the latest OSDBuilder release is able to service 23H2 successfully (even though it says that it only supports up to 22H2). It utilizes the update catalogs from the “OSD” module so I would make sure it’s on the latest version too.

[@[email protected] @kevmjohnston]

@IoanPopovici This reminded me of something I encountered a while back. Not sure if it’s relevant to what you’re seeing but figured I’d link it just in case it’s helpful: https://t.co/ANYxQRo5Fs

[@[email protected] @kevmjohnston]

@AdamGrossTX This seems to be related to having the "select when FUs are received" GPO set which is deprecated after 1809. This is causing CCM_OperatingSystem.OSBranch = 1 which translates to a NULL servicing state scenario. Remove GPO and OSBranch returns to 0 which fixes dashboard state 🤔

[@[email protected] @kevmjohnston]

@ccmexec @sassan_f This is great, thanks! One thing I noticed is that there are references to Install-NewTeams.ps1, but the actual file is named Install-MSTeams.ps1, so if you copy/paste like I did, make sure you're calling the right one or you'll end up with weird stuff in AppEnforce.log 😁

[@[email protected] @kevmjohnston]

@WindowsDocs When you build such a powerful PC that you attract the Borg and get assimilated

[@[email protected] @kevmjohnston]

@chukdotcom Somebody on a different IT team who probably should have their workstation admin privileges taken away 😏

[@[email protected] @kevmjohnston]

I guess the #ConfigMgr client doesn't like it when the network adapter name has an apostrophe in it?...cause I just fixed a client that wasn't able to determine boundary group membership (and couldn't download content) by renaming the adapter and removing the apostrophe 🤯

[@[email protected] @kevmjohnston]

@Hotzenwalder @miketerrill @bytenerd @sudhagart @AdamGrossTX It seems that all of these (undocumented?) registry settings may need to be configured to prevent the new behavior, but I haven't tested thoroughly.

[@[email protected] @kevmjohnston]

There must also be someone whose bonus is directly tied to how many people have the Windows taskbar search box enabled...

[MattWreede @MattWreede]

@MEM_MVP Someone's bonus is directly tied to how many people buy stuff through Edge shopping, so "no" :P

[@[email protected] @kevmjohnston]

@TheFrankUK @bdam555 In the meantime, compliance settings to the rescue!

[@[email protected] @kevmjohnston]

@abetterpc Well that’s not good… I installed it about a week ago immediately after updating to 2303. I haven’t noticed the issues mentioned in the doc, or any other issues yet though. Hopefully the fix to the “fix” will be server-side components only and not another client update 😩

[@[email protected] @kevmjohnston]

@PotentEngineer @mike_marable So I think what can happen is that a user signing into apps with the Azure account will trigger the machine to switch over from KMS to subscription based activation. But if that user doesn't regularly use that machine, it can fail to renew Ent and fail back to Pro only

[@[email protected] @kevmjohnston]

@PotentEngineer @mike_marable We have domain A and B. Users log on to Windows with A which is not tied to Azure. Azure entitlements are assigned to account in B. User uses B account to sign in to M365 Apps, Teams, OneDrive, etc.