Quantcast
Channel: Force removal of Exchange 2010 CAS Server
Viewing all articles
Browse latest Browse all 20

Force removal of Exchange 2010 CAS Server

$
0
0

Force removal of Exchange 2010 CAS Server

 

Over the past two weeks I have had a number of Exchange issues that were caused by an underlying storage problem on a NetApp filer. A failed datastore migration by the storage team resulted in a DC BSOD on reboot. This caused a stress on AD that manifested itself in elevated CPU on the CAS servers. All this is resolved and performance is working ok. During that time we have generated a self inflicted problem A colleague of mine tried to build another CAS server thinking this would assist rather than understanding and dealing with the root cause. The install of Exchange 2010 succeeded but it failed when SP2 was installed. My colleague then removed the server from AD. Although the server doesn’t have Exchange installed, as it failed when SP2 removed Exchange but before SP2 is applied Exchange again. When I test AutoDiscover I see some of the connection points are referencing the new/failed CAS server. The server is also visible in the EMC.

 

My plan would have been to carry out a DR install of the server if the AD computer object was there, then uninstall Exchange so all the binaries are removed correctly and all the connection points are removed within the Exchange environment. I can’t uninstall Exchange from the server. I can’t install Exchange as a fresh install as the environment is aware the server has/does exist in some way. The only option I can see is to rip it out via adsiedit. I am happy to do this but want to make sure all the connection points are removed for OAB for example.

 

Any ideas on the process we need to follow?


Viewing all articles
Browse latest Browse all 20

Latest Images

Trending Articles





Latest Images