?
Solved

Removed CAS server still showing in Exchange server list

Posted on 2015-01-22
2
Medium Priority
?
417 Views
Last Modified: 2015-01-22
Infrastructure: 2 x Exchange 2010 in a DAG, 2 x Windows 2008 servers in a CAS array.  All on one site

A couple of months ago, one of the servers in our CAS had some problems, so we decided to rebuild it from scratch.  It was essentially a file and print server that had also been given the role of a CAS member.

We removed it from NLB and shut it down prior to rebuilding it.

We created a new CAS member and added it to NLB.  Everything was fine.

We rebuilt the failed server, without the CAS role.

Now when I look in the Exchange management console (Server Configuration, Client Access) the old server is still listed.  When I run get-clientaccessserver, 3 servers are listed; the 2 that are currently in the CAS, ad the one which was removed.

The command get-mailboxdatabase | ft name,rpcclientaccessserver correctly returns the FQDN of our CAS

How do I get rid of the old server from Exchange?
0
Comment
Question by:Japes
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 53

Accepted Solution

by:
Will Szymkowski earned 2000 total points
ID: 40564506
This role was not removed properly. Because you have already re-created the server that had the CAS role installed, I would recommend using ADSIedit to remove the old CAS entry showing up in the EMC.

- open adsiedit.msc
- open Configuration partition
- expand Configuration
- expand Services
- expand Microsoft Exchange
- expand <SiteName>
- expand Administrative Groups
- expand <Administrative Group Name>
Click on Servers

In there you should see that old orphaned server listed in the.
- right click it and delete it

NOTE: when you are using ADSIEdit be careful. If you delete another other objects other then the ones required you can cause potential damage to Active Directory and other services. Also, Using ADSIEdit is not supported by Microsoft.

In your situation and where you are with your rebuilds this is the most practical way to remove this object.

Will.
0
 

Author Closing Comment

by:Japes
ID: 40564586
Many thanks for your help - it worked like a dream

Jain
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
This video discusses moving either the default database or any database to a new volume.
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
Suggested Courses

719 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