User Profile
ajc196
Iron Contributor
Joined Feb 17, 2019
User Widgets
Recent Discussions
Does Rights Management Service currently support MFA claims from EAM?
We've been testing EAM (external authentication methods) for a few months now as we try to move our Duo configuration away from CA custom controls. I noticed today that when my Outlook (classic) client would not correctly authenticate to Rights Management Service to decrypt OME-protected emails from another org. It tries to open the message, fails to connect to RMS, and opens a copy of the email with the "click here to read the message" spiel. It then throws a "something is wrong with your account" warning in the Outlook client's top right corner. If I try to manually authenticate & let it redirect to Duo's EAM endpoint, it simply fails with an HTTP 400 error. When you close that error, it then presents another error of "No Network Connection. Please check your network settings and try again. [2603]". I can close/reopen Outlook and that warning message in the top right stays suppresses unless I attempt signing into RMS all over again. However.. If I do the same thing and instead use an alternate MFA method (MS Authenticator, for example), it signs in perfectly fine and will decrypt those OME-protected emails on the fly in the Outlook client, as expected. I verified that we excluded "aadrm.com" from SSL inspection and that we're not breaking certificate pinning. So all I can assume at the moment is that Rights Management Service isn't honoring MFA claims from EAM. Any experience/thoughts on this? Thanks in advance!Re: Email Signatures vanishing - New Outlook
I've had a flurry of reports that the "Add new signature" button was missing as of today in New Outlook. I pulled up a VM of mine, and it looked fine at first. Then I was prompted to restart the app for an update. Once it came back, my "Add new signature" button was ALSO gone. It was present before the app update occurred moments prior. Affected version seems to be 1.2025.522.100. The signatures themselves remain, though. Is this a bug or new behavior? Because there is nothing talking about this in New Outlook changelogs or M365 message center that I can see.3.2KViews0likes0CommentsRe: New Teams client suddenly not allowing specific characters from M365 Group naming policy
We're well into February with no fix, and there's still never been an advisory or incident in the M365 message center for this. So I'm a little dubious about the statement of Microsoft's awareness higher up in this thread.2KViews0likes1CommentRe: New Teams client suddenly not allowing specific characters from M365 Group naming policy
Still an issue. Respectfully, Microsoft needs to expedite this fix. Because right now, we have to do one of the following: 1) Undo our M365 Group naming policy and blow up expected logic for way more M365 services than just Teams. 2) Leave users unable to create teams in Teams, and hope they reach out to us. Since we are a university with a user count in the 5-figures, this is a very bad option.3.2KViews2likes0CommentsRe: New Teams client suddenly not allowing specific characters from M365 Group naming policy
No one else seeing this? Still very reproducible for us, and there's no mention of parentheses not being supported in a Group naming policy so far as Teams is concerned. https://learn.microsoft.com/en-us/microsoft-365/solutions/groups-naming-policy?view=o365-worldwide#things-to-look-out-for5.4KViews0likes0CommentsNew Teams client suddenly not allowing specific characters from M365 Group naming policy
Since we deployed Teams a few years ago, we have had an M365 Group naming policy that appends " (UserCreated)" as a suffix for anything created by an end user/non-admin. There have been no changes since. Starting a few days ago, we got reports that users were getting an error of The team prefix or suffix is incorrect, please try again whenever creating a new team. After testing myself and reproducing the problem what I found is that if you're using the v2 client ("new" Teams on Windows/macOS, or https://teams.microsoft.com/v2 for the web client), it kicks back with the above error. If using a classic/v1 desktop client or the non-updated web client, the issue is not reproducible. v2 client + no parentheses in naming policy = SUCCESS - https://imgur.com/a/fun0klN v2 client + parentheses in naming policy = FAILURE - https://imgur.com/a/ZeADI6E v1 client + parentheses in naming policy = SUCCESS - https://imgur.com/a/jYae7l8 Currently unaware if this is a bug or new behavior that went unannounced, but there's at least a few other recent complaints of the same out in the community. https://answers.microsoft.com/en-us/msteams/forum/all/naming-teams/ebb29b25-20df-4642-8fcf-ffc67896e9f56.2KViews4likes13CommentsMassive Outlook issues since Monday: Not opening at all, freezing after 5 minutes, losing connection
EDIT: Finally got a client where the issue was constantly reproducible enough to get a Wireshark and ProcMon capture. Immediately noticed that while Outlook was in the middle of it's "not opening" phase, there were a **ton** of retransmits over IPv6 to Microsoft endpoints. For one example, 2603:1036:305:48ca::2 in Texas, which is our Exchange Online front door. Error on the event was "destination unreachable (no route to destination)". Disabled IPv6 on the network adapter and their Outlook issues **immediately** went away. I think somewhere there is a bad IPv6 routing issue. ********** Since the beginning of this Monday, we've seen a pretty massive uptick in our environment of complaints about Outlook (another some other pieces of M365 Apps like Word, Excel, Teams) having issues. We are in Southeast US. For us, the most prevalent symptoms include: * Outlook not opening at all * Outlook freezing (going "not responding") after 5 minutes of usage * Outlook will random lose connectivity and throw a red exclamation mark onto the taskbar icon * Outlook not syncing messages until 20-30 minutes after the mailbox receives them These issues persists across a reboot. We've already employed all manners of usual fix attempts (new profiles, clearing caches, etc) to no avail. The issue is reproducible when our EDR (Cisco Secure endpoint) is removed from a client. (First thing I suspected since this and other security clients broke Chrome from opening correctly starting last week) Uninstalling the June 2023 Windows cumulative update does not affect the issue, and having M365 Apps on Current Channel or Monthly Enterprise Channel makes no difference for the symptoms. Microsoft doesn't seem to be acknowledging any issues, and many of us are just plain stuck with royally pissed off users. This includes a few folks on Reddit that have been reporting this exact same thing since Monday as well: https://old.reddit.com/r/Office365/comments/14f6g28/is_something_down https://old.reddit.com/r/sysadmin/comments/14exlr6/office_issue https://old.reddit.com/r/Office365/comments/14fbmrd/help_365_app_woes Anyone else seeing this? I'm losing my mind here because we just get more and more reports with no end in sight...3.6KViews0likes0CommentsRe: Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
KB5010427 for Server 2019 back in February fixed the issue in our environment and it has not recurred, at least not to my knowledge. Only extra thing we had to do was re-activate our 2022 host key after installing the patch.3.9KViews1like9CommentsRe: Server 2022 WSUS shows Windows 11 clients as Windows 10
The bits for Win11 22H2 have been out for a while and it was never fixed there. So this will continue to be a problem for a while, unless Microsoft fixes it at random between feature updates. My suggestion would be to give up on Microsoft and just self-fix with AJTek WAM's custom OS description functionality.46KViews0likes4CommentsRe: Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
It's not just you, ours is doing the exact same thing. Issue was fixed after KB5010427 back in February, and I never looked back at it. Now that I see your comment, I tried activating a test Win10 10 Ent. LTSC 2019 VM, and nope. Failed to activate, back to square one all over again. Good God, Microsoft...6.3KViews0likes18CommentsGetting new Insider builds without undoing WSUS settings
I have a Windows 11 Education VM that I keep on the Insider Dev channel for testing things as soon as they come out. Because I want to see how Insider builds would look in our production environment, this VM stays in an AD DS OU with various GPOs applied, including one that points clients to our organization's WSUS host. (client-side targeting) The problem arises when a new Insider Dev build comes out. Obviously it's not going to come in from my WSUS server since we don't sync any Insider categories, but the "Check Online for Updates from Microsoft Update" button which should be bypassing WSUS, never pulls any new Insider builds. I always have to do one of the following: A) Move my VM out of its OU to get it out of the scope of my GPO that sets our WSUS settings. Then it pulls Insider builds just fine. B) Update via ISO. Which is not ideal , because ISO releases greatly lag behind actual release dates of Insider builds. Option A only takes a couple seconds and is easy enough, but I was curious if there's any relevant registry settings that will simply let the OS find new Insider builds when clicking "Check Online for Updates from Microsoft Update" without undoing the client-side WSUS config?641Views0likes0CommentsRe: Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
Just installed KB5010427 on our KMS host (Server 2019) and re-inserted our 2022 host key. We are now back to normal. 2016 LTSB, LTSC 2019, and LTSC 2021 are all activating fine. The few Server 2022 clients I had to put on MAK keys, I put back on KMS and they activated fine as well. On one hand I'm happy this is fixed; On the other hand, this has been an ongoing bug since August. Seems like it was not highly prioritized, and we never did get a pre-release workaround/fix last year as offered by Premier. 😕7.2KViews2likes1CommentRe: Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
I wonder if someone just jumped the gun for the changelog for the regular February updates. Since waaaay last year (this issue has been going on for months), Support had told me that the fix was coming in *late* February for Server 2019 hosts, which I interpreted to be the "C" release updates. i.e. not February's "B" releases on Patch Tuesday.7.1KViews0likes17CommentsRe: Teams Mobile App for Android Showing Unread Chats which is wrong
Might take a cache/data clearing and reinstall for this fix to actually apply, though. That appears to be the only thing post-update that finally made my mobile app keep track of read/hidden messages from the desktop apps. EDIT: Can also confirm I'm seeing meeting entries stick around as explained by Tushar.7.5KViews0likes0Comments
Recent Blog Articles
No content to show