When migrating public folders from legacy Exchange 2007 and Exchange 2010 environments to Exchange 2013, you may receive the following error message:
Error: Property expression "Anglicare RT" isn't valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.
This is caused by an invalid alias format generally created from legacy versions of Exchange such as 2000 or 2003. Exchange 2010/2013 does not support spaces in the Public Folder Alias.
On the legacy Exchange 2007/2010 server open up Public Folder Management console and navigate to the Public Folder in question. On the Exchange General tab you will receive an error message saying the object contains invalid data.
Simply remove the space from the Alias, this is no longer supported.
Error: Property expression "Anglicare RT" isn't valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.
This is caused by an invalid alias format generally created from legacy versions of Exchange such as 2000 or 2003. Exchange 2010/2013 does not support spaces in the Public Folder Alias.
On the legacy Exchange 2007/2010 server open up Public Folder Management console and navigate to the Public Folder in question. On the Exchange General tab you will receive an error message saying the object contains invalid data.
Simply remove the space from the Alias, this is no longer supported.
Next go back to your Exchange 2013 server and resume your public folder migration request.
You may need to repeat this process a few times as it is likely multiple public folders have incorrect aliases.
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon