Deployment of DNP Exchange Solution in existing AD/Exchange environment is supported. However DNP Exchange Solution cannot automatically and immediately start working with customer organizations, created before DNP Exchange Solution deployment (manually or with another provisioning system).

You can immediately start create and manage new customer organizations in DNP Exchange Solution. However to manage previously created organizations with DNP you need to migrate them to DNP.

It was developed and practically approved migration plan inside one AD/Exchange that will not affect your users very much.

Here is high-level description of steps for migrating one customer organization:

• Create new customer organization in DNP for old organization, created before DNP Exchange Solution deployment. DNP will create Organizational Unit (OU) for this organization. This OU will have the same name as Organization ID and located inside root OU used by DNP Hosted Organizations module.
• Move this organization's users, contacts and distribution groups to new OU with Active Directory Users and Computers native tool.
• Move those user's mailboxes to DNP-managed mailbox database with Exchange Management Console or Exchange Management Shell.
• Manually set some attributes on moved mailboxes, contacts and distribution groups.
• Request Exchange Import Tool and run it against organization you are migrating.
• Backup Public Folders content for organization you are migrating to ".pst" files with Outlook.
• Re-create Public Folders in newly created organization with DNP.
• Restore Public Folders content in newly created organization from ".pst" files with Outlook

Note. Migrated users, contacts and distribution groups may preserve their old pre-Windows 2000 names and Exchange aliases. They only condition - they must be unique. Newly created uses, contacts and distribution groups will get standard (DNP style) pre-Windows 2000 names, Exchange aliases, etc. You can change those attributes to old users (set them in DNP style for unification) or you can stay them as is for easy migration.

Here is low-level description of steps for migrating one customer organization:

   1. From the panel create Customer hosted organization in Hosted Organizations.

   2. Make organization "Exchange-enabled". For this create any Exchange-related object (mailbox, or distribution group, or contact, or public folder) and then delete it.

   3. Move users, contacts and distribution groups to newly created OU - DNP Hosting OU\Customer with Active Directory Users and Computers tool.

   4. Move user's mailbox to Mailbox database managed by DNP Exchange Solution with Exchange Management Console or Exchange Management Shell.

   5. Ensure that "User logon name (pre-Windows 2000)" is the same as "Alias" both for users and distribution groups. You can do it with the Exchange Management Console manually or with scripts like those:

   For users:

   $user = get-mailbox User
   set-mailbox User -Alias $user.SamAccountName

   For distribution groups:

   $group =Get-DistributionGroup Group
   set-DistributionGroup Group -Alias $group.SamAccountName

   Those scripts copy "SamAccountName" (pre-Windows 2000 User logon name) attribute value to "Alias".

   6. Open Active Directory Users and Computers and ensure that "Name" is the same as "User logon name (pre-Windows 2000)" both for users and distribution groups. To make them the same copy "User logon name (pre-Windows 2000)" to clipboard, right click user user in Active Directory Users and Computers, choose "rename" and paste name from clipboard. Change only "Full name" in "Rename user" dialog box opened.   

   7. Set appropriate custom attributes for users, contacts and distribution groups:

   For users:

   Set-Mailbox -Identity ‘User'-OfflineAddressBook 'Customer Offline Address Book' -CustomAttribute1 ‘Customer' -CustomAttribute3 'user@hosterdomain.local'

   For contacts:

   Set-MailContact -Identity ‘Contact' -CustomAttribute1 ‘Customer'

   For distribution groups:

   Set-DistributionGroup -Identity ‘Group' -CustomAttribute1 'Customer' -CustomAttribute3 ‘group@hosterdomain.local'

   8. Add migrated users to AD group created by DNP:

    Add-DistributionGroupMember -Identity ‘Customer' -Member ‘User'

   9. In ADSI Edit locate ‘hosterdomain.local/DNP Hosting OU/Customer/User' account. Type in "msExchQueryBaseDN" property the distinguished name of the organization OU: OU=Customer,OU=DNP Hosting OU,DC=hosterdomain,DC=local

    Note. You can copy this attributes value from sample user created by DNP in this Organization.

   10. Repeat steps 2 - 8 for all users in migrated organization

   12. Run Exchange Import Tool against organization you are migrating, with "Import users only" checkbox selected

   12. Check that mailboxes became visible in DNP

   13. Check that mailboxes became manageable with DNP

   14. Backup Public Folders content for organization you are migrating to .pst files with Outlook

   15. Re-create Public Folders in newly created organization with DNP

   16. Restore Public Folders content in newly created organization from .pst files with Outlook

All bold green are variables:

Customer - customer organization ID (automatically the same as OU).

User - Exchange Alias for user/mailbox

Group - Exchange Alias for distribution group

Contact - Exchange Alias for contact

hosterdomain.local - internal AD domain

DNP Hosting OU - root OU for DNP hosted organizations