Hybrid

We're not having much luck at all with our AB2s since changing workstations over summer. We're now getting constant BSODs. We've tried a multitude of combinations that used to work no problem at all. - Newer USB to serials - Direct USB - 5.18.16, 5.18.19, 5.7.25 you name it, they're now all producing BSODs. We're trying to explain to staff that we are trying to get decades old hardware to work with newer hardware. It's never going to be pretty.

PM sent - very interested in this as we have the same issue now.

Wondering about this too. It would seem the game Minesweeper is coming back into fashion again but it's baked straight into google.com

Interesting way of doing it! I was under the impression that if OneDrive detects a folder direction (to anywhere, by any means), it simply halts the process of KFM. Is that not what you've found doing it that way? Or are you removing the GPO you've created for that purpose so OneDrive *thinks* it isn't being redirected, but actually is?

That is indeed what we used to do - however with the advent of OneDrive, you cannot use Folder Redirection and use KFM together.

Not that I'm afraid. Soon as I put the entry in, it simplifies the name back to %userprofile%\Desktop again.

We're trying to reduce the rubbish people store on their desktops ideally - some users' have unsightly desktops, littered with files that makes it 30x harder to find files from. Leaving it to sync with OneDrive will end up being our fall-back and just 'advise' people not to save to their desktops.

Doesn't look like it's that. I can see the file I've created in the user's local desktop directory. The issue is, it looks like my permissions (probably the way I have them setup) aren't taking effect... or just none effective because of another group permission maybe taking control?! If I look at the file on the local C drive, the permissions appear to be inherited (by design), but I'd just assume the GPO file system change I've made would overwrite that? It will be something obvious I'm missing or haven't changed.

I haven't. I'd just assume that because they are all using their own individual desktops it wouldn't be writing to the shared desktop folder?

Morning all, Hope you are all well? Before I pull any more hair out that I cannot afford to lose, does anyone have a solution that works to prevent users from saving the desktop? Background: - We use OneDrive with KFM enabled - so we can't/aren't redirecting folders - otherwise I would have just redirected them to a read-only share - Setup using local profiles - so desktops are all %userprofile%\desktop I have tried to add a file system GPO rule in to prevent WRITE access to the folder in question, but it doesn't seem to take effect, despite gpresult saying it was applied. What am I missing?? Open to ideas and suggestions. Cheers

For that, I think I'd be just disabling MFA for the user and recreating it again. Get them to check their MS account too. https://account.microsoft.com/security

Just in case anyone was having this issue, MS released a statement and 'fix'. https://admin.microsoft.com/AdminPortal/Home?ref=MessageCenter/:/messages/MC257668 Message Summary Problem detected: Some users on Windows version 19H2 may be unable to connect to desktop clients for some Microsoft 365 services, including Microsoft Teams, Outlook, and OneDrive for Business. As described in Service Health Dashboard post MO257074, we’ve detected a problem related to some Windows clients running version 19H2, and specifically the update delivered via KB 5003169. We are sending you this communication because we’ve determined that your organization has some users running Windows version 19H2 and if they have taken the update they may have issues connecting to one or more Microsoft 365 services. The following communication provides instructions on how to correct the problem for any affected users. How this will affect your organization: Users affected by this problem are potentially unable to connect to Microsoft 365 services including Microsoft Teams, Outlook and OneDrive for Business. When encountering this problem, users may see the following errors: "We're sorry – we've run into an issue," or “80080300” when attempting to connect or sign in. What action do I need to take: To fix this problem for users that are reporting this issue on devices that have already installed Windows Update KB 5003169, we’ve confirmed that an additional device reboot will resolve the problem. For users on Virtual Desktop Interface (VDI) clients, we have confirmed that a reboot of the underlying VDI host may also be required. For users on devices which have yet to install Windows Update KB 5003169, those devices will require an additional reboot after the final automated Windows Update restart, and any hosts of VDI instances should also be rebooted as part of this process. We recommend incorporating these steps into your update process as you adopt Windows Update KB 5003169.

Are your machines registering as normal on Azure AD now, Chris? We found that a simple restart of the PC kicked the whole thing into play again and it started working as expected. Obviously not a concrete fix, but it gets them back on again.

I'm diving deeper into this now. Looks like the machines/users that I'm having the issues with aren't hybrid domain joining any more. Event viewer spits out: Device is not cloud domain joined: 0xC00484B2 AAD Cloud AP plugin call Plugin initialize returned error: 0xC00484B2

Heck! Do you know when this notification was released at all? I can't seem to see a date stamp.