Thanks. I don't have licensing for Exchange 2013, so that's not an option.
We're small enough that several hours downtime on a weekend night wouldn't be a big deal. If I do go the P2V route, it would definitely be a cold migration so that I could spin the original back up in case of problems. On Mon, Sep 9, 2013 at 6:54 AM, Sobey, Richard A <[email protected]>wrote: > In my opinion, stand up a new server and migrate your data. It’ll be > cleaner, you won’t have all the old hardware drivers knocking about using > resources, and the outage for your users will be almost non-existent.**** > > ** ** > > My only reservation will be having to set up a new PF database and > replicate the content across, but only because I hate PF/replication with a > passion.**** > > ** ** > > Have you considered the option to go to Exchange 2013 CU2?**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Richard Stovall > *Sent:* 09 September 2013 11:33 > *To:* [email protected] > *Subject:* [Exchange] Exchange 2010 P2V?**** > > ** ** > > I am retiring the hardware my single Exchange 2010 server lives on.**** > > ** ** > > I have a shiny new Hyper-V 2012 deployment and I'm thinking of > virtualizing Exchange. Are there any strong thoughts out there about doing > a P2V of the server versus standing up a brand new one and moving the > mailboxes and public folders? We have ~50 users and the databases are > ~350GB in total size.**** > > ** ** > > I do not have SCVMM. (Can't afford it.)**** > > ** ** > > Cheers,**** > > ** ** > > RS**** >
