Forum Widgets
Latest Discussions
Exchange Management Shell 2019
Hi All, We have a 4-node Exchange 2019 hybrid environment. On one of the nodes, we've noticed that connecting to the Exchange Management Shell takes an unusually long time, despite normal CPU utilization and all other services running smoothly. Has anyone experienced a similar issue or have any insights on potential causes and solutions?
User is unable to login to Mailbox
Hello experts, We are in Hybrid environment and one of the user which was recently re-enabled an AD account as the user is returned back to us, is unable to login to mailbox Steps we done Re-enabled the AD account and moved it to syncing OU and added license to enable mailbox I checked the recipient details in both on-prem and online On-prem results RecipientType : MailUser RecipientTypeDetails : RemoteUserMailbox Online results RecipientType : UserMailbox RecipientTypeDetails : UserMailbox What is the part that is missing here.
OOF to personal emails dropped at EOP relay
Issue: When an OutOfOffice recipient is gmail.com, outlook.com, msn.com ,etc, relay is dropped by EOP. Oof is delivered when recipient is an M365 tenant. Any other mail flows no issues to gmail and other personal addresses as well. It's only OOF to personal addresses. Env: Exch 2016 with EOP send/receive (hybrid manually, not hcw) We found 2 blog posts might be relevant, but these instructions did not resolve: https://techcommunity.microsoft.com/blog/Exchange/updated-requirements-for-smtp-relay-through-exchange-online/3851357 https://techcommunity.microsoft.com/blog/exchange/enhanced-filtering-for-connectors---improving-deliverability-and-minimizing-fals/4160483 This is what we see on the smtp protocol log: >,MAIL FROM:<> SIZE=7072, >,RCPT TO:<****@gmail.com> NOTIFY=NEVER, <,250 2.1.0 Sender OK, <,550 5.7.64 TenantAttribution; Relay Access Denied [*****.eurprd03.prod.outlook.com 2025-01-04T14:03:21.934Z *****], >,QUIT, ### We also looked into dkim, but finally found this line: By design, Exchange Online Protection uses the high risk delivery pool (HRDP) to send OOF replies, because OOF replies are lower-priority messages. https://learn.microsoft.com/en-us/exchange/troubleshoot/email-delivery/understand-troubleshoot-oof-replies#what-are-out-of-office-replies We feel this is not likely a connector or ceritifcate or onprem issue, rather something with HRDP and OOF in EOP. Could you confirm we are on the right track now? If not the Exchange Team can help please let me know who. Thanks
Outlook Android App error occurred during authentication. Please try again later.
Hi, I am migrating mailboxes between on-premises Exchange forests using ADMT automated calls in SC Orchestrator 2019. 1-Prepare-MoveRequest; 2-Migrate-ADMTUser; 3-MoveMailbox; 4-Set-Resources; Problem: Outlook mobile app using ActiveSync does not configure the same account after the mailbox is migrated from the source forest to the target forest with the email address in the "Username" field. Only using DOMAIN\Login or NETBIOS\SamAccountName. This happens with some accounts, but there are cases where it does not happen, even though the migration method is the same for all cases. Error message in the app: Outlook Android App error occurred during authentication. Please try again later. Workaround to configure post-migrated accounts: Email address: login@domain Password: User's forest password Server: FQDN of the NEW on-premises Exchange server Domain: Empty User Name: DOMAIN\SamAccountName PS: I can connect normally with 'Email - Fast & Secure Mail' and 'Gmail App ActiveSync'. This problem doesn't occur, and I can use the email address in the Username field." Troubleshooting performed: Enabled ActiveSync Logging: Set-CASMailbox -Identity "login@domain" -ActiveSyncDebugLogging:$true Get-Mailbox login@domain | Set-User -LinkedMasterAccount $Null Set-CASMailbox login@domain -ActiveSyncBlockedDeviceIDs $null Compared all attributes in Active Directory of an account with issues with another that does not have this problem; Compared all attributes in Exchange Server of an account with issues with another that does not have this problem; Both Exchange Server 2019 in the source and target forest with the latest CU14 and SUv2 from November. The Outlook Android App Support is very very complicated. It practically doesn't exist because no one ever responds.
CBA setup for ActiveSync on Exchange server 2019 on premise
I was setting up CBA for active sync and owa on exchange on premise 2019 following this guidehttps://learn.microsoft.com/en-us/exchange/plan-and-deploy/post-installation-tasks/configure-certificate-based-auth?view=exchserver-2019 It was a struggle. First, I tried to make sure OWA would work on a domain PCs with CBA. Finally, after I did optional step from the guide above, increased uploadReadAheadSize value to 49152 for owa, ecp and activesync, I started getting error on browser “too many redirects, try clearing cookies”. Clearing cookies didn’t help (private windows also didn’t help), but then I installed another browser (chrome), and owa started working accepting certificates. The browser that I was experimenting with before (edge) still not working for owa, I guess something needs to be cleaned. I understand it is not specifically edge problem, but the fact that edge has cashed some data (since I did all testings on it) that doesn’t allow to connect. I was able to connect to owa with edge on another domain computer, which was not used before. After I got owa to work on PC, I installed user certificate on iphone, and owa works there with certificate too (great!! one problem solved). However, for some reason active sync still doesn’t work with client certificate set to required on the same iphone. I assume iphone should use same certificate it uses for owa (which works), so certificate is not the problem. Without requiring client certificate ActiveSync on iphone also works, so permissions/policies shouldn’t be the problem. I’m getting error codes 403 7 64 and 403 7 5. Does anybody have any suggestions???How to Configure CBA for ActiveSync on exchange 2019 on premise??
Hi all, I was setting up CBA for active sync and owa on exchange on premise 2019 following this guidehttps://learn.microsoft.com/en-us/exchange/plan-and-deploy/post-installation-tasks/configure-certificate-based-auth?view=exchserver-2019 It was a struggle, but after I increased uploadReadAheadSize value to 49152 for owa, ecp and activesync, I started getting error on browser “too many redirects, try clearing cookies”. Clearing cookies didn’t help (private windows also didn’t help), but then I installed another browser (chrome), and owa started working accepting certificates. The browser that I was experimenting with before (edge) still not working for owa, I guess something needs to be cleaned. I understand it is not specifically edge problem, but the fact that edge has cashed some data (since I did all testings on it) that doesn’t allow to connect. I was able to connect to owa with edge on another computer, which was not used before. After I got owa to work on PC, I installed user certificate on iphone, and owa works there with certificate too (great!! one problem solved). However, for some reason active sync still doesn’t work with certificate required on the same iphone. I assume iphone should use same certificate it uses for owa (which works), so certificate is not the problem. Without requiring client certificate it also works, so permissions/policies shouldn’t be the problem. I’m getting error codes 403 7 64 and 403 7 5. Does anybody have any suggestions???
