AD schema extension: Exchange 2010
In this post we will troubleshoot a problem you can encounter when you are extending the Active Directory schema for Exchange 2010. You can read this technet article for the steps to prepare the AD schema for Exchange 2010.
We encountered some problems when launching the command line:”setup.com /PrepareAD /OrganizationName:<Organization Name>”. First an error occurred and the setup process exited, after fixing this we had a warning when running the command.
- Error message: “The Exchange organization name is invalid”:
- Warning: The recipient “ldap389.info/users/test-user” is invalid and couldn’t be updated:
The setup exists with an error, when you open the Exchangesetup.log file you can read the following error message:
The Exchange organization name is invalid. Message: ‘The property value you specified, “{335A1087-5131-4D45-BE3E-3C6C7F76F5EC}”, isn’t valid. The value must not contain “‘~’, ‘`’, ‘!’, ‘@’, ‘#’, ‘$’, ‘%’, ‘^’, ‘&’, ‘*’, ‘(‘, ‘)’, ‘_’, ‘+’, ‘=’, ‘{‘, ‘}’, ‘[‘, ‘]’, ‘|’, ‘\’, ‘:’, ‘;’, ‘”‘, ”’, ‘<‘, ‘>’, ‘,’, ‘.’, ‘?’, ‘/'”.’
This error occurs because a schema extension for Exchange 2003 was already performed a few years ago, but no Exchange server was installed in the domain. When preparing the schema for Exchange 2003 the command line setup /forestprep creates a temporary organization named {335A1087-5131-4D45-BE3E-3C6C7F76F5EC} (which is a GUID). The organization is set up when you install the first Exchange 2003 server, you can read this article for more details. With later versions of Exchange (2007 and 2010), the organization name is set up when running the schema extension.
To fix this issue you need the Exchange 2003 CD and must run the “Setup /removeorg” command, in order to remove the temporary organization (read this KB for more details). Once this organization has been removed you can use the Exchange 2010 CD to launch the “setup.com /PrepareAD /OrganizationName:<Organization Name>” command again.
This problem was already discussed in a technet forum, the problem occured when preparing the schema for Exchange 2007, the same fix was applied.
This warning does not block the setup process, but you might not be able to setup a mailbox for the test-user account. This warning occurs because the account’s MailNickName attribute had a value edited, this attribute (brought by the Exchange 2003 schema extension) was used by another application. We had to clear the attribute value on the account in order to avoid this warning.
This post is also available in: French
