I assume you are using PowerShell integration with O365? If so, here is what you can do:
Step 1: Search for the device in your AirWatch console under ' Email > List view' and check if it appears as ' Blocked' . If so, select it and click ' Actions > Default' . Give it a minute or two and try to sync email. If this does not work, note the EAS ID of the device and proceed to Step 2.
Step 2: Launch PowerShell, connect to your Exchange server (or O365 environment) and look for the device based on the email address of the user it has been enrolled for using the following command replacing #email# with the user's email address:
Get-CasMailbox #email# | FL
Check if the ActiveSyncEnabled field is set to True, if it is, proceed to Step 3. If not, issue the following command replacing #email# with the user's email address:
Set-CASMailbox -Identity #email# -ActiveSyncEnabled $true
Give it a minute or two and try to sync email. If this does not work, proceed to Step 3.
Step 3: Look for the ' ActiveSyncAllowedDeviceIDs' and ' ActiveSyncBlockedDeviceIDs' fields in the result of the ' Get-CasMailbox #email# | FL' command. If you find the device's EAS ID in the ' ActiveSyncAllowedDeviceIDs' field then that's a good first indication. If not, it needs to be added manually by issuing the following command replacing #email# with the user's email address and #device id# with the device's EAS ID:
Set-CASMailbox #email# -ActiveSyncAllowedDeviceIDs @{Add = ' #device id#' }
If the device's EAS ID also appears in the ' ActiveSyncBlockedDeviceIDs' field then you need to remove it by issuing the following command replacing #email# with the user's email address and #device id# with the device's EAS ID:
Set-CASMailbox #email# -ActiveSyncAllowedDeviceIDs @{Remove = ' #device id#' }
I wrote the above by heart so I hope I did not make any mistakes. Let me know if it helped.
Kind regards
Konstantinos
Hey John. Not listed as Blocked is a good thing but unless it is listed as Allowed in PowerShell, it won't sync. It is not uncommon to have a discrepancy between what you see in the AirWatch console and in PowerShell. Give it a shot and let us know how it goes 🙂
Kind regards
Konstantinos