Generic Groupwise to Exchange Migration Advice

Good afternoon folks, I am after some general advice/guideance on a migration project that I am about to start working on.
We're taking a Novell eDirector/Groupwise environment to Microsoft AD/Exchange...I know there's tools/utils that will do the migration but I am just after some general real world experiences/gotcha's etc.
The AD will be a nice new Win2008 R2 AD so first question is, what order should I approach this in..
Build new AD
Install Exchange
Migrate User Accounts/Data
Migrate Groupwise to Exchange
or
Build new AD
Install Exchange
Migrate Groupwise to Exchange
Migrate User Accouts/Data
To me the first looks more logical but I'm looking for advice from the trenches so to speak....
Also, what utils/tools would you recommend for the migration and co-existence?

Hello,
I think you can do migrate Groupwise to Exchange at last.
Here is one related document for you, hope can give you some help:
http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/groupwise-exchange-2007-interoperability-migration-part1.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or
suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Thanks,
Evan Liu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

Similar Messages

GroupWise to Exchange Migration - lessons learned from a failedmigration

Read more at:
http://www.novell.com/communities/no...ion-exchange-2
007-%E2%80%93-notes-failed-migration

Novell actually designed the GW migration util because of several large Exch
to GW migrations. The very latest version is looking sweet and does a great
job.
Far better than any util out there taking GW to Exch.
Good Luck!!
Take Care.
Gregg A. Hinchman
Consultant
[email protected] ( mailto:[email protected] )
www.HinchmanConsulting.com
A Novell Consulting Partner
317.329.0288 Office
413.254.2819 eFax
"Courage is doing what is right."
"Do not be bound to any doctrine, theory or ideology, even Buddhist ones.
All systems of thought are guiding means, not absolute truth." Thich Nhat
Hanh, Vietnamese monk.
>>> On 8/25/2008 at 5:22 PM, in message <[email protected]>,
Paul
Caron<[email protected]> wrote:
> Hopefully Exchange 2003. Use the Exchange to GW migration tool from
> Novell
> - works great. Pitfalls? Be sure to locate the workstation(s) to do the
> migration as close as you can to the Exchange server. For example, I'm
> in
> the beginning phase of doing the same thing, from one organization that
> has
> Exchange. We're going to migrate them to our GroupWise. We can't run
> the
> software from our workstations - it has to be on a workstation in the
> source
> domain. (The login process assumes so and can't be supplied with a
> different
> domain to log into.
>
> You can do test migrations and see how the data looks coming over. If
> you're working with someone on the Exchange side, make sure that you can
> trust them. Make sure they don't sabotage your efforts (I'm currently
> dealing with this). Additionally, take no assumptions and catalog your
> accounts that you test the migration on - meaning - how many emails do
> they
> have in each of their folders? How many appointments, tasks, notes,
> etc.
> Make sure that you have the appropriate number after migration. In an
> earlier buggy release of the software, the migration looked fine and I
> had
> the IT guy verify - yup, looks good. Turns out he didn't fully inventory
> the user's accounts and we migrated about one third of the data. So do
> it
> yourself.
>
> GroupWise - make sure that you're running the latest GroupWise. Don't
> try
> to migrate from Outlook 2007 and go to GroupWise 6. The users will kill
> you.
>
>>>> On 8/25/2008 at 3:06 PM, tgerber<[email protected]>
> wrote:
>> Ok it's great to hear that you are staying with GW, but how do I goabout
>
>> migrating away from Exchange to GW? I must make this as seamlessas
>> possible because I am also brand new with the company. Has anyonedone a
>> migration away from Exchange to GW and what were some of thepitfalls? We
>
>> need to be able to run parallel for awhile to ensure asmooth
> transistion.
>
>> I am a Novell person who has just come onboard to anAD shop yet we are
>> switching to GW. :-) Any assistance would beappreciated.--
>
tgerber---------------------------------------------------------------------
> ---tgerber's
>> Profile: http://forums.novell.com/member.php?userid=29334View this
>> thread: http://forums.novell.com/showthread.php?t=333949

Migrate Novell Groupwise to Exchange Server

