exchange 2007 - Moving accounts to new server

You will need to use something like Kernel EDB to extract the mailboxes from the EDB and then import the PST files.

See here: http://www.nucleustechnologies.com/edb-to-pst.html

thats not right i know you can use powershell......


any help?

You can't if you are restoring to a different Exchange Organisation/ActiveDirectory.

Like I said, you will need to use a 3rd party took to extract the mailboxes to PST.  You can then import them using powershell.

if its a new domain and as long as the original is still there, create a trust between the 2 domains. and as long as you have the rights go into either the exchange admin tools or ad users and computers (i cant remember which one as im not sitting in front of the console) and there should be an option to move to new exchange server. all the data and so forth should move as long the trusts have been setup correctly and then decomission the legacy domain and server if no longer needed.

You cannot create trusts in SBS!!

well, you dont have to get all pushy "demazter" i prefer OS's not lock-down mini-small versions. so i dont normally work on SBS servers..

It's not pushy, I just don't like people giving bad/wrong advice.

If you are not familiar with the technologies, don't post in the question.

Just to go on the record here, demazter is 100% correct. The built-in options to do what is wanted don't apply here. You cannot create trusts with SBS so you can't move the data, and the other common method...mounting the database in a recovery storage group...is dependent on both exchange servers being part of the same AD forest, which also doesn't apply.

You can use a 3rd party utility to extract data, or you can use your old server if it is intact to export the mailboxes.

-Cliff

Hello,

Another option here is to build a recovery server. Build a server with the same name as the original server and promote it to a DC using the same domain name as the original forest. Install Exchange and then restore the database. You can then export the mailbox.

I'm simplifying the process here but these are the major steps.

JJ

Exchange 2007 database portability should allow you to mount the databases on the new server, as long as it came from Exchange 2007 to begin with.  Did it?  After that, Guid or not, there should be a way to map users to mailboxes.

SBS presents a few unique problems, but database portability is one feature that makes D.R. on Exchange 2007 and now on 2010 very easy.

PLEASE MAKE SURE that you zero out the logfiles if the databases dont mount.

Cliff is correct, I was assuming you had at least a Domain Controller from the old organization.  If you DO, what you could do is go back to that and start a SWING migration....where you capture a copy of that Active Directory on temporary hardware using a workstation running Windows server 2008 and DCPROMO it, disconnect this workstation from the network holding the original server you started with so that it no longer updates it (you can do this by just unplugging that server from the network), and then cut out the domain controller that you had originally using Active Directory metadata cleanup as if it had failed.  Once you have this workstation running a clean directory (with your old Exchange org objects in it, it doesn't matter that Exchange is not running), you can run a Windows SBS upgrade install.  Jeff Middleton over at SBSMIGRATION.COM has a TREMENDOUS walkthrough document that is incredibly easy to follow that documents this process in great detail.  If you purchase a migration kit, it comes with support from Jeff Middleton (the author) himself, as well as tools to clean up your Active Directory and Exchange installations to get everything back WITHOUT having to go to PST (although PST remains an option in the SBSMIGRATION).

If you don't want to go through ALL of that, you could just use ONTRACK POWERCONTROLS, a utility that allows you to mount the RAW EDB files and extract everything to PST, including public folders.  Not an inexpensive utility, but if you need your data it's the path of least resistance.

If you have an existing Domain Controller from the domain that this Exchange system came from, or even a SYSTEM STATE backup of a domain controller that is reasonably recent, you can reconstruct this environment and get this data back without issue.  If you have a Hyper-V environment, you could create all of these installs on the same server by having multiple VMs talking to each other.

If you have an existing DC from the source domain or at least a SYSTEM STATE backup, reply and I'll give detailed instructions on how to recover.