Removing old Exchange Database and instense

Hi,
I have installed a New exchange server 2013 on windows Server 2012 r2 in a old exchange 2010 environment on windows small business server 2011 for migration. Now I removed it due to some problems and format the whole server and reinstalled it on the
same machine. Now it is installed but it shows the old server and database. How can I remove it form this environment.
Thanks
Prashant

Hi,
Kindly let me know, you have reinstalled Exchange 2013 or have you run disaster recovery of Exchange 2010.
---------------------------------------------------------------------------------------------------------------Deepak
Kotian.
MCP, MCTS, MCITP Exchange 2010 Ent. Administrator
Disclaimer:
Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!
All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no right

Similar Messages

How to save old email database, and make a new one

can anybody please lead me to a direction sheet for saving your old email database, making a new one, and then importing the old messages into the new database?
thanks in advance

I have been trying to figure out why my mac mail will start to down load, and then it stops. I have 50 messages that i'm trying to POP and it start out fine, then after 10 or so messages it stops. i have tried to delete the messages from the server to see if there is some specific message that is causing problems to no success.
so now i'm trying to just remove the old Messages and start a new mail data file from scratch. then move the old messages into it, that is if it can be done.

Removing old exchange 2003 routing groups from Exchange 2010.

I have migrated over to Exchange 2010(server2008) from Exchange 2003(SBS2003). I've also already run the uninstall for exchange 2003 on the old SBS 2003 server. The old server itself is still running but exchange has been removed and once I get this fixed
I plan to fully remove the old SBS server.
I now get event ID 5020 and 5006 throughout the day on the new server. From what I've read, this happens because the old routing group connectors still exist.
If I run Get-ExchangeServer I get
Name                Site                 ServerRole Edition     AdminDisplayVersion
SERVER                                   None
Standard    Version 6.5 (Bui...
SERVER2008          hr.local/Configur... Mailbox,... Standard    Version 14.0 (Bu...
Am I correct in assuming that the way to fix this now is to go into ADSI edit and delete records under CN=First Administrative Groups? As in delete CN=Routing Groups and CN=Servers and everything under both of those? I'd try this myself but I'm not aware
of any way to restore those records easily if I'm wrong.
Event ID 5006
Cannot find route to Mailbox Server CN=SERVER,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local for store CN=Public Folder Store (SERVER),CN=First Storage Group,CN=InformationStore,CN=SERVER,CN=Servers,CN=first
administrative group,CN=Administrative Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local in routing tables with timestamp 27/09/2014 1:57:43 PM. Recipients will not be routed to this store.
Event ID 5020The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 server.hr.local in Routing Group CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative
Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local in routing tables with the timestamp 27/09/2014 1:57:43 PM.

Get-RoutingGroupConnector shows nothing. As for the servers group. It has the old server under it as shown in the image I posted above. That's actually what stops me from just deleting it because other guides have said not to delete it if an old server
is listed.
Is the SBS2003 server listed because I haven't ran DCPROMO to remove it from the network yet? I am planning to do this but was waiting till I cleaned up all the errors before transferring the 5 FMSO roles and running DCPROMO on the old server.
DCPROMO isn't related to this, no.
So you removed Exchange already? How? With setup? It should have removed the Exchange Server object then.
It is supported to remove Exchange 2003 manually if required with adsiedit:
http://support2.microsoft.com/kb/833396
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

How do I install a new Exchange account with the same address as my old Exchange account and have my bcc mail not go to the old account?

I have an iPhone 5s running iOS8 and an iPad, up to date. I have recently changed my mail server but not my email address. My "old" mail account is an Exchange account and I have also set up a "new" Exchange account with the same address but with the new mail server details. When I receive outside, third party emails they are routed correctly to the "new" Exchange account but when I bcc myself or receive other emails from any account with my domain name the emails are routed to my "old" Exchange account. I have changed the default account settings to the "new" Exchange account. Also, if I send myself an email from my laptop, through the new mail service provider, it is routed correctly on my laptop but incorrectly on my iPhone and iPad. It appears as though the Apple products have cached my email address and routing and won't look to pick up the new mail server details. I don't see anything in the mail account settings or contacts that allows me to refresh or clear the cache. The result is I now have mail in 2 accounts. If I can get the misdirected mail from the odl account to the new one I will then make the old account inactive. Anyone have any ideas on this one?
Thanks in advance for your time and ideas,
DAA

Can you set up a rule in your old account to forward mail to your new account and then delete it from the old account?
(1012)

Removing old Exchange 2007

Last year I upgraded to Exchange 2010 & all has been working fine.
This year I plan to upgrade to 2013.
Last year I moved everything over to exchange 2010 but could not completely remove all roles from old server which by this time was virtualised. This server has been off for 12 months.
In the exchange management console window on 2010 I can see in the server summary window that it thinks there is still an exchange 2007 server.
I have fired back up my old virtualised version of 2007 & tried to perform add remove roles as it still thinks it has a mailbox role. This fails saying it cannot find it self.
How do I get rid of this server so I can progress with upgrade to latest version?
I have checked ADSIEDIT & cannot see an entry for my old server.
Please help

Unlike Exchange 2003, manual
removal of Exchange 2007 is not supported. However, take a look at these threads..
http://social.technet.microsoft.com/Forums/en-US/exrca/thread/b365aa9b-350f-481a-9222-9e5595946da8
http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/412e2904-839f-4960-970d-6ee281d1d50a
http://support.microsoft.com/default.aspx/kb/927464?p=1
Regards
SK

Removing dead Exchange 2003 and Exchange 2000 Server from the domain

Hi Team,
I have come across a client who wants to migrate to O365 from existing Exchange 2003 environment through the Hybrid Model. I am trying to introduce 2010 Sp3 to the environment. While checking the environment using Exchange pre-deployment found 2 servers
in the environment which is not present on the network now. Client has no clue what they are.
One is Exchange 2003 and the other is Exchange 2000. The problem here is i cannot introduce Exchange 2010 Sp3 unless all the Exchange servers are running minimum Exchange 2003 Sp2.
At present i find only 2 exchange 2003 Sp2 server which are in production. Need kind assistance to move forward.

Hi,
I recommend you follow the steps below:
1. Please upgrade Exchange 2000 and Exchange 2003 to Exchange 2003 SP2 at first.
2. Deploy Exchange 2010 servers in this order: CAS, Hub, UM and Mailbox. For more information, here is an article for your reference:
Exchange 2003 - Planning Roadmap for Upgrade and Coexistence
http://technet.microsoft.com/en-us/library/aa998186(v=exchg.141).aspx
3. Install Exchange 2010 SP3.
Here is an article for your reference.
Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
About a hybrid deployment with Microsoft Office 365 using Microsoft Exchange Server 2010 servers, here is an article for your reference.
Understanding Upgrading Office 365 Tenants for Exchange 2010-based Hybrid Deployments
http://technet.microsoft.com/en-us/library/jj945383(v=exchg.141).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Mounting an old Exchange database file for recovery.

Can we safely and without disturbing the production Exchange 2010 server mount an old database file from a year ago backup using (New-MailboxDatabase -Recovery) to mount the database then recover an old user mailbox.

I believe that is no problem because a newly mounted database isn't pointed to by anything by default since it will have a different name. User mailboxes have static entries for the database they point to.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Can't Remove Old Exchange Server

While going through ADSI edit, I noticed there is an entry for an old Mail Server object in the Domain Controllers OU. It only appears in ADSIEdit and not under AD Users and Computers and it didn't show under ntdsutil either.
I have full permissions under the domain admin account, but when I try to delete it and I get the error:
Operation Failed. Eror code: 0x5
Access is denied.
00000005: SecErr: DSID-031A121F, problem 4003
(INSUFF_ACCESS_RIGHTS), data 0
I've heard that this can be caused by a former Trust Account that is no longer present. Under that objects properties, under the UserAccountControl attribute is 0x820 = (PASSWD_NOTREQD | INTERDOMAIN_TRUST_ACCOUNT)
and also under sAMAccountType 805306370 = (TRUST_ACCOUNT)
I'm not sure what the best process would be to remove this object.
I appreciate any thoughts and future assistance!

Hello,
If you are really sure that you want to remove this date, unchecked the
"Protect object from accidental deletion" and try again.
Regards.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Removing old exchange servers from AD with ADSIEdit

Hello all,
I know this has been discussed MANY times but I wanted to know if the only place these are stored is under CN:Server under Microsoft Exchange? I know this isn't the recommended way but I need to get these removed so I can re-use the old names.

CN=configuration,DC=.example,DC=.COM > CN=Services > CN=Microsoft Exchange > CN=Organization > CN= Administrative Groups > CN=(Groupname) > CN=Servers >
Looks to be correct.
This is where you would the sevrers, but try add/remove programs first, if a uninstall has failed or hasnt move the object then delete from here.Sukh

Exchange 2010 transfer of the license and uninstall old Exchange

Hello everyone,
I had some problems with my old Exchange 2010 as it was freezing from time to time. I decided to install a new Exchang 2010 server. I transferred mailboxes, MX record stays the same and I routed all e-mails to the new server now. I disconnected other server
from the network to test is everything working fine and so far so good.
My bigger concerns are following now:
a) how to transfer license as I wanna use the same license key which old server uses.
b) How to Uninstall old Exchange 2010 server.
In regards to license transfer I don't want to get to the point where I am going to get message that I used the same license key on another server. Do I have to deactivate license on the old server? How do I do that. Maybe uninstallation of it will send
a signal to Microsoft that license is gone. Has anyone come across this kind of issue? So what do you think should I uninstall old server first before I enter this license?
In regards to my second question which is related to the first one. How do I properly remove old Exchange 2010 server. I found some instructions that I should just go to "programs and features" and uninstall it this way or run a setup from CD.
Other instructions says that I should uninstall database over power shell and uninstall public folders etc. I would like to do it as clean as possible as I don't want my new exchange or any of DCs to look for missing Exchange later. Which option properly uninstalls
Exchange 2010 from my domain and from AD. I wanted to add that my Exchange2010 are on Windows Server 2008 R2.
I just wanted to add that I phoned Microsoft to ask about it but they said that I have to pay for support otherwise they can't help me. What would you do first? license or uinstallation of old Exchange 2010? I still have over 100 days of trial on new build
server.

Hi,
1. Arbitration mailbox is used to store organization-wide data such as administrator audit logs, metadata for eDiscovery searches, and Unified Messaging data. To avoid more issues, we recommend to move the mailboxes. And here is a reference about how to
move arbitration mailboxes:
http://social.technet.microsoft.com/wiki/contents/articles/3912.exchange-2010-how-to-delete-the-first-database-and-move-the-system-mailboxes.aspx
2. If the public folders won’t be used in the new environment, we don’t need to move them.
3. For the issue whether the license can be used twice, we recommend you to contact with Microsoft Customer Service to confirm.
4. By default, when Exchange 2010 is installed, OAB is created in the default internal Web site in Internet Information Services (IIS).
For more information:
http://technet.microsoft.com/en-us/library/aa996917(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi

Introduction of New OAB Architecture in Exchange 2013 and Some General Troubleshooting methods

Exchange 2013 is different from previous versions of Exchange server on architecture, some of the old features have been changed. In this FAQ, I will demonstrate the changes on OAB and list a common issue for your reference.
[Agenda]
1. Differences between Exchange 2007/2010 OAB and Exchange 2013 OAB
a. Generation
b. Distribution
c. Download
2. Common issue and troubleshooting
3. More information
[Difference between Exchange 2007/2010 and Exchange 2013 on OAB]
As we know, OAB in Exchange 2007/2010 has 3 points, OAB files generated from MBX server, distributed to CAS server and downloaded to Outlook client. However in Exchange 2013, these 3 points have a little different from previous servers. For example, the OAB
Distribution process doesn’t depend on Microsoft Exchange File Distribution service anymore. Now let me show you the changes of OAB in Exchange 2013.
[OAB Generation]
====================
Exchange 2007/2010:
1. OAB generation server is the specific MBX server which has –server property.
2. If MBX01 is down, OAB generation will be affected.
3. Previous Server using Microsoft Exchange System Attendant service for OAB generation.
4. OAB generation is a scheduled process. By default, OAB files generated at 5:00AM every day.
5. The OAB files which generated from MBX server are located in following path:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
Exchange 2013:
1. OAB generation server is the MBX server that hosts a special type of arbitration mailbox, called organization mailbox. Thus, the same OAB files could be generated from multiple
MBX servers.
2. If one of the MBX server down, other MBX server still have the ability to generate the specific OAB files.
3. Exchange 2013 server using OABGeneratorAssistant for OAB Generation.
4. OAB generation is a throttled process. It depend on the Server workload.
5. The OAB files which generated from MBX server are located in following path:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
[OAB Distribution]
====================
Exchange 2007/2010:
Previous Servers use Microsoft Exchange File Distribution service to distribute OAB files from MBX server to CAS server. The distributed oab files stored in CAS server.
Exchange 2013:
The OAB files doesn’t distributed to CAS server. The OAB files only stored in MBX server.
[OAB Download]
====================
Exchange 2007/2010:
If Autodiscover works fine, Outlook should use OAB URL to get the OAB files and download it.
If Autodiscvoer doesn’t work, authenticated users can also get the OAB from the CAS server local disk.
Exchange 2013:
Microsoft Exchange File Distribution service has been removed from Exchange 2013 and the OAB files stored in MBX server. CAS server will proxy all OAB download requests to the appropriate MBX server.
Outlook also use Autodiscover to get the OAB URL and download it.
[Common issue and Troubleshooting]
Issue: Outlook doesn’t download OAB files automatically. When I try to manually download OAB, get this error: Task xxx reported error (0x80190194): The operation failed.
Troubleshooting:
1. First, please run following command to check the information of OAB Generation Server.
Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like “*OAB*”} | ft Name, Servername, Database
Example result as below:
2. Please make sure the authentication settings and URLs are set properly.
3. Try to verify whether the OAB files generated from MBX server successfully. Path as below:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
4. If all of the settings above set correctly, please try to check Autodiscover. Run “Test E-mail Autoconfiguration” to check whether there is anything abnormal on OAB. If has, please search the error code on MS official documents.
5. If this issue is related to local cache, please try to delete the OAB caches from local PC and re-download OAB for testing. Path as below:
C:\Users\Administrator.CU1(different)\AppData\Local\Microsoft\Outlook\Offline Address Books
[More information]
http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi Techy,
According to your description, I am still not quite sure about your environment. Could you please provide more information about it, such as:
1. How many Exchange servers in your coexistence environment? One Exchange 2010 with all roles and one Exchange 2013 with all roles? Or several Exchange 2010 and multiple Exchange 2013?
2. Are there two sites in your environment? What’s the Exchange deployment in different sites?
3. Please confirm if both Exchange 2010 and Exchange 2013 are Internet-facing.
Additionally, if you are using different namespaces for different services for internal access and external accessing, we need to include all service namespaces in your certificate with IIS service. Personal suggestion, we can follow ED Crowley’s suggestion
to use split-brain DNS in your environment and only use the same namespace for Exchange service URLs.
The following article described the details about how to configure different namespace for Exchange services by using Load Balance in Exchange 2013:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part2.html
Regards,
Winnie Liang
TechNet Community Support

Droid Razr Maxx/Issues with Exchange Sync and Texting

I have a Droid Razr Maxx. Since the KitKat update to 4.4 in May 2014, my Exchange email account will not sync. My Comcast account does. If I power cycle the phone, it will sync the Exchange account for a short time until I receive the following error message: 'couldn't open connection to server due to sec..." When I touch the error message, it just goes away. If there is more of the error message, I'm unable to see it. I have removed the Exchange account and added it back in three times. My IT department indicates they have not made any changes to the security levels, but have fielded several questions from other Android users with the KitKat update. My text messaging service also stopped. I've been reviewing all forums and tried different things, but to no avail. I went to the Verizon store, who just said that there have been 'lots' of complaints about KitKat and that I should buy a different phone. This $200+ phone is only 7 months old. Please help!!

After deleting and adding my Corporate account, visiting the local Verizon store several times, visiting my IT department, and now wiping the phone and re installing all software, the Corporate email still only syncs when I power cycle the phone. We are a BYOD company which means every other phone works with the Exchange account. My phone also worked up until the KitKat update in May 2014. The only recommendation I have received from Verizon is to replace my 8 month old Motorola Razr Maxx with a entirely different phone at full price. The tech I spoke with at Verizon made the statement that she has avoided updating to KitKat given all the customer issues she has had to deal with.
I'm in a technology field and understand when glitches occur, but also expect functionality issues to be addressed. I've been with both Verizon and Motorola for a long time, but very doubtful I will continue this relationship when contract time is up for renewal. I'm carrying my iPad around to get the Corporate emails and the Razr Maxx has been relegated to just being a very expensive phone.

Remove default mail database

Dues to the size of my default mailbox database I created two new mail box databases and moved (using EMC) the existing user mailboxes from the default mailbox into the two new ones (half in each new database). That left me with the Discovery Search
Mailbox which I loved (using EMC) to one of the new databases. Am I now safe to remove the default database or is there something further that I need to do first? I read something about arbitration mailboxes but don't know what those are or if they are
already handled by moving my user mailboxes and the Discovery Search mailbox. When I run "Get-Mailbox -Database" against the default database it shows no objects. I think I'm ready to remove the default database but am nervous about doing that without
checking first.

Hi Don,
Hope you are doing well.
there is nothing wrong in removing your default database but there are few steps / precautionary measure that you need to take before you remove your default database and those are as follow.
Move Arbitration Mailboxes
Move Discovery Mailbox
Move User Mailboxes
Move Archive Mailboxes
If you miss out anything and if you try to remove the Default Database you might face a popup with an Error.
Microsoft Exchange Error
The mailbox database ‘Mailbox Database 0089743213′ cannot be deleted.
Mailbox Database 0089743213
Failed
Error:
This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all mailbox plans
in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox
-Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the
command Disable-Mailbox <Mailbox ID> -Archive. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command Disable-Mailbox <Mailbox
ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID> -Database <Database ID>.
Get-Mailbox -Arbitration | NewMove-Request -TargetDatabase "xxxx" ==> This command will get all the arbitration mailboxes and move them to new database to which you want to move.
Get-Mailbox -Filter { RecipientTypeDetails -eq "DiscoveryMailbox" } | new-moverequest -targetdatabase xxxxxx ==> This command will move the discovery mailbox to your new databse.
You can move the user mailbox from Admin Center or EMS by using the following command.
New-moverequest -identity abc@xyz -targetdatabase "xxxx"
Once you are done with the move of all user, discovery and arbitration mailboxes, dismount the database for couple of days to see if there is still any impact on production (It will not have any impact but best practice is to dismount your database first
and then remove it after couple of days). If you don't have any issues with your production after dismounting the default database, remove it after 2-3 days. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Exchange 2013 finds an old Exchange 2003 server

We have a new MS Server 2012. We are trying to install Exchange 2013
We migrated from an MS SBS Server 2003. We migrate AD over. The SBS 2003 is no longer on the network.
When I try to install Exchange 2013. I receive an error.
Error:
One or more servers in the existing organization are running Exchange 2000 Server or Exchange Server 2003. Installation can't proceed until all Exchange 2000 or Exchange 2003 are removed.
Any and all help is appreciated.

The correct supported method I believe is to ensure that you uninstall the old Exchange server from SBS as part of the migration, before you demote the SBS server and remove it from the domain, otherwise you end up with old records remaining in Active Directory.
If you still have the old SBS server available and it hasn't been demoted then have a look at the steps listed here
http://technet.microsoft.com/en-us/library/gg563804.aspx
If that's not possible the other option is to remove the old records via ADSIEdit as detailed here
https://social.technet.microsoft.com/forums/exchange/en-US/46ca107c-7ece-4da7-8aea-46b705793f37/removing-old-exchange-and-installing-a-new-one however you should be aware that while it reportedly does work this is not a supported method.

Decommissioning an Old Exchange Server

I have a bit of an issue here at my work, I have been asked to decommission our 2003 exchange servers as we have finally finished moving the last of our users off of the old exchange servers and on to our 2010 server. Currently they route between each-other
and I need to ensure that I remove the old servers without causing any issues with the 2010 servers. What would be the correct way to approach this?
Thank You

Hi Neurotox,
Please can check these below,
Remove Exchange 2003 server ====
1- Move all mailboxes and public folder content on Exchange
2003 to an Exchange 2010 environment.
2- Move each OAB generation process to an Exchange 2010 server.
3- Remove the Exchange 2003 Mailbox and Public store.
4- Verify the Internet Mail-Flow is configured to route through your Exchange 2010 transport servers
5- Verify the Client Access services are configured for Exchange 2010. ActiveSync, OWA, Outlook Anywhere, etc
6- Delete the routing group connectors that connect the Exchange
2003 routing groups.
7- If you have Exchange 2003 recipient policies that are only Mailbox Manager policies and don't define e-mail addresses (they don't have an E-mail Addresses (Policy) tab), delete them
8- If you have Exchange 2003 policies that are both E-mail Addresses and Mailbox Manager policies (they have both the Mailbox Manager Settings (Policy) tab and the E-mail Addresses (Policy) tab), delete them
9- Delete the domain Recipient Update Service from ESM
10- Delete enterprise Recipient Update Service from ADSIEDIT.
11- Uninstall Exchange 2003 by using Add or Remove Programs from Control Panel.
12- After the last Exchange 2003 server has been removed from the Exchange 2010 organization, you can also remove the legacy Exchange Domain Servers and Exchange Enterprise Servers security groups.
Thanks,
James

Removing old Exchange Database and instense

Similar Messages

Maybe you are looking for