Exchange 2010 - Some Device Partnerships Do Not Exist

Posted on 2012-09-07
Medium Priority
Last Modified: 2012-09-11
Hello, Experts!  We have a single Exchange 2010 Server w/SP1.  We migrated from an Exchange 2003 SP2 Server a couple of months ago with a few bumps along the way but things are running pretty smoothly now.

I've been experimenting with PowerShell commands to list all users with a device partnership, but just noticed not all of them are appearing in the query and the Manage Mobile Phone option is not appearing for them in the EMC.

The one user I know of is using TouchDown on an Android phone because he just replied to one of my e-mails and he has it in his signature.  I do know that his device started syncing back on Exchange 2003 -- but so were the rest of us.  Plus, I have TouchDown on my Android phone and it's appearing in the lists.

I know that there are 3 methods of syncing in TouchDown: Exchange 2003, Exchange 2007 and ActiveSync ONLY.  Mine is set to ActiveSync ONLY.  I sent an e-mail asking which one he's using.  But even if he's using one of the other methods, does Exchange not create a Partnership for it?  Can there be any other hardware/software combinations that won't show up, either?

Any ideas of what might be going on?
Question by:wchestnut
  • 2
  • 2
LVL 63

Accepted Solution

Simon Butler (Sembee) earned 2000 total points
ID: 38378410
A partnership is only created in ActiveSync. The other methods I believe will be using OWA screenscraping, which will not create a partnership - they are designed for sites where ActiveSync hasn't been enabled.


Author Comment

ID: 38378488
So there's no way to identify -- and especially block/control those users?
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38379066
Not really.
The prducts are specifically designed to get round those "pesky admins" who don't want to allow users to access their email with a mobile device. The only way would be to turn off OWA completely.
You might find something in the web logs where the device identifies itself which you could use at an IIS level to block the product, but there is nothing to stop the developers of the product from changing that value so the block no longer works.


Author Closing Comment

ID: 38389293

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
If you have come across a situation where you need to find some EDB mailbox recovery techniques, then here you will find the same. In this article, we will take you through three techniques using which you will be able to perform EDB recovery. You …
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Course of the Month13 days, 19 hours left to enroll

807 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question