MS Exchange 2010 Replacement of failed Server
Posted on 2014-03-12
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!