Migrating from one platform to another is really very tedious and complex job. However, manual migration of each user mailbox from Novell GroupWise to Exchange can be an extremely tedious and time consuming task. Starting from preparing Novell GroupWise
environment to installing and configuring connector manually, there is a long list of tasks to perform that needs a lot of technical expertise.
Therefore, GroupWise to Exchange Migration is the best tool to perform migration of mailboxes from Novell GroupWise to MS Exchange Server or MS Outlook. Equipped with user benefitted features, this software allows single and multiple mailbox
migration where users can save the migrated items to orphan .PST files or direct to MS Exchange Server user mailboxes.
Migrate archived items, address books, emails, trash items, attachments, images, calendars, work in progress, cabinet items and every other item of the mailbox..
You can try Free Demo version to see preview of Converted Mailboxes:- http://www.recoverydeletedfiles.com/groupwise-exchange-migration.html

GroupWise to Exchange migration tool perform the migration by two method.
Convert single GroupWise mailbox: In this method user is allowed to migrate only single GroupWise mailbox.
Convert batch of mailbox: In this method user is allowed to migrate batch of mailboxes
Thus having various features It has become one of the best GroupWise to Exchange migration tool.
Visit http://www.groupwisetoexchange.net/

Novell Groupwise to Hosted Exchange Migration

We are looking to migrate a client from Novell Groupwise Email to Hosted Exchange. It seems the only toll available to assist with this type of migration is the following:
http://www.quest.com/groupwise-migrator-for-exchange/
Does anyone know of any tools that Microsoft provides that are similar to this? I cannot really find any information via searching google, the microsoft partner portal...etc...
Thanks,
Ian

Most cusotmers moving from Groupwise utilize Quest Tools.
A couple other options, depending on the size of your user base:
http://www.nucleustechnologies.com/migrate-groupwise-to-exchange.html?gclid=CI-Pu6q8sKcCFQpvbAodLGjD_w
http://www.migrationwiz.com/Public/landing/groupwisemigrations.aspx?gclid=COX0jc28sKcCFQkFbAodBFngBw
If it wasn't difficult, it wouldn't be fun, but why's it got to be this much fun.

GroupWise 7 Exchange Gateway "Bad GroupWise proxy"

I am testing the GW7 Gateway on a GW702(NW) and Exchange 2003SP2 installation. I have it basically running, but there are 2 issues that I cannot seem to fix.
as part of my learning, I have determined that I must run the Gateway as an Application, due to the windows Service being unable to run from a NetWare UNC, and I also determined that the Gateway name must be 8 chars. This all works.
At this point, if I initiate a Directory Synchronization, it creates contacts for every GroupWise user in the AD import container, and contacts in GroupWise for any existing Exchange users.
My first issue is that it ONLY creates contacts. It does not seem to be able to "mail enable" existing AD accounts event though they match. It is ignoring the settings in the properties of the gateway-> Import Container "When replicating a mailbox whose primary account does not exist in the domain" if I set it to create a Windows Account. Is this normal?
Second issue is: if I migrate a user from GroupWise to Exchange using the Microsoft Exchange 2003 sp2 Migration wizard, it correctly removes the Contact, and mail enables the AD User account, but the new Exchange account will not synchronize.
The problem is that the directory sync gives errors on every user account that was migrated, and does not create a new contact in GroupWise. Any new user created manually in Exchange does sync and is ok. The verbose log in the Gateway says "DXIN: Ignored: Adding User GW701DO.GW701PO.Bob Brown: Reason-Bad GroupWise proxy".
Taking this message at it's word, I have ensured that the account running the Gateway has full AD and NDS rights, and is explicitly assigned full GroupWise proxy rights.
What does this error message really mean?

There is something else going on with the migrated user account. I have deleted the NDS account, leaving only the AD/Exchange user, but it still does not populate the gateway domain with a contact. It still says "Bad GroupWise Proxy".
I will test if I can export, delete, and then import this user so that I can reproduce the content of the AD account. Perhaps there is something in the attributes that is causing the gateway to fail to do it's creation.
Originally Posted by durrand
I've previously tried (and failed) to get the gateway to create windows user accounts - maybe a call to NTS is require to get newer code(?)
On the second issue, are you trying to import/export to/from the same conatner in AD and DOMAIN in GroupWise? Is it possible that the create fails because it clashes with the old account?
If you're only testing the gateway my suggestion would be to create a separate External Domain and use this in the Exchange GWISE addressing scheme (which, in turn, will ensure that any sync'd accounts are created in the new domain).

Zenworks to SCCM before Exchange migration??

We are currently a Novell shop and will be moving to all Microsoft in the next year. With that said, would you recommend having SCCM in production before migrating from Groupwise to Exchange?

Totally unrelated products. The order does not matter. It could even be done in parallel.
Torsten Meringer | http://www.mssccmfaq.de

