This procedure imports a consumer or business user into MPS system. This procedure attempts to import a user into the Hosted Exchange and MPS systems by doing the following:
The user must be located in an OU container that is compliant with the hosting prescription. If the OU was created or processed with any of the following, then it is valid:
When creating a user, it is necessary to also ensure that the new user's sAMAccountName is unique within the domain. If it is not, creation will fail. The procedure will attempt to create the object with the provided sAMAccountName. If this value is not unique in the domain, then the following auto account name generation applies:
Also, interactions with Exchange make it undesirable for the '@' character to appear in a sAMAccountName. Therefore, when creating or renaming a user or group, the sAMAccountName will be similar to the input name (or Universal principal name), except that illegal sAMAccountName characters are removed, and '@' characters are replaced with '_'. If the sAMAccountName collides with an existing sAMAccountName, then a random string of digits will be appended to the sAMAccountName to ensure uniqueness.
The algorithm for generating a sAMAccountName from the seed name (Universal Principal Name for a user, or cn if the object is a group), is as follows: type="ORDERED"
Example XML Request
Minimal XML Usage
The minimal usage shown above will only have the following effects on the specified users:
Example XML Response
Shown for format only; content may vary.
MPS Import Namespace API for: