Running in to an issue after an Exchange ActiveSync device is removed using the Remove-ActiveSyncDevice PowerShell command. 

We successfully removed over 1200 out-of-date devices from Exchange ActiveSync. 

After removing all devices, the issue is with 160 mobile devices that are reporting back to as what Im referring to as unassigned. 

The user is still able to send and receive emails from their mobile device, but the device does not show up in the EMC or ADSI under the user.  When exporting ALL_Domains using the Get-ActiveSyncDevice without specifying the -DomainController the UserDisplayName is empty and the DistinguishedName is showing the same as ADSI Configuration Naming path listed below.

With 1 test user, we removed the Exchange account from the mobile device, rebooted the device and then added the Exchange account back to the mobile device.  Now the device shows up under ADSI assigned to the user, but not in the EMC.

When changing ADSI to Configuration Naming Context for the parent domain, the unassigned mobile devices are reporting back to

CN=<***device name***>,CN=ExchangeDeviceClasses,CN=Mobile Mailbox Settings,CN=<*******>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<*******>,DC=net

Ran the following commands

• Set-ADServerSettings -ViewEntireForest $true
• Exported the Get-ActiveSyncDevice for each of our domains, 1 parent and 3 child domains
  • Get-ActiveSyncDevice domaincontroller dc.child.parent.net | export-csv .\child_Domain_vDate_Time.csv
• Remove-ActiveSyncDevice -Identity <GUID ********> -confirm:$False
• Get-ActiveSyncDevice | export-csv .\ALL_Domains_vDate_Time.csv
  • This command without specifying the Domain Controller is reporting back the empty UserDisplayName

Server OS 2008 R2 Enterprise with SP1

Exchange Exchange 2010 Enterprise SP2

• Moved by Jason Johnston [MSFT]Microsoft employee Tuesday, June 23, 2015 6:54 PM Not a development question.

Hi hrcafe,

There is no question in your post, you know? :)

It's obvious from your description that your DCs have a large gap or delay in synchronization. All your tools (EAC, EMS, ADSIedit, etc) can address requests to different domain controllers - and that's why you see different results. I believe Exchange services work ok in this case and you should dig into AD replication area.

At least it's worth trying "repadmin /syncall" with controlling results after each removal operation.