Exchange Migration Workflow down

Using Exchange 2013 CU6 Standard with 2 Server in a DAG. Both Servers with the same Patchlevel. Last night the "Microsoft Exchange Migration Workflow" goes down. When I try to restart the Service goes imidetly down again.
Application Event says every time: Event ID 4999 from Source "MXExchange Common":
Watson report about to be sent for process id: 10984, with parameters: E12IIS, c-buddy-RTL-AMD64, 15.00.0995.029, M.E.Diagnostics.Service, M.E.Diagnostics.PerformanceLogger, M.E.D.P.PerformanceLogSet.StartLog, System.ArgumentException, 95c6, 15.00.0995.012.
ErrorReportingEnabled: False
Mailbox-Migration only works on the second node where no problems with Migration Workflow Service detected.
Any ideas?

Hi
In my case the event 4999 shows:
Watson report about to be sent for process id: 12992, with parameters: E12IIS, c-RTL-AMD64, 15.00.0995.029, MSExchangeMigrationWorkflow, unknown, M.E.M.L.L.<>c__DisplayClass11.<GetLocalServerData>b__10, System.NullReferenceException, 49af,
unknown.
ErrorReportingEnabled: True
Does that solution apply too? or it has another problem?, because began to raise another events like 1001 from Windows Reporting:
Fault bucket , type 0
Event Name: E12IIS
Response: Not available
Cab Id: 0
Problem signature:
P1: c-RTL-AMD64
P2: 15.00.0995.029
P3: MSExchangeMigrationWorkflow
P4: unknown
P5: M.E.M.L.L.<>c__DisplayClass11.<GetLocalServerData>b__10
P6: System.NullReferenceException
P7: 49af
P8: unknown
P9:
P10:
Attached files:
C:\Windows\Temp\1e07ce7f-6e1c-49ce-a995-6152985231ac\report.txt
C:\Windows\Temp\1e07ce7f-6e1c-49ce-a995-6152985231ac\report.xml
These files may be available here:
Analysis symbol:
Rechecking for solution: 0
Report Id: c3dece0a-76c6-11e4-80d0-6cae8b1d2a4b
Report Status: 262144
Hashed bucket:
But I cannot find the file report.txt and .XML even if I select to show hidden ítems.
In the active node of the dag, that service is running without problems, but in the other node stops....
or raise Eventid 7031 Service Control Manager:
The Microsoft Exchange Migration Workflow service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
This raise every 10 seconds... even if I set that service in Manual startup type.
I noticed this when I tried to add a database copy with no success...
Exchange 2013 CU6 and all patch applied until this week.

SBS2011 Exchange Migration (Server configuration change is temporarily preventing access)

Greetings,
I 've begun an exchange migration from SBS2011 (Exch 2010) to 2013 Exchange. I am on this step of the deployment assistant, for reference, http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-EQBEAgAAQAAAAQEAAQAAAAg~
I can login and access any users mailbox with the respective credentials if their mailbox is on the SBS exchange server.
Ive migrated a couple test users, and while I can access their owa box if I browse to the localhost of the 2013 server, I cannot access their mailbox internally nor externally if I go to the external FQDN of the owa site. All other users with mailboxes
still on the 2010 exchange work.
I get this message for those with mailboxes on the new server: A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
Any ideas?
Thanks!

Hi,
On current situation, please check if you move mailboxes to the new Database properly. Please refer to Olaf’s
solution in following thread and check if can help you.
OWA
not working after SBS2008 to SBS 2011 Migration
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Issue with client-side rules after Groupwise to Office365 migration

