Exchange Tenant Mig...
 
Notifications
Clear all

Exchange Tenant Migration from MSPControl to SolidCP

4 Posts
2 Users
1 Reactions
905 Views
Posts: 17
Topic starter
(@rickstinson)
Active Member
Joined: 6 years ago

Hi,

we moved to solidCP some years ago and migrated all user from msp - except some customers using public folders.
So, i'm aware of the normal migration process.

But what about our customers with public folders in use?
- I can import them with the enterprise tool, and move everything in a new OU, update the GAL for every User + public folder user
-> In this case, users should still have access to their old public folder (link in the User "msExchPublicFolderMailbox")

But what about new Mailboxes created in Solid CP? They will get the public folder created by solidcp, not the old one.
Can i force SolidCP to use the old, existing public folder?

Thanks a lot!
Patrick

3 Replies
Posts: 17
Topic starter
(@rickstinson)
Active Member
Joined: 6 years ago

Some ideas...

creating new hosted org in solidcp with new name (eg domain instead of domain.com)
rename the ou from domain(/customers/domain) to domain.com (/customers/domain.com)
edit all the serviceitemproperties in the db from domain to domain.com
move all items vom old MSP OU (/hosting/domain.com) to /customers/domain.com
import all users with the enterprise import tool
update the gal (just in case)
- everthing should be fine?

Most important: Users shouldnt have any impact, especially on public folders (eg public folder favorites in outlook, etc)

Reply
Posts: 17
Topic starter
(@rickstinson)
Active Member
Joined: 6 years ago

This way worked for me, for using the existing public folder:

  • creating new hosted org in solidcp with new name (eg domaincom instead of domain.com)
  • rename the ou from domain(/customers/domaincom) to domain.com (/customers/domain.com)
  • edit all the serviceitemproperties in the db from domaincom to domain.com:
    UPDATE dbo.ServiceItemProperties
    SET PropertyValue = REPLACE(PropertyValue, 'domaincom', 'domain.com')
  • edit ServiceItems to set domaincom to domain.com
    UPDATE dbo.ServiceItems
    SET ItemName = REPLACE(ItemName, 'domaincom', 'domain.com')
  • edit ExchangeOrganizations to set domaincom to domain.com
    UPDATE dbo.ExchangeOrganizations
    SET OrganizationID = REPLACE(OrganizationID, 'domaincom', 'domain.com')
  • Search in "dbo.exchangeAccounts" for the security group account "domaincom" and rename it to "domain.com"
  • move all items vom old MSP OU (/hosting/domain.com) to /customers/domain.com
  • import all users with the enterprise import tool (security groups will fail)
  • Manual create security groups in the database
    -> ItemID = the id of the customer
    -> Values are case sensitive!
    INSERT INTO dbo.ExchangeAccounts (ItemID, AccountType, AccountName, DisplayName, SamAccountName)
    VALUES (525, 9, 'username', 'Displayname', 'AD\username');

= current users shouldnt have any impact, especially on public folders (eg public folder favorites in outlook, etc)
= new users are created also with no impacts

Reply
1 Reply
Admin
(@m-tiggelaar)
Joined: 9 years ago

Noble Member
Posts: 1967

@rickstinson Very nice and detailed instructions. 

Do you mind if i add this to the msp control to scp manual? (current instructions on there are for a old version).

Reply
Share: