Thanks Dan...the info you provided on what does/doesn't work is very valuable to me. Sounds great that you only had 150 accounts to migrate over a weekend. Unfortunately, we have about 1500 mailboxes so we probably could not accomplish in a weekend. We are also looking at the option that Joe pointed out, where a product similar to Messaging Architects is used to help get the info migrated over.
>>> Dan Abernathy <[email protected]> 8/14/2010 7:37 PM >>> Lori, We just did this about a month ago, and decided to do a “hot” cutover spanning a weekend. We were migrating from NetWare/eDirectory as well as GroupWise, we used the Quest tools to do it, and for the most part it worked great. We were able to bring over personal GroupWise archives into Outlook .pst format – if you do that it’s good to run a standalone GWCheck on the archive first before running it through the Quest migrator. The biggest gotcha we had was the Frequent Contacts address book in GroupWise. It self-populates, so your users are almost certainly making use of it whether they’re aware of it or not, and it’ll be a mess of old/bad contacts mixed in with good ones. Once migrated over, it did –not- show up as a contacts folder in Outlook that people can select from when composing mail. So we’ve had to tell people to click Contacts in Outlook, and look through Frequent Contacts and Move good ones into the “Contacts” folder. We also had issues with some personal distribution lists not working correctly (“this address is invalid” for several entries), which could usually be fixed by opening the group and clicking Update Now. We had no issues at all with peoples’ calendar items converting to Outlook, though we did have to re-create a couple of shared calendars that we had set up as “dummy” users, e.g. Sales Group Calendar that half a dozen people had proxy access to so they could post itineraries on it. We also recreated our resource/conference rooms. You didn’t say what version of GroupWise or how large your installation is; we’re small, about 150 email users spread over two GroupWise post offices in two cities. We went from GroupWise 8 to Exchange 2010. We brought the server hosting the smaller of the two GroupWise post offices to the main office on Friday evening so we could avoid trying to migrate their GW data over the WAN. Dan From:Lori Binner [mailto:[email protected]] Sent: Friday, August 13, 2010 1:46 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 - A Practical Approach Hi Joe- I'm hoping you'll post how your migration goes to the list so we can see how things went. We're on GroupWise too (it's been our only email for over 12 yrs now) but the rest of our network for everything else has migrated from NetWare to MS for a few yrs now and we'll be going to Exchange in the future, just not exactly sure when yet. I view this list trying to gain any bit of knowledge I can about Exchange to try and help. We're having a difficult time deciding what's best to get our GroupWise appts/scheduling and emails to Exchange due to the calendaring/scheduling/busy searching being used VERY heavily here. We had a test environment with the MS Connectors/API gateway (to see if that could run for a few months while we slowly migrate users) and also tested Quest for getting their data migrated, but determined that a slow migration trying to rely on this old/unsupported technology was not the best from a user stand-point as their are some drawbacks to using this for appts. So looks like a very quick weekend or shortest migration possible will work best. Although our users seem to do better with slower phased approach, we may have to bite the bullet with as quick a migration as possible due to the scheduling. Thanks, Lori >>> Joseph Heaton <[email protected]> 8/13/2010 1:31 PM >>> I haven't gotten any books yet, but I just finished an Exchange 2010 class, in preparation for our migration from.... Groupwise. Finally getting off the Novell side of the house. >>> Jason Gurtz <[email protected]> 8/10/2010 6:49 AM >>> Yea, I think you may be right; it's pretty short too. We're also going to be making the same migration. Hopefully have most users on Office 2010 too. Life is good. ~JasonG > -----Original Message----- > From: Maglinger, Paul [mailto:[email protected]] > Sent: Tuesday, August 10, 2010 09:37 > To: MS-Exchange Admin Issues > Subject: RE: Exchange 2010 - A Practical Approach > > I thinking more like Chapter 10. We're moving from 2003. > > -----Original Message----- > From: Jason Gurtz [mailto:[email protected]] > Sent: Tuesday, August 10, 2010 7:50 AM > To: MS-Exchange Admin Issues > Subject: RE: Exchange 2010 - A Practical Approach > > The 911 page book plopped on my desk yesterday. I'm starting at Chapter > 14... :) > > ~JasonG > > > -----Original Message----- > > From: Maglinger, Paul [mailto:[email protected]] > > Sent: Monday, August 09, 2010 14:32 > > To: MS-Exchange Admin Issues > > Subject: OT: Exchange 2010 - A Practical Approach > > > > Just got in my Exchange 2010 books! One of them is Exchange 2010 - A > > Practical Approach. A short read at 182 pages, I'm hoping this will > get > > me up to speed enough to get a server up and running to play on, then > on > > to the 911 and 813 page books for the nitty-gritty. A quick thumb > > through looks good, and MBS is the Technical Reviewer. > > > > -Paul > > > > > > This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this e-mail in error, please notify the sender immediately; disclosing, copying, distributing, or taking any action in reliance on the contents of this information is strictly prohibited.
