Exchange server lost

I may have lost our Exchange 2003 server after a RAID controller failure.
I am trying to make the fastest backup plan possible to rebuild in case the replacement controller doesn't bring the server back online.

I can make a clean Exchange 2010 server install on a 2008 R2 server, and then import everyone's .PST files into it. Would that be the fastest way?

Thanks.
raffie613Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
if you have a good backup, i would build another 2003 server with exchange installed in DR mode

Recovering a Failed Exchange 2003 Member Server Using the Disaster Recovery Switch
http://www.msexchange.org/articles-tutorials/exchange-server-2003/high-availability-recovery/Recovering-Failed-Exchange-2003-Member-Server-Using-Disaster-Recovery-Switch.html

AD would have the users' mailbox pointing to the 2003 server so not as simple as building a 2010 server and importing pst files (which likely isn't updated to the current mailbox at the time of the failure)
0
raffie613Author Commented:
problem is i don't have the installation disks for the 2003 Exchange software.

Would making a new exchange server 2010 and importing pst into new user mailbox work ?
0
Seth SimmonsSr. Systems AdministratorCommented:
that's a problem
importing pst files into a 2010 mailbox can be done with powershell

Create a Mailbox Import Request
https://technet.microsoft.com/en-us/library/ff459261%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396

problem is with AD since each user object points to the mailbox on the 2003 server
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

raffie613Author Commented:
but wait, if I just create a brand new exchange box for each user from scratch , then all i am doing is upload their pst file into their newly created exchange box. that happens all the time. what does this have to do with user objects?
0
raffie613Author Commented:
ok Just purchased office 365 for off site Email. However outlook keeps trying to find the old exchange server. I have even typed in the new exchange server settings manually and it is still not finding it. like it keeps looking for the old server. any idea why? I no longer even care about the old email.
0
raffie613Author Commented:
Seth,
I am assuming that the issue i am having is what you were referring to. Is there a way to get the user objects to stop pointing to the exchange server 2003?

I even tried creating a new user and that didin't seem to work.

Please help.
0
Seth SimmonsSr. Systems AdministratorCommented:
Is there a way to get the user objects to stop pointing to the exchange server 2003?

you might be able to change the AD attributes but is a very long shot and no guarantee it would work
also would be extremely tedious depending on the number of users
i wouldn't waste time on it
0
Seth SimmonsSr. Systems AdministratorCommented:
you are better off creating a new domain and starting from scratch and importing what you have for pst files - probably much simpler than trying manual recovery methods that would take longer and could create a bigger mess

since you have office 365 you can work with that as a base for users' mailboxes
your AD will be a mess with the now defunct 2003 server configuration
how many users/computers are we dealing with here?
0
MASEE Solution Guide - Technical Dept HeadCommented:
Agree with Seth
You better install a new domain controller and Exchange(tools if required) to make your life easy.

Get the PSTs imported.
0
raffie613Author Commented:
ALSO the few machines we have that are not joined to the domain, are giving the same errors. they too are only looking for the other exchange server.
I checked the DNS settings and didn't notice anything in there but that is the only thing I can think of that would be having any computer sitting on the network point to the old exchange server.

Ideas?
0
raffie613Author Commented:
we have about 28 users
0
raffie613Author Commented:
Any ideas as to why the computers not on the domain but sitting on the network are also having the same errors with outlook connecting to the new exchange office 365 server?
0
raffie613Author Commented:
by the way, I wonder if this has anything to do with it... but the domain was created originally with the same name as the website. in other words, contoso.org is the internal domain name as well as the external office 365 Email and the website.
Would this be contributing to the issue maybe?
0
Seth SimmonsSr. Systems AdministratorCommented:
the loss of the exchange server would not affect computer accounts on the domain, only user accounts since the AD info for the users is pointing to the old exchange server
0
raffie613Author Commented:
but I am telling you that I am still getting the same issue where the computers that are not in the domain are still trying to connect to the local exchange server that is not there. Would this have anything to do with what I mentioned to you about the local Domain name?
0
raffie613Author Commented:
Another experts in another question said it would be easier for me to just clean the old exchange server Metadata on my remaining DC . Does that make sense? How do I do that? Remove all metadata remnants of the old exchange?
0
raffie613Author Commented:
They said all I need to do is clean up the MEtadata of the old exchange server in AD DNS using the Active Directory Tool in Sites and services?
How do I do that and search for all records of the old exchange server?

Thanks.
0
MASEE Solution Guide - Technical Dept HeadCommented:
If you want you can go ahead with that.
If I am in your place I would start from scratch as suggested by Seth.
Your AD will be clean and error free.

 If you clean up you may find warnings/errors in your server event viewer.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
raffie613Author Commented:
i just used ADSI to clean out the metadaat of the old exchange server in the DNS portion and it worked. also created an internal dns record pointing to office365 autodiscover.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.