Yeah - I'd do exmerge. But then again, I've done it that way every time I've done one of these. And my boss didn't call me Iron Chef Migration for nothing. ;)
Those sizes are small enough that MSW doesn't buy you anything. ------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:will.zimmerman@;ihrco.com] > Sent: Thursday, October 10, 2002 3:08 PM > To: Exchange Discussions > Subject: collapsing Orgs > > > We've recently gone through a merger, and I've been tasked > with collapsing > the other company's 5.5 org into our 5.5 org. My first > thought was the Move > Server Wizard, but I started having second thoughts after seeing the > simplicity of their setup. I'm wondering if it's worth > taking the risks > involved with MSW, so I'm leaning towards just exmerging the > entire org out > of simplicity, and wondered what some of you thought. Here's > a rundown of > the collapsing infrastructure: > > 2 sites, single server in each. > 300 mailboxes in one, 200 in the other IS sizes of 7 and 5 gigs > No public folder usage worth worrying about > No custom or third party apps interfacing with Exchange > All clients connecting via MAPI > > > > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:leave-exchange@;ls.swynk.com > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:leave-exchange@;ls.swynk.com Exchange List admin: [EMAIL PROTECTED]
