Showing posts with label MobilePhone(s). Show all posts
Showing posts with label MobilePhone(s). Show all posts

Exchange 2013 EAS probe (health monitoring)

If you are deploying Exchange 2013 you might be aware that Microsoft is using all it's knowledge to build a "self healing" product. You can read more about it here: LINK.

One monitor is EAS (ActiveSync) and if you require all EAS devices to be compliant (on the Default EAS policy) you might get a warning in the event log:
A non-compliant phone is trying to connect with Exchange ActiveSync. However, the Exchange ActiveSync mailbox policy for user [DOMAIN\SM_GUID] and device ID [EASProbeDeviceId141] requires phones to be compliant before they synchronize with Exchange ActiveSync.
Solution

  1.  Logon to ECP website (Exchange Admin Center)
  2. Go to Mobile
  3. Click on the + under "Device Access Rules"
  4. Create a rule for "EASProbeDeviceType" and "Allow access"

Remove corrupt ActiveSync device from Exchange 2010 using MFCMapi

Corrupt ActiveSync device
Sometimes you can get a corrupt ActiveSync device in a Exchange 2010 mailbox.

  • You can see the device in OWA under options > Phone > Mobile phones. 
  • When you try to do anything with the device (Details or Wipe) you will get an error message. 
  • If you in Powershell try to get the ActiveSyncDevices (Get-ActiveSyncDevice -mailbox mailbox_id) you will not see the corrupted device. 
Why is this happening
When a user sets up a ActiveSync relationship the information is stored in two places (AFAIK);

  1. Hidden folders in the user mailbox
  2. AD as child items to the user account

How to fix
This fix deletes the corrupted ActiveSync device that is visible from OWA so a new partnership can be established (or just to remove an orphan device from the list):

  1. Download MFCMapi
  2. Create a MAPI Profile to the users mailbox on a server/workstation with Outlook
    You might as a administrator add [Full Access] permissions to the mailbox that you are going to fix (remember to remove the permissions after the routine is finished)
  3. Start MFCMapi 
  4. Menu Session > Logon [choose the correct Outlook Profile]
  5. Double click the "Mailbox - User name"
  6. Expand the "Root Container"
  7. Expand the "ExchangeSyncData"
  8. Locate the corrupt device (a folder under ExchangeSyncData) and right click > Delete Folder
    [I recommend a hard delete]
  9. Close MFCMapi


Links

Problems updating apps placed on SD card on Andriod phones

I have had problems updating my apps on Andoid that are stored on the SD Card. Google Play informs me with the following:
Installation error... Couldn't install on USB storage or SD card
A tip from the following page helped me getting updates installed correctly:

  1. Mount the Andriod phone as a hard disk on a computer
  2. Navigate to the /sdcard/.andriod_secure folder (on SD card)
  3. Delete the file "smdl2temp1.asec file
Disclaimer
I have no clue of what the file is used for and if this can damage the Andriod installation on your phone. However it solved me problems (and other according to forums on the Internet) with installing updates to apps moved to the SD card.


Links