Using iOS Build Numbers in Exchange ActiveSync Device Access Rules
A change made in late 2024 allows Microsoft 365 tenants to use IOS build numbers in Exchange ActiveSync device access rules. Apparently, the idea is that tenants can insist that people use iOS devices with very specific build numbers (like iOS 18.3.1 22D72) before the devices can synchronize with Exchange Online mailboxes. You never know when you might need the feature (or so they say). https://office365itpros.com/2025/03/06/device-access-rule-ios-build/
Automatic redirection of Exchange ActiveSync On-Pre
I am migrating mailboxes between on-premises Exchange forests using ADMT automated calls in SC Orchestrator 2019. Prepare-MoveRequest Migrate-ADMTUser MoveMailbox Set-Resources Has anyone already done the automatic redirection of Exchange ActiveSync in the following scenario: Moving mailboxes between on-premises Exchange organizations. I know the link below says it is not possible, but I would like to know if anyone has overcome this limitation? https://learn.microsoft.com/pt-br/exchange/activesync-settings
Exchange 2019 ActiveSync + Mobile Outlook App stop syncing
Good day! We have a local installation of Exchange 2019. Services are published through the IIS ARR reverse proxy. Everything works correctly, including OWA and the Outlook desktop client. But, at some point in time, some clients on mobile devices stop syncing. At the same time testconnectivity.microsoft.com shows that everything is ok. Manually, this problem is solved if all the user's mobile devices are deleted via the ecp. Then, at the next synchronization, everything starts working as it should. This affects only a part of the clients, the other part continues to work correctly. Clients with Gmail app on Android and native mailapp on iOS work without any problems.Recommended Clients for Exchange Activesync for Exchange 2019 Mailbox Users
In my environment, we have Exchange 2019 CU11. My understanding from when I spoke with Microsoft Exchange Engineers on the phone was that the Outlook mobile app was built primarily around for mailbox in Exchange Online (M365). While I know that Outlook mobile app does have Activesync in it, the Engineers told us that for Exchange On-Premises mailboxes, we should use the Native Mail, Calendar, and Contacts apps on Android and iOS because the Outlook mobile app wasn't meant for Exchange On-Premises. Would someone be able to confirm or give recommendations as to what is truly the way we should direct our customers to use when accessing On-Premises Exchange email on their mobile devices?
ActiveSync exception on Exchange 2016
I get this error on my event after restart IIS. I run this two command for resolve error but error is exist. `Get-Mailbox | Set-CasMailbox -ActiveSyncEnabled $False` `Get-Mailbox | Set-CasMailbox -ActiveSyncEnabled $True` Error: > Level Date and Time Source Event ID Task Category > Warning 1/3/2023 11:37:52 AM ASP.NET 4.0.30319.0 1309 Web Event "Event code: 3005 > Event message: An unhandled exception has occurred. > Event time: 1/3/2023 11:37:52 AM > Event time (UTC): 1/3/2023 8:07:52 AM > Event ID: 7c89094cd79849efb70201ca892246f8 > Event sequence: 3 > Event occurrence: 1 > Event detail code: 0 > > Application information: > Application domain: /LM/W3SVC/2/ROOT/Microsoft-Server-ActiveSync-1-133171417813586892 > Trust level: Full > Application Virtual Path: /Microsoft-Server-ActiveSync > Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\sync\ > Machine name: EX-MB-03 > > Process information: > Process ID: 17228 > Process name: w3wp.exe > Account name: NT AUTHORITY\SYSTEM > > Exception information: > Exception type: ThreadStateException > Exception message: Thread has not been started. > at System.Threading.Thread.JoinInternal(Int32 millisecondsTimeout) > at System.Threading.Thread.Join(TimeSpan timeout) > at Microsoft.Exchange.AirSync.Common.NotificationManager.ShutdownNotificationManagerTimerThread() > at Microsoft.Exchange.AirSyncHandler.Global.ExecuteApplicationEnd(Object sender, EventArgs e) > > > > Request information: > Request URL: > Request path: > User host address: > User: > Is authenticated: False > Authentication Type: > Thread account name: NT AUTHORITY\SYSTEM > > Thread information: > Thread ID: 114 > Thread account name: NT AUTHORITY\SYSTEM > Is impersonating: False > Stack trace: at System.Threading.Thread.JoinInternal(Int32 millisecondsTimeout) > at System.Threading.Thread.Join(TimeSpan timeout) > at Microsoft.Exchange.AirSync.Common.NotificationManager.ShutdownNotificationManagerTimerThread() > at Microsoft.Exchange.AirSyncHandler.Global.ExecuteApplicationEnd(Object sender, EventArgs e)
Do Not Send ActiveSync Quarantine Messages to End Users
Is it possible to completely drop or block these emails from being sent to end users? We are getting ready to implement a Quarantine for all devices policy and do not want these emails sent to end users since their ActiveSync allowed devices will be enabled by Workspace One integration. Your device is temporarily blocked from accessing content via Exchange ActiveSync because the device has been quarantined. You don't need to take any action. Content will automatically be downloaded as soon as access is granted by your administrator.Outlook Mobile - Sync
Good evening, I have two employees at the company who use the Outlook mobile app. When you submit a new address and search the search directory, it puts the initial letter of the email address, but it takes a long time to respond. Already tried everything, there is an option in Outlook that resets synchronization by performing this action back to normal. After a few hours, the problem occurs again.
