Resetting Exchange ActiveSync blocking solutions after uninstalling or changing the Symantec Management Platform infrastructure

Article:TECH197075  |  Created: 2012-09-21  |  Updated: 2012-09-28  |  Article URL http://www.symantec.com/docs/TECH197075
Article Type
Technical Solution

Issue



There may be cases where you need to reset or "cleanup" your F5 or Exchange 2010 servers after uninstalling or making changes to your Symantec Management Platform infrastructure.


Solution



To reset F5:

  1. In Mobile Management EAS settings, remove all F5 servers and disable the EAS blocking via F5 option.
    NOTE: On the confirmation dialog specify that you want all F5 configurations to be automatically deleted.
  2. Save the settings.
  3. In the CMDB, in the MobileManagementEASAccess table 'AccessVia’ column, delete all records (if any) with a value that is not equal to 'exchange'.
  4. In F5 verify that no objects (iRules & Data Groups) named smm_eas_XXXX are present. If present, remove them.

To reset Exchange:

  1. In Mobile Management EAS settings, disable EAS blocking via Exchange. Save the settings.
  2. In the CMDB, in the MobileManagementEASAccess table 'AccessVia’ column, delete all records (if any) with a value that is equal to 'exchange'.
  3. Using PowerShell script (or management console), reset the ActiveSyncAllowedDeviceIDs property on every CAS mailbox. For example, the PowerShell script to reset the property on all mailboxes could be:
Get-CASMailbox | Set-CASMailbox -ActiveSyncAllowedDeviceIDs $null

 Impact on Exchange by uninstalling Mobile Management

When you uninstall Symantec Mobile Management, any “allowed devices” will remain associated with their Exchange blocking solution, whether F5 or Exchange. Once Symantec Mobile Management is uninstalled, you must manage the "allowed devices" whitelist and any mobile device management activities either manually or with another solution.

 


Supplemental Materials

SourceETrack
Value2879446

SourceETrack
Value2828666


Article URL http://www.symantec.com/docs/TECH197075


Terms of use for this information are found in Legal Notices