Todd
Sat Sep 11 12:06:41 CDT 2004
Microsoft does support newer versions of GroupWise. They would be crazy to
turn away a company migrating to their platform just because of the version
of their email system. The official Microsoft statement is that they will
support newer versions of GroupWise (6 and 6.5), however they have not
TESTED the connector on these versions of GroupWise. They will do
everything they can to resolve an incident that you open with them on this
even if your on 6. or 6.5. I had one open for about 2 months. They will
even put a little effort in to code updates to try to resolve it.
having said that, if you are migrating a large number of accounts, go with a
3rd party utility to migrate the mailboxes.
The Microsoft Migration wizard had problems in my migration. All mail and
tasks migrated fine. I had problems with the calendar items. I finally
closed the incident after finding a couple 3rd party utilities that worked
much more reliably. The calendar items are converted into a .sc2 file and
show up as a single email with this .sc2 file attachment. .sc2 is a
schedule+ file type, Microsoft's old calendar program. We use the calendars
pretty heavily and also use recurring appt's a lot, I found that users who
didn't have many items in the calendar migrated with no errors. the heavy
calendar users gave me 1 error, this would be that email with the .sc2
attachment. it errored on the export from GW side. BUT, I found the
weirdest thing, if I had a user who errored out on the calendar items, I
could go into the GW account and archive the calendar items, then
immediately unarchive them and the they would migrate with no errors. can't
think of any reason why this would change anything, but it did.
If you don't have a large number of users and/or they don't really use the
calendar that much, give the MS migration wizard a shot.
Compusven - Email shuttle is the one I liked. it is simple and fast.
I have about 8500+ users to migrate, so any little issues would quickly slow
the project down.
please feel free to email me offline if you want any info on the migration.
keep in mind that you can migrate an account for a test run as often as you
like. it doesn't impact the GW account at all, and when it gets into
exchange, delete the mail account and migrate it again if you want.
Todd Seagraves
remove_todd.seagraves@gbe.com_remove
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:%23tSrRpzlEHA.748@TK2MSFTNGP11.phx.gbl...
> As with anything, it depends.
> However, Microsoft has it's reasons for only supporting a particular
> version. Something along the lines of testing I would guess. Whatever
> doesn't work under later versions may or may not be something you're
> willing to accept as part of your migration. If you find something that
> doesn't work, you'll not be able to call Microsoft and expect them to
> help, right? Third party has the added benefits of not only working, but
> being supported and recommended.
>
> Al
>
>
>
> "W" <anonymous@discussions.microsoft.com> wrote in message
> news:984701c49737$cd1c0ea0$a501280a@phx.gbl...
>> Greetings,
>>
>> We are looking to migrate from a GroupWise 6.5 system to
>> Exchange Server 2003. Once the migration has taken
>> place, the GW server will be taken offline. I have read
>> that the Microsoft wizards only support migrations from
>> older versions of GroupWise and if you have GroupWise 6
>> or 6.5 I should go with a third party migration tool.
>>
>> Is it true that I need to go third party? Or can it be
>> done in the MS wizards?
>>
>> Thanks
>
>