Exchange Team Blog

You Had Me at EHLO..

Options
1,782
The_Exchange_Team on Dec 05 2022 07:33 AM
4,476
The_Exchange_Team on Dec 01 2022 02:58 PM
4,090
The_Exchange_Team on Nov 23 2022 07:16 AM
19.2K
The_Exchange_Team on Nov 16 2022 01:40 PM
9,049
The_Exchange_Team on Nov 15 2022 12:03 PM
66.5K
The_Exchange_Team on Nov 08 2022 10:00 AM
11.9K
The_Exchange_Team on Nov 03 2022 08:43 AM
17.4K
The_Exchange_Team on Nov 01 2022 03:43 PM
9,018
The_Exchange_Team on Oct 13 2022 06:48 AM
54.3K
The_Exchange_Team on Oct 11 2022 10:02 AM
15.8K
The_Exchange_Team on Oct 03 2022 02:19 PM
124K
The_Exchange_Team on Oct 01 2022 07:30 AM
83K
The_Exchange_Team on Sep 30 2022 12:06 AM
11.1K
The_Exchange_Team on Sep 27 2022 07:09 AM
15.9K
The_Exchange_Team on Sep 20 2022 06:56 AM
8,300
The_Exchange_Team on Sep 16 2022 10:45 AM
11.3K
The_Exchange_Team on Sep 15 2022 03:23 PM
8,263
The_Exchange_Team on Sep 09 2022 08:40 AM
5,322
Scott Schnoll on Sep 07 2022 09:53 AM
724K
The_Exchange_Team on Sep 01 2022 08:00 AM
13.1K
The_Exchange_Team on Aug 31 2022 07:33 AM
6,298
The_Exchange_Team on Aug 30 2022 07:50 AM
6,266
The_Exchange_Team on Aug 29 2022 08:57 AM
17.8K
The_Exchange_Team on Aug 22 2022 08:54 AM
6,042
The_Exchange_Team on Aug 11 2022 12:48 PM
133K
The_Exchange_Team on Aug 09 2022 10:04 AM
28.4K
The_Exchange_Team on Jun 30 2022 11:04 AM
13.5K
Scott Schnoll on Jun 24 2022 02:03 PM
63K
The_Exchange_Team on Jun 16 2022 08:00 AM
12.8K
The_Exchange_Team on Jun 06 2022 01:58 PM

Latest Comments

The frustrating thing about this situation is that Microsoft was repeatedly told this was going to cause problems, and blindly forged ahead anyway, ignoring all concerns. Now the exact scenario we predicted would happen has happened, and MS team seems to be surprised. It's really frustrating to have...
0 Likes
Thanks @AdityaMukund and I wish that I didn't have to say this, but it would have helped if @The_Exchange_Team would have listened to us when we all tried to stress the problems that this was going to create. I now have multiple users who are seeing GUID's instead of (new hire) Names. And they don't...
3 Likes
Hi @KevinGodfrey Could you please share why the current workaround of piping is not helpful?
0 Likes
It's good to see reply from @AdityaMukund that you are looking at impact on EAC and remediating that.@The_Exchange_Team Are you reviewing Exchange Powershell cmdlets to improve output from those that return only name.i.e. get-recipientpermission (we're now having to pipe the trustees into get-recipi...
2 Likes
Hello @Eriq VanBibber sorry for taking some time to reply to you as I have to validate such information with our engineering team. Answering your question in 2 parts -> consider the scenario that you have 200 PF MBXs where 100 PF MBX are hierarchy serving mailboxes while the other 100 are content ba...
0 Likes