Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 295
  • Last Modified:

Groupwise migration to Exchange 2003

My client's organization has recently acquired 2 companies. Both acquired companies (Company A/Company B) use Novell Groupwise, while the acquiring company (Company C) uses Exchange 2003. There are two-way trusts between the acquired companies and Company C.

Phase I - Company A and C are in two different AD forests/domains. Company A runs Groupwise. They require their users mailboxes to be migrated to Exchange 2003. Company A would like their users to continue logging onto their current domain BUT launch their Exchange/Outlook mailboxes, which will reside in Company C domain. Company A would also like their email addresses to be changed to user@companyC.com - currently user@companyA.com.

Phase II - Company B and C are in two different AD forests/domains. Company B is on Exchange 2003. They require their users mailboxes to also be migrated to Company C Exchange 2003. Company B would like their users to continue logging into their current domain BUT launch their Exchange/Outlook mailboxes, which will reside in Company C domain. Company B would like to retain their email address, which is user@companyB.com.

Would it make sense installing a Groupwise connector during migration? What tools should I use to migrate the Groupwise mailboxes? What else needs to be done to complete Phase I

What about phase II? What needs to be done?

Thanks
0
ianforbes
Asked:
ianforbes
  • 3
  • 3
1 Solution
 
Jamie McKillopIT ManagerCommented:
Hello,

I'm not familiar with Groupwise, so I can't answer your connector question, but I can answer your Phase I and Phase II questions...

Phase I: Once you have the mailboxes migrated, disable the AD account then right-click the account and select Exchange Tasks. Select Associate with an External account and select the user account in the other domain. The default email address should be assigned by your recipient policy, which I assume would assign user@companyC.com. You will need to change the recipient policy if you want to add user@companyA.com

Phase II: Same as above except the email addresses. You will need to add a recipient policy for these users which sets the default address to user@companyB.com. There needs to be something unique about these user accounts (OU, company name, etc) that you can apply the filter to.

JJ
0
 
ianforbesAuthor Commented:
Hi JJ

Phase I -So you're saying a should be creating "dummy accounts" in Company C which will be tied to the migrated Company A mailboxes. Then, re-associate the "dummy account" with the account from the other (trusted) domain? The MX for CompanyA wouldnt be changed until the last prson was migrated, so I suppose I'd have to do a store and forward from Company A to Company C in the meantime?

PhaseII - Makes sense.

Thanks!
0
 
Jamie McKillopIT ManagerCommented:
Yes, you create "dummy accounts" in Domain C. These accounts must be disabled then the mailbox is associated with the account from the trusted domain.

You will need to share the SMTP namespace between Exchange and Groupwise until you finish the migration. The best way to do this is to setup Exchange to share the name space (http://www.msexchange.org/tutorials/Exchange-2003-SMTP-Namespace-Sharing.html) then point your MX record at Exchange before you start migrating users. This will forward all unresolved recipients to Groupwise. As you migrate users, the addresses get resolved in Exchange instead of being forwarded. As you migrate users, you will need to replace them in Groupwise with Groupwise's equivalent of contacts. Those contacts should have the SMTP address user@domainC.com. You need to do this so that users who haven't been migrated can send to users who have.

JJ
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
ianforbesAuthor Commented:
Thanks JJ. Great info. I've configured Exchange for exactly what you're talking about before. Why couldn't I just let mail continue to be delivered to Company A's MX and just do a store and forward to the migrated users Company C mailbox? When everyone has been migrated over I could then change Company A's MX.

This way no real changes need to be done. People still not migrated yet in Company A will still send an email to people who have been migrated using the same email address they've always used - and it will be delivered by way of a store and forward.

Does that sound like it'll work?
0
 
Jamie McKillopIT ManagerCommented:
As long as Groupwise can be configured to deliver any unresolved recipients to Exchange, that will work. If "store and forward" needs to be configured on a per user basis, it will create a lot of extra work and you will need to make sure you set this up for any new objects you create in Exchange.

JJ
0
 
ianforbesAuthor Commented:
Thanks!
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now