Exchange 2010 Retirement

Hi Experts.  

We recently moved to a hosted Exchange service and it is 100% not connected to our on-premises Exchange or active directory.
I'm in the process of retiring our on-premises Exchange and am making great progress.  
Before I move forward with the next step, I wanted to check with the community and see if there is anything I'm missing.

I have 1 Mailbox Server and 2 CAS servers left.  
There is 1 Mailbox DB left and it does NOT contain any more user mailboxes - all disabled and retention has passed.
I do see a single entry under Recipient Configuration | Mailbox and that is the Discovery Search Mailbox bound to the single remaining Mailbox DB.  That's it.
Furthermore, under Organization Configuration | Mailbox, I see the 1 Mailbox DB AND Public Folders (which were never used).

Question # 1- Can I go ahead and simply uninstall this last Mailbox server since it only has that Discovery Search Mailbox tied to an otherwise empty first mailbox database and an empty public folders db?  I'm worried about missing some pre-step and getting into a messy situation mid-way through the uninstall of this last Mailbox server.


For the 2 CAS servers, there is a CAS Array defined in DNS (no load balancing being used)

I assume I can simply retire the CAS array and then uninstall gracefully (CAS2 and then CAS1).

Any other special care when I uninstall the final Exchange server (CAS1) from the organization?  
dpmoneyAsked:
Who is Participating?
 
dpmoneyAuthor Commented:
Just circling back on this - I was able to uninstall Exchange 2010 from our environment.  Points going to MAS for providing the most input.  I ended up doing the following:

Delete all mail enabled contacts
Delete all main-enabled security groups
Delete Discovery Search Mailbox (using right-click | remove method) which also deleted AD account
Remove 1 system arbitration mailbox
Other 2 had to be disabled
Deleted Mailbox database
Tried deleting Public Folders database.  Despite nothing in use, it said it had some replicas (I suspect from old 2003 migration).  I ended up dismounting, moving all database and log files, re-mounting and letting it create a clean empty public folders, then removed it no problem at all
Uninstalled Mailbox server
Uninstalled CAS server (final Exchange box!)
0
 
FOXActive Directory/Exchange EngineerCommented:
You can delete the discovery mailbox.
As a precaution before uninstalling I would turn off all exchange services and verify if you have any issues before hand.
0
 
Exchange UserSystems AdministratorCommented:
Do not uninstall the role straightaway. Turn off your services first as Foxluv suggested and then after a few days, turn off your server for a week atleast and monitor all the processes which are dependent on email server. Once you see everything is working fine, you can uninstall the exchange server.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
MAS (MVE)EE Solution GuideCommented:
Remove SCP to ensure your internal client will not connect by SCP instead use the DNS/Autodiscover method.
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri $Null

Open in new window

If you are not using on-prem anymore you can delete the arbitration mailbox by this command and uninstall Exchange from Add/Remove programs.  Stop the Exchange services for couple of days to be safe before uninstall.
get-mailbox -arbitration | remove-mailbox

Open in new window


Please check this for more details
https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx

Thanks
0
 
dpmoneyAuthor Commented:
Thanks.  There is nothing utilizing Exchange in the building anymore.  The 2 CAS boxes have been off-line for the past 2 months so we are definitely at the point where I can remove it.  There is NOTHING using these servers and as noted above, all user mailboxes are long gone and even the mailboxes databases are all gone except for this last one which has nothing but the discovery mailbox on it.  

Taking that all into account, does it sound like I can just delete the discovery mailbox and do the uninstall from Add/Remove Programs?  

When done, I'll just have to deal with 2 CAS boxes.
0
 
dpmoneyAuthor Commented:
@MAS....thanks.  Every single Outlook client in the building has had their Outlook profiles rebuilt to utilize the 3rd party hosted email system.  No one is connecting to the internal CAS defined in the SCP because I had the NICs of both CAS servers off-line for past 2 months.
0
 
dpmoneyAuthor Commented:
Regarding the Public Folders, should I remove that database first or will the uninstall of my final mailbox database server remove it?
0
 
MAS (MVE)EE Solution GuideCommented:
If your CAS is down for few 2 months you can uninstall it right away as CAS server is your client interface.

Regarding PF. EIther you move to cloud https://technet.microsoft.com/en-us/library/dn874017(v=exchg.150).aspx
or delete it before uninstalling.

Thanks
0
 
dpmoneyAuthor Commented:
@MAS, thanks.  

We do not use Public Folders (never did on premises) and do not with our new 3rd party hosted environment so that should be all set.  I will remove the Public folders database before uninstalling.

For the Discovery Search Mailbox, should I right-click and choose "Disable" like I did for all the users OR should I right-click and do Remove (which will also remove the corresponding AD account I think).

If I right-click and do disable to get rid of the mailbox, will the Exchange uninstall remove the DiscoverySearchMailbox account from AD?
0
 
dpmoneyAuthor Commented:
*** UPDATE ***

I am down to just 2 servers:

1 CAS Server
1 Mailbox Server

The mailbox server has 1 mailbox database and 1 public folder database.
The mailbox database points to the public folder database as it default
The mailbox database has no user mailboxes
The mailbox database still has a the discovery search mailbox
There are also 3 arbitration mailboxes still in existence

This is a simple single domain environment.  We do NOT use Exchange at all anymore and all I need to do is uninstall the final 2 servers.  

Since it will be difficult to award points to so many people who have contributed, I will award points to whomever can give me a clear path to take so I can get these final 2 boxes gracefully uninstalled.  

Which server should I uninstall first and what power shell commands should I run at this point.  

Thank you!!!
0
 
MAS (MVE)EE Solution GuideCommented:
1.Unistall Exchange CAS first.

a. Delete the search mailbox. If you want you can delete it from ADUC. Search will be there in office 365 by default.
b. Delete mailboxdatabase.
c. Delete Public folder database

2.Then uninstall mailbox server.

Thanks
0
 
dpmoneyAuthor Commented:
@Mas - thank you.

I'd like to delete the search mailbox gracefully from PowerShell or from within the EMC using either:
 
 Right-click | remove
 Right-click | disable

I'm leaning toward remove because I don't want the discoverysearchmailbox AD account lingering after the discovery search mailbox is gone.  Is this safe to choose remove?

Will the uninstall of the mailbox server remove all the arbitration users in Active Directory?

Interesting that you suggest CAS uninstall first.  When I installed the environment about 4 years ago, I recall reading the first role you should have setup is a CAS role.  Shouldn't I have the CAS also be the final server in the environment before completely removing Exchange.  Any harm in doing it that way?
0
 
dpmoneyAuthor Commented:
Just checking back again...I won't have an opportunity to resume work on this until late next week and will post an update at that point.  Thank you.
0
 
dpmoneyAuthor Commented:
I did it slightly different and had to search for more details, but MAS pointed me in right direction.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.