When using Migration Manager for AD, the Exchange Processing Task may report a HTTP error 400 on CSDProcessor.ReadMailboxSDs when migrating certain mailbox permissions from one user account to another.
For mailboxes where the name contains an ampersand, the E2KPW_Trace.Log reports an error of the following form:
23/02/2012 21:36:20(GMT) CSDProcessor.ReadMailboxSDs Error -2147217761 Failed to read data (client permissions and/or objectscount) for folders in mailbox 'http://yourserver/exadmin/admin/yourdomain.com/MBX/mailboxwith&'. Bad Request(400)
With reference to the WebDAV specifications at http://www.webdav.org/specs/rfc4918.xml and http://tools.ietf.org/html/rfc3986#section-2.1 applications should percent-encode an ampersand the URI when performing a WebDAV SEARCH. The issue can be reproduced natively, with a PFDAVAdmin SEARCH returning '(400) Bad Request' for a mailbox name containing an ampersand and '(404) Not Found' for the name when the ampersand character is escaped with percent encoding..
The recommended workaround is to query for all such mailboxes with reserved characters such as the ampersand, and re-name them prior to running the Exchange Processing Wizard against them.
There are security implications in attempting to allow these character sequences to be accepted by the Microsoft Exchange Server as this increases the attach surface and the potential for damaging requests to be accepted.