We are preparing for migration from Groupwise to Office365 and face an issue for which I do not have a solution for: Groupwise rules currently contain functional mailboxes that include rules to implement business logic. When migrating these mailboxes to
Office365, the rules must be applied manually (since Quest can't handle it). So far so good. However, some of these business logic rules are client-side rules, which will never be executed because it's a functional mailbox.
The issue arises among multiple mailboxes, for instance for a customer-receive mailbox that moves incoming mail based on subject to a sub-folder.
Anyone an idea how to implement this, without having to use a logged-on user/outlook client?
Please advice.
Gr, Mike Schmeitz

We are preparing for migration from Groupwise to Office365 and face an issue for which I do not have a solution for: Groupwise rules currently contain functional mailboxes that include rules to implement business logic. When migrating these mailboxes
to Office365, the rules must be applied manually (since Quest can't handle it). So far so good. However, some of these business logic rules are client-side rules, which will never be executed because it's a functional mailbox.
The issue arises among multiple mailboxes, for instance for a customer-receive mailbox that moves incoming mail based on subject to a sub-folder.
Anyone an idea how to implement this, without having to use a logged-on user/outlook client?
Please advice.
Gr, Mike Schmeitz

GroupWise to Exchange

Just wondering if anyone has any experience migrating from GW 7.x/8.x to Exchange 2K7/2010? If so I am curious what utilities/software if anyone used? Example: Quest Migration, M+ Archive or other?

I did it in March 2008, thousands of mailboxes, 70 postoffices from Groupwise 7.0.3 to Exchange 2007 SP1. I used the quest tools, and they worked GREAT. I already had my AD in place. The biggest obstacle for us was archives, we mad people get their
mailbox size under 500 megs, prior to this we had no size limit. So after the migration we had tons of Groupwise archives we had to convert into PST's and make them statically available to users.This was an awful process because so many people's GW archives
were corrupt and some of them were unusable. The Quest tools are expensive, but worth every penny.
We also did it in phases 1 postoffice at a time, so we were interoperating with Groupwise for a while. During this time, free/busy (busy search) between Exchange and Groupwise is not available, this was a challenge for SOME users, but a minority. We did
leave Groupwise as the primary SMTP connector until the migration was over, then we made Exchange primary.

Exchange Migration from One domain to another domain on same forest

Team,
we are in the process of migrating exchange infrastructure from one child domain to another child domain within same forest.
root domain - root.com
child domains - US.root.com and EMEA.root.com
EMEA and US Domains setup are different from each other. Like EMEA has different email address policy , Email Flow than US , connectors etc.
Now we need to migrate all emea users under US Domain. based on the geographical locations, we are building a new dc, mailbox , cas servers on EMEA location , but these servers will be part of US Domain.
for CAS Servers - we are planing to register respective sites ( site affinity), so all the local requests will be handled by new cas server which is built under US Domain.
Mailbox Servers - we would be creating new db's and the limits on new mbx server and going to replicate as its on EMEA Mailbox server.
can some one please let us know what are the precautions , recommendation, sequence which we need to follow to perform smoother migration. as of now , I can think of below topics.
Mailbox Migration -I Have a script , which
will take care of mailbox movement once the objects are being moved.
Contacts Migration - Willard Martin blog helped me to perform migration
DL Migration - I believe there is no mechanism to migrate DL. only option is to recreate.
Email address Policy:we would be creating a new address policy and apply to OU's
DB Consistency check – do we have to perform the health checks on source mailbox server to see , the servers are free from errors /corruption.
Check outlook configuration - After the migration, we need to check and see , the exchange server/ auto discover works and identify the new exchange servers.
Internal /External Email flow.-
Active Sybc , OWA
Public folder Migration -
Offline Address Book
Certificates
any help or suggestions would be great.
Srinivasa K

Hi Srinivasa,
According to your description, I think you have done all the preparation.
For DL migration, the following article may give your some hints:
How to Migrate Distribution Groups Across a Forest
Good Luck!
Niko Cheng
TechNet Community Support

Migration advice

My little Mac Mini died, so I have ordered a new iMac. But I'm not sure of the best migration strategy. The old Mini was running Leopard, so I have both Time Machine and Backup3 backups on external hard drives as well as .mac syncing. I also have a Macbook with a lighter but similar setup. Should I use Time Machine, or Backup 3 to rebuild my data and applications? Or Migration Assistant? I would appreciate any advice from anyone who has been through this experience.

If the Mini is an Intel model then you should be able to migrate directly to the iMac. However, if it's a PPC Mini, then I recommend against using Migration Assistant and move only your personal data manually:
Folders You Can Move to Your new Mac
From the Home folder copy the contents of Documents, Movies, Music, Pictures, and Sites.
In your /Home/Library/ folder:
/Home/Library/Application Support/AddressBook (copy the whole folder)
/Home/Library/Application Support/iCal (copy the whole folder)
Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)
/Home/Library/Keychains (copy the whole folder)
/Home/Library/Mail (copy the whole folder)
/Home/Library/Preferences/com.apple.mail.plist (* This is a very important file which contains all email account settings and general mail preferences.)
/Home/Library/Preferences/ copy any preferences needed for third-party applications
/Home /Library/iTunes (copy the whole folder)
/Home /Library/Safari (copy the whole folder)
If you want cookies:
/Home/Library/Cookies/Cookies.plist
/Home/Library/Application Support/WebFoundation/HTTPCookies.plist
For Entourage users:
Entourage is in /Home/Documents/Microsoft User Data
Also in /Home/Library/Preferences/Microsoft
For FireFox:
/Home/Library/Applications Support/FireFox
/Home/Library/Preferences/org.mozilla.firefox.plist
Credit goes to another forum user for this information.
If you have PPC-only third-party applications on the Mini then either upgrade them to universal binary versions or reinstall them on the iMac from scratch. All other third-party applications should be reinstalled. Do not use any third-party PPC-only plug-ins such as contextual menu items, login items, startup items, preference panes, input managers, internet plug-ins, and the like because they will not work on an Intel Mac.

Changing generic selection parameters for Payment advice notes

Hi,
I want to add few more generic selection parameters for Automatic Payment advice notes generation on the seletion screen(f110 - rffoavis_fpaym). Please let me know the config settings for doing this.

Hi Pradeep,
you can change the sender, when you change the system-field SY-UNAME before calling FM SO_NEW_DOCUMENT_ATT_SEND_API1.
REPORT Z_TEST_SEND_MAIL.
h_uname must be a SAP-UserId.
sy-uname = h_uname.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
    EXPORTING
      DOCUMENT_DATA              = DOC_CHNG
     PUT_IN_OUTBOX              = 'X'
      COMMIT_WORK                = 'X'
    TABLES
      PACKING_LIST               = OBJPACK
      OBJECT_HEADER              = OBJHEAD
      CONTENTS_BIN               = OBJBIN
      CONTENTS_TXT               = OBJTXT
      RECEIVERS                  = RECLIST
    EXCEPTIONS
      TOO_MANY_RECEIVERS         = 1
      DOCUMENT_NOT_SENT          = 2
      OPERATION_NO_AUTHORIZATION = 4
      OTHERS                     = 99.
I tried it and it was successfull.

Exchange Migration 2010 to 2013 different AD domains....

Here's my situation, I have migrated our users AD accounts to a new domain (newDomain.corp), but still use the exchange server in our old domain (oldDomain.corp) with linked mailboxes, which work fine.
I am now to the point where I want to decommission our old 2010 exchange server in the old domain, or at least have the users mailboxes on a new Exchange 2013 box belonging to the new domain.
I am looking for the best way to migrate the users mailboxes from the EXCH01oldDomain.corp (2010 Exchange server) to the new exchange 2013 server EXCH01.newDomain.corp, yet still have both servers online serving mailbox roles for users for a limited
time. So basically, can i have 2 exchange servers from different domains serving the same users in newdomain.corp?
Free busy and calendaring all have to work.
Thanks!
richard

Hi Richard,
Please make sure the two-way trust between the new domain and old domain has been set up.
Generally, when we run New-MoveRequest cmdlet to move a mailbox from an Exchange source forest (Old domain) to an Exchange target forest (New domain), the target forest must contain a valid Mail-Enabled user account with the set of AD attributes.
Since the mailboxes in old Exchange 2010 are all linked mailbox
which have Mail-enabled user accounts in new forest, we can directly move the mailbox from old Exchange 2010 to new Exchange 2013.
We can use the Prepare-MoveRequest.ps1 script with the -UseLocalObject to move mailbox with the existing AD account in new domain:
http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange Migration

Hi All,
Require some help if possible.
Migrated a company from a 3rd party exchange provider over to our own internal exchange.
Users are now unable to edit or change calendar items that existed prior to the migration, a bounceback is below.
They have full permissions over the calendars, this has been confirmed and rechecked. I know this for certain as new items can be created.
The bounceback I see is like below:
Delivery has failed to these recipients or groups:
[email protected] You can't send a message on behalf of this user unless you have permission to do so. Please make sure you're sending on behalf
of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server:
[email protected] #MSEXCH:MSExchangeIS:/DC=local/DC=uptime:USEXMB2[578:0x000004DC:0x0000001D]
#SMTP#

How is the co-existence working between 2 forest?
Is it happens to all the Calendar items or some of them?
Did you had a chance to look at this thread?
http://social.technet.microsoft.com/Forums/exchange/en-US/128f9a31-e805-4dd9-8255-629d871b90d3/you-cant-send-a-message-on-behalf-of-this-user-unless-you-have-permission-to-do-so?forum=exchangesvrgeneral
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Generic Groupwise to Exchange Migration Advice

Similar Messages

Maybe you are looking for