Solved

Groupwise migration to Exchange 2003

Posted on 2009-05-11
6
287 Views
Last Modified: 2012-05-06
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
Comment
Question by:ianforbes
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 37

Expert Comment

by:Jamie McKillop
ID: 24378345
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
 

Author Comment

by:ianforbes
ID: 24380237
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
 
LVL 37

Expert Comment

by:Jamie McKillop
ID: 24383901
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
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:ianforbes
ID: 24387651
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
 
LVL 37

Accepted Solution

by:
Jamie McKillop earned 500 total points
ID: 24387721
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
 

Author Closing Comment

by:ianforbes
ID: 31580364
Thanks!
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses
Course of the Month3 days, 23 hours left to enroll

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question