Solved

MS Exchange 2010 Replacement of failed Server

Posted on 2014-03-12
7
365 Views
Last Modified: 2014-03-13
Our Exchange Server has died a horrible, miserable death. We have arranged a decent burial for it, including the services of a lovely soprano to sing the requiem, but we obviously need to replace it first.

Only problem is, we've built the new Server (on 2012, the last one was 2008 but we don't have the RAID drivers for 2008 for the new one) but when we install Exchange it keeps trying to connect to the dead Server for some reason and we can't get it not to.

If we attempt to add a new exchange forest we get stuck because the Server wants to know where to get its "remote Powershell" from? Apparently, this is a Microsoft Account if you do it from the web (the only available drop-down option), but we've not got one that I can use (all the accounts I've tried have not had permission).

Moreover, we don't want to do Powershell remotely - why can't we just do it locally?

We've been working on this for too long, now and we really need to get things moving. Any assistance would be greatly received!

Thanks!
0
Comment
Question by:winstalla
  • 3
  • 3
7 Comments
 
LVL 24

Expert Comment

by:-MAS
ID: 39922794
0
 

Author Comment

by:winstalla
ID: 39922930
I have tried this now, but sadly I've had to re-re-flatten the 2012 server, so exactly how it will work when it comes back up, I have no idea.

I assume, now that the mail Databases have been removed from the AD, I have to create new mailboxes for every user? Is there a quick way to do this?
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39923099
If the server died you should have recovered it, rather than trying to do a new installation. That will bring everything back and then you just need to restore the databases. Removing the server from the domain isn't really a good idea and is always the last thing you should try, rather than the first.

Simon.
0
6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

 

Author Comment

by:winstalla
ID: 39923114
Agreed, but the server is not loading at all. It doesn't even load the BIOS! Everything is dead on it, so we've had to replace it.

Is there a quick way to recreate the mailboxes from AD?
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39923659
You don't understand.
I wasn't referring to recovering the physical server, but doing a recovery installation of Exchange. This process is well documented and means you can recover Exchange in less than 90 minutes.

If you haven't damaged the domain configuration, install Windows on a new machine using the same name as the original. RESET (not DELETE) the Computer Account and join to the domain. Install Exchange pre-requisites, then install Exchange 2010 from the command line with the recovery switch.

You can then restore the database.

However what I tell all of my clients is the same thing I will tell you - if a server fails, there should be only one thing you do - call Microsoft support. For their fixed fee they will help you recover the server and get everything that can be found back. The longer you leave it before calling them, the more difficult it is to have a successful recovery.

Simon.
0
 

Author Comment

by:winstalla
ID: 39923726
And here's where it all falls apart. The Exchange Server was sticking in the AD and other forums suggested using ADSIedit to remove it. Thus damaging the AD records, I assume because even a fresh attempt at an Exchange 2010 install fails at the Hub Transport install because it says
"Database is mandatory on UserMailbox. Property Name: Database"

Open in new window


Checking the ADSIedit again, there is no homeMDB entry because, under the new Server name (which is the same as the old Server name) there is only a CN=Protocols, no entries exist for CN=Information Store or CN=Microsoft System Attendant or anything else that should be there.

Notwithstanding, we are waiting for Microsoft to call us. We're beyond anything we can think of now!
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39924427
I think Microsoft support is now the best option.
It is a pity you did anything in adsiedit (people seem very quick to go for that "solution") as a dead Exchange server is very easy to recover from, if everything is in place.

Simon.
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now