Power Shell/Exchange Management
In certain Microsoft Exchange environments (primarily Office 365), a restriction is placed on XenMobile Mail Manager that effectively limits bandwidth, preventing an app from issuing any PowerShell requests or commands. You can now use an alternate PowerShell cmdlet pathway in the Exchange configuration tab, which puts XenMobile Mail Manager into an alternate snapshot mode; this mode bypasses the original data path.
A new flag enables you to expose the AllowRedirection flag for non-Microsoft Office 365 environments. Use the Microsoft Exchange configuration tab to enable this flag.
LDAP local rules now support an indiscriminate number of groups for large Active Directory environments.
XenMobile duplicates device information for WorxMail clients. Resolving this issue requires that you enable regular expression support in the Managed Service Provider (MSP) portion of XenMobile Mail Manager; doing so filters the record sets returned to XenMobile. Devices matching the filter are not returned to XenMobile.
Users who are removed from the Blackberry Enterprise Server (BES) database are now removed from the local database.
You can now use a progress dialog class for scenarios in which a persistent process takes place. In such a process, XenMobile Mail Manager sends users feedback and provides them with an opportunity to cancel where applicable.
The default value for new Microsoft Exchange instances is now set to Shallow.
Components referring to Zenprise have been changed to reflect XenMobile Mail Manager.
The installer hangs when it fails to find the installation path.
Support binaries and scripts now reside in the Support folder after installation.
In the Windows Start menu, XenMobile Mail Manager shortcuts now reside in the \Citrix\XenMobile Mail Manager folder.
The Support model provides the ability to enable troubleshooting functionality through the addition of a config.xml file. You can use this file to help Citrix troubleshoot problems. At this release of XenMobile Mail Manager, this functionality only applies to the Microsoft Exchange configuration Add
Note: You can also enable this troubleshooting functionality by holding the Shift key when opening the Configure utility.
Error messages returned from PowerShell now have a GUID associated with them. Use this value to control what appears in the Snapshot History detail tab.