Re: Migration from Groupwise 7 to Exchange 2007 Need Help!
- From: mdgray@xxxxxxxxx
- Date: Wed, 07 Nov 2007 20:53:58 -0000
JasonJ
I am experiencing the same issues in our migration as you. We are
moving away from a 15 post office 2500 user GRoupwise system to a
Exchange 2007. I have nutted how I both email systems can exist and
emails can be sent between them. I am still working on Migration and
shared address books at the moment. One strategy we have thought about
is using the Outlook 2007 client and connect to GRoupwise and Exchange
at the same time and moving the mail that way. Anyone seen this done
before?
As far as a plan goes I read the "Microsoft Exchange 2007 Unleashed"
eBook and there documented is a guided explanation of how you should
choose your hardware and how to choose the correct configuration for
your environment.
Matt
On Nov 3, 1:03 pm, "Ed Crowley [MVP]" <cursp...@xxxxxxxxxxxxxx> wrote:
Sorry, but I wandered off-topic forgetting you were doing a Groupwise
migration.
If you can't buy a tool, your best approach might well be to cut over mail
delivery to the new system, and leave the old Groupwise system up and
running long enough for everyone to print out or otherwise archive all the
mail they want to keep. If your users use Outlook with Groupwise, you can
instruct them to log into Groupwise one last time after cutover day, and
copy all their mail to a PST. Of course, they won't be able to reply to it,
they'll have to readdress replies. And they'll probably have to recreate
their contacts, or at least fix all the addresses. There will undoubtedly
be other nasty side effects.
Your management can decide whether the pain they'll be inflicting on their
employees is worth the savings from not buying a tool set and the expertise
to deploy it properly.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"Ed Crowley [MVP]" <cursp...@xxxxxxxxxxxxxx> wrote in messagenews:eDssUxbHIHA.4272@xxxxxxxxxxxxxxxxxxxxxxx
Without the Quest or NetIQ tool set, or proper use of the free Microsoft
tools, it will likely be anywhere from a slightly to excruciatingly
painful experience for your users.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"JasonJ" <Jas...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:50CB279B-F353-4565-BE37-9FAF0221BF40@xxxxxxxxxxxxxxxx
Tell me about it!! This is a forced mandate without a business reason.
The
budget is so small it's almost non-existent. We asked for consulting
help
but were denied. However I think our team has the capability to pull
this
off with a small bit of guidance. Some basic steps we may overlook,
suggestions or things to look out for would be appreciated. We may not
even
be able to purchase the Quest Migration tool. Our project deadline has
been
set by upper management for May 1, 2008 and more items keep getting added
to
the scope of this project that should not be. This is a huge undertaking
and
I realize there is no simple answer. You mentioned a couple of authors,
which titles by them would you recommend. We have basically stated that
without hiring outside consulting and purchasing the Quest software, the
best
method may be just to build our network from scratch side by side and
schedule a mass cut over. Any thoughts on that idea.
Thanks for your response.
"Ed Crowley [MVP]" wrote:
What you've asked is what I call a "consulting engagement question", a
question so complicated or requiring so many follow-up data-collection
questions from us that we can't possibly give you the depth of
information
the issue deserves. You really ought to hire a consultant to work this
project through with you, or pick up Tony Redmond's and Jim McBee's
books
and start reading.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"JasonJ" <Jas...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C8EA7D8D-6DD6-4E8C-9921-DAE11D19D908@xxxxxxxxxxxxxxxx
Our organization is migrating from Novell eDirectory and Groupwise 7
to
Active Directory and Exchange 2007. We have always been a Novell shop
and
have had some active directory and exchange training but not much
experience.
We may not have $ in our budget to purchase a third party connector
such
as
quest and are looking for other deployment options and suggestions on
the
best way to perform this migration with the least disruption to users.
We have approximately 900 users/mailboxes on our domain with post
offices
setup on 6 remote sites 5 of which are connected by high speed fiber.
If
we
cannot purchase the connector we would at least like some sort of
client
export utility so the users can import their contact lists and
calendars.
I am looking for suggestions and guidance on successfully converting.
Any suggestions on the following would be greatly appreciated as our
deadline is May 1, 2008.
Migration tools/process?
Deployment scenarios
Project Plan templates
Any migration tools compatible with our versions? It appears the
migration
tools supplied by MS are not compatible with Groupwise 7.
There is so much information on the web and MS Technet site I am not
sure
what the best method is.
Thanks in advance for your help.
Jason Jefferson
Senior Network Technician
St. Charles County Government
.
- References:
- Re: Migration from Groupwise 7 to Exchange 2007 Need Help!
- From: Ed Crowley [MVP]
- Re: Migration from Groupwise 7 to Exchange 2007 Need Help!
- From: JasonJ
- Re: Migration from Groupwise 7 to Exchange 2007 Need Help!
- From: Ed Crowley [MVP]
- Re: Migration from Groupwise 7 to Exchange 2007 Need Help!
- From: Ed Crowley [MVP]
- Re: Migration from Groupwise 7 to Exchange 2007 Need Help!
- Prev by Date: Re: Data and Server MIgration
- Next by Date: Re: Using Exchange 2003 as a backup email server
- Previous by thread: Re: Migration from Groupwise 7 to Exchange 2007 Need Help!
- Next by thread: All mail from exchange goes to spam fold on external mail
- Index(es):
Relevant Pages
|
