This section provides the details of the HMC Disable Namespace included with the Microsoft® Provisioning System (MPS). The HMC Disable Namespace is designed for removing an existing organization from Hosted Messaging and Collaboration version 3.5 provisioning data stores.
All procedures defined in HMC Disable Namespace require Domain Admin privilege to execute.
The procedures in this namespace are for migration purpose from Hosted Messaging and Collaboration version 3.5. With earlier versions such as Hosted Messaging and Collaboration version 3.0, you need to do clean deployment.
|HMC Disable Namespace::DisableOrganization||This procedure removes an existing organization from Hosted Messaging and Collaboration version 3.5 provisioning data stores.|
|HMC Disable Namespace::DisableUser||This procedure removes an existing user from Hosted Messaging and Collaboration version 3.5 provisioning data stores.|
The following table documents common exceptions that can be raised by the procedures in HMC Disable Namespace.
|0x80070057||The argument '%1' cannot be null.||A required argument was supplied without a value.|
|0x80070057||The required argument %1 was not supplied.||A required argument was not supplied in the request.|
|0x80070057||Insufficient Privilege! Not Domain Administrator.||A procedure was run with credentials not belonging to a user that is a member of domain admins.|
|0x80072030||Unable to open object '%1'./There is no such object on the server./ADsGetObject||The specified object was not found in Active Directory.|
|0x80131509||The organization has %1 active child organizations or users. You must first disable all children before this organization can be disabled.||The specified organization was discovered to have child organizations or users still present in the plan database (HeCustomerDb).|