FSLogix Problem with Microsoft.AADPluginBroker
We have a few on prem windows 2022 RDS farms using fslogix and outlook. We are bashing our heads against the wall because of the this 58tm1 problem. Every once in a while (5 times a day) a user will get a 58tm1 error while trying to open outlook, we usually fix the problem by deleting the Microsoft.AAD.BrokerPlugin which would fix things for a short while, because we've tried everything else out there, nothing works. Every possible settings combination, registry fixes etc... Newest fslogix versions (hello 25.09) do not fix anything but break everything (this entire branch has a nasty bug which would create temporary profiles and fill every storage space available). Let me know any possiblity to fix this =)
BitLocker Network Unlock Question
I set up network unlock for two servers in our network as a test for a future deployment of BitLocker. Both HP's. One is a DL 360 Gen9 server with aftermarket TPM, the other is a DL360 Gen11 with onboard/HP TPM. Configured first NIC on both boxes for DHCP. Just to test things, I unplugged NIC1 but kept NIC2 plugged in on the Gen11 server and rebooted. It prompted for a PIN on boot up (expected behavior). Did the same test on the Gen9 server and it boots straight into the OS (unexpected behavior). As a further test, I kept NIC1 unplugged and then unplugged NIC2, rebooted and got prompted for a PIN (as expected since box was completely off network). Does anyone have any ideas why this is happening? Could it have something to do with the aftermarket TPM? From what I've read network unlock requires the first NIC to be DHCP so it can communicate with the WDS server and allow network unlock to work. Could it be something with the NIC's on the Gen9 server? I'm at a loss to explain this behavior. Hoping someone may have some insight. TIATPM Warning Message during Device Wipe
Dear all, When we initiate Intune device wipe (not Autopilot reset) on the Dell PC, it prompts a TPM clear message on the reboot. Usually we will just hit F12 to proceed with the device wipe and Autopilot. However, sometimes we need a fully unattended workflow for our Kiosk PC setup. This prompt is preventing us to achieve a 100% zero touch experience. Is there a way to fix this via Intune? Thanks,
