Share via

HMC Disable Namespace::DisableOrganization

  • Article

This procedure removes an existing organization from Hosted Messaging and Collaboration version 3.5 provisioning data stores. This includes setting the existing Plan Database (HeCustomerDB) records to a deleted state and removing Resource Manager records.This procedure is intended to be called only after the target organization has been sucessfully migrated to the Hosted Messaging and Collaboration version 4.0 platform.

Arguments

Input arguments Required Description

organization

Yes

The Lightweight Directory Access Protocol (LDAP) path of the organization.

preferredDomainController

Yes

The domain controller to use for Active Directory actions.

Remarks

All child organizations and users of the target organization must be disabled before running the procedure. If enabled users or child organizations are discovered during executing this procedure, an exception will be thrown.

Parameters Format

<executeData>  
        <organization>1..1 </organization> 
        <preferredDomainController>1..1 </preferredDomainController> 
</executeData>

Returns Format

The return message contains no parameters.

<executeData>1..1 </executeData>

Expected Results

  • The organization's record in the HeCustomerDb is expected to be marked "Deleted."

  • Any associations between the organization and service plans in the HeCustomerDb are expected to be marked "Deleted."

  • Any associations between the organization and customer assets in the HeCustomerDb are expected to be marked "Deleted." One example of this is SMTP Domains.

  • The offline address book allocation, if any, in the Exchange Resource Manager, is expected to be de-allocated.

  • Any public folder allocations owned by the organization in the Exchange Resource Manager are expected to be de-allocated.

  • Any mail storage allocated to the organization in the Exchange Resource Manager is expected to be de-allocated.

  • Any public storage allocated to the organization in the Exchange Resource Manager is expected to be de-allocated.

Sample Code

Example XML Request

<request>  
        <data>  
                <organization>LDAP://OU=AlpineSkiHouse,OU=ConsolidatedMessenger,OU=Hosting,DC=Fabrikam,DC=Com </organization> 
                <preferredDomainController>AD01.Fabrikam.Com </preferredDomainController> 
        </data> 
        <procedure>  
                <execute namespace="HMC Disable Namespace" procedure="DisableOrganization" impersonate="1" >  
                        <before source="data" destination="executeData" mode="merge" /> 
                        <after source="executeData" destination="data" mode="merge" /> 
                </execute> 
        </procedure> 
</request>

Example XML Response

<response>  
<data /> 
</response>

Applies To

HMC Disable Namespace for:

  • Hosted Messaging and Collaboration Migration version 4.0 Migration Kit