Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Tue, 25 Mar 2008 05:18:16 -0700,    group: microsoft.public.exchange.connectivity        back       


Migration from GroupWise 7 to Exchange 2007 SP1   
I am currently working on a project to migrate our GroupWise 7 email system 
to Exchange 2007 SP1. We are going to need to provide coexistence for a 
phased migration from GroupWise to Exchange. We have an Exchange 2003 server 
installed which was being used for voicemail accounts for our newly installed 
Cisco Unity system. We also have an Exchange 2007 SP1 server installed. The 
accounts for the voicemail boxes have been moved to the Exchange 2007 server. 
The voicemail accounts are configured to work with the user's email address. 
So the moved voicemail accounts are mail-enabled.

We have Active Directory and Novell EDirectory running with Novell's 
Identity Manager product sychnronizing the two systems - we do not have the 
email provisioning feature activated. We will be using the Quest migration 
tool to migrate users but we need to provide coexistence among the email 
servers as well as provide the free/busy search capabilities. We have 
installed the following components so far to provide the coexistence: 
GroupWise API 4.1 SP2, Microsoft Connector for GroupWise, and Calendar 
Connector.

The problem is in our ability to configure the Microsoft Connector for 
GroupWise appropriately before starting up the services. The instructions 
indicate that we need to have an import container selected (can be only one 
organizational unit) in order for the connector to place recipeint objects 
created for Novell GroupWise users. Also an export container needs to be 
assigned as well for exporting Exchange recipient objects to the Novell 
GroupWise directory. We are unsure what the results will be if we do this 
because of our current synchronization configurations - we have user accounts 
that are email enabled in AD as well as EDirectory that continue to get 
synchronized. Will this configuration produce duplicate accounts if we 
continue with the configuration? 

We have been unsuccessful in finding any assistance with this situation. 
Quest has informed us that they cannot help us because this coexistence must 
be configured before they can provide any type of support. Any ideas how we 
can get the proper support we need to move forward on this migration project? 
THANKS!
date: Tue, 25 Mar 2008 05:18:16 -0700   author:   pnote

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us