Removing Exch 2013 in Exch 2010 environment

I have a production Exchange 2010 + UM environment.
Exchange 2013 was installed for migration but the 2013 server seems to have several issues operational issues and needs to be removed and a new 2013 server built from scratch.
What is the best practice here and any documentation available to do this.
Thanks.

HI
First you can try running the below command which will remove the Exchange 2013 server
.\Setup.exe /mode:Uninstall /IacceptExchangeServerLicenseTerms
Also you can try below for manual uninstall.
If you already have Exchange 2010 you will need to remove this Exchange server like Exchange 2010.
After removing all mailbox database & Public folder mailbox database, then from add/remove program
uninstall the Exchange.It‘s similar as we remove Exchange 2010.on adsiedit there will be Exchange 2013 object, you will need to delete this object manually from below location
CN=Configuration,DC=DOMAIN,DC=LOCAL CN=Services CN=Microsoft Exchange CN=Administrative Groups CN=Servers using ADSIEDIT and then disable the associated computer account as well.
NOte: YOu should be careful while dealing with ADSIEDIT and ensure you are removing only Exchange 2013 container. Its better to take a system backup before you play with adsiedit if you are not sure about making this change.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com
Do NOT delete Exchange 2007, 2010 or 2013 servers using ADSIEDIT. That is not supported.
Exchange 2003 was the last version that allowed this, but there was a strong recommendation that it was to be used *ONLY* in specific circumstances.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Similar Messages

Introduce an "passive" Exchange 2013 in Exchange 2010 environment without user or administration impact.

Hi
We wish to introduce an Exchange 2013 server in our existing Exchange 2010 environment.
The Exchange 2013 server is only needed for migration purposes where we wish to leverage the new features of the migration-batch functionality.
It’s important that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, right now, since the customer wish to stay on 2010.
Can you guys come up with anything to be aware of?
Oblivious we disable the Autodiscover SCP for the Exchange 2013 server, so that the clients will not hit this server. Nor will we point any URLs to the Exchange 2013
I can see that a new “Default Offline Address Book (Exch2013)” is created and set as default when EX2013 is installed. We will change this back to the default EX2010.
The server will properly take part in the Shadow Redundancy feature, and is doesn’t seem to be possible to exclude the server or avoid, unless disabling Shadow Reduncancy.
I can only come up with these 3 things that will have a "direct" impact on the environment, but any input will be highly appreciated!
BR,
Martin

Hi,
I agree with Li Zhen’s suggestion. If you don’t migrate from Exchange 2010 to Exchange 2013, we can disable add services in Exchange 2013 and don’t use it any more.
If you want that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, please keep the published server to pointed to Exchange 2010. Then the original configuration in Exchange 2010
would not be changed to the new configuration in Exchange 2013.
If you want to use Exchange 2013, then we can point the published server to Exchange 2013 and configure the virtual directories in Exchange 2013. Though all mailboxes are still located in Exchange 2010, all external requests would be proxy or redirected
from CAS 2013 TO CAS 2010 automatically.
For more information about Client Connectivity in an Exchange 2013 Coexistence Environment, please refer to:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Regards,
Winnie Liang
TechNet Community Support

Installed 2013 into a 2007 environment, cleanly removed 2013 now trying to install 2010

So first, before you flame me, this is in QA!
We installed 2013 into a 2007 environment, then due to shifting business demand, cleanly removed 2013. Now we are trying to install 2010 CAS servers and it goes in fine, reports no errors, but I do not have 'server configuration' on the left pane of
EMC, but I can run any related EMS cmdlet (so not permissions). On the org health page all the info is listed as 'unavailable'. I'm thinking something is left over in AD's config container, but I can't find it. Help?

Hi,
From your description, it seems to be the obsolete information is cached in an EMC file in the Windows profile with whom user has logged into the server. I recommend you follow the steps below for troubleshooting:
1. Go to the following location and delete the Exchange Management Console file. (Note: Before deleting it, please do a backup.)
C:\users\<specific user>\AppData\Roaming\Microsoft\MMC\Exchange Management Console
2. Close EMC and Reopen it.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exch 2013 - Someone Relaying Email Through Server

Exch 2013 - Someone Relaying Email Through Server, there are thousands are emails in Queu. Please help me urgently

You need make sure your Receive connector is not allowing IP address \ host from the internet to open relay using it.
If you open the tracking log you will be able to see which connector is allowing the relay.
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Migrating to Sharepoint 2013 from 2010 - Can you use the same URL for the Web Application without affecting the 2010 environment?

Hi,
I am currently trying to migrate our SharePoint 2010 environment to SharePoint 2013. The first thing I'm doing is creating a 2013 development environment to verify that this migration goes smoothly. I'm also doing this so that we will have a testing environment
after the upgrade to 2013 is complete.
So here is my question: I have a 3 tier farm including; 1 app server, 1 wfe, and 1 sql server. I have made a copy of our SharePoint 2010 database and installed that on our sql server 2012 sever (This new environment is on 3 completely separate servers from
our 2010 environment). I have also installed the prereqs and configured SharePoint 2013 on the App server and wfe servers, as well as configuring the necessary service applications (I have created a completely new 2013 database where I will migrate my 2010
database content when I'm ready).
I am now at the point where I need to create a new web application on the 2013 app server, where I will be migrating the copied 2010 database. (Also note that we have a 2010 development site called https://[email protected])
When I go to create a new web application in our 2013 dev environment, can I use the same url (https://[email protected]) to create this web app, or will this screw up our current 2010 dev environment?
I'm new to SharePoint migrations, so I apologize if this is a stupid question.
Thanks in advance for any insight you can share on this!
Boe Barlage

So, what you are recommending is that before I create a web application in my new 2013 environment, I need go into my hosts file on my 2013 app server and alter it to point to my 2013 wfe.
Then after I do that, then I can create my new web application on my 2013 app server with the same url as my 2010 testing environment
(https://[email protected]).
Then after that I should be able to access my new sharepoint 2013 environment at the same URL (https://[email protected])?
I must be missing something.
In your first reply, you told me to alter the host file on my 2010 app server and point it to my 2010
wfe (I guess I thought it probably already is). You also told me to alter the host file on my 2013 app server and point it to my 2013 wfe.
so I am confused on after I do this, what url would I access my 2010 test environment, and what url would
I access my 2013 test environment?
I am fine with having my test environment as a different URL until I am totally ready to roll everything over and kill the 2010 site. But I want to make sure that when I migrate my database, none of the site links are broken.
I also want to make sure that if I proceed this way, I want to be sure that I will be able to modify the URL to what my 2010 environment is (without a lot of headaches) when I am ready to kill the 2010 site.
Thanks again for your help, it's much appreciated!
Boe Barlage

Exch 2013 SP1 How to create new mailbox account for multiple users exist in active directory in one go?

Hi,
First let me explain my Exch 2013 SP1 Multidomain set up.
1. DA as Forest Root domain, having schema master domain role installed.
DB as Tree Root domain in above forest
DC as Child domain in Tree root domain.
Brought 1 machine in Child domain and in stalled Exch 2013 SP1 on it.
Now i have created 100 users in child domain, but i am not getting a option to enable Exchange mailbox for all 100 users in one go. (Also unable to do same on normal set up having one DC and Exch 2013 SP1 server)
Could you please help me do it.
Thanks & Regards,
Sudhir

Dear Sudhir
Please try this through Exchange management shell and it will help you
Get-User -RecipientTypeDetails User -Filter { UserPrincipalName -ne $Null } | Enable-Mailbox
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

How to introduce exchange 2013 mailbox server in an existing Exchange 2010 Environment

Hi All,
we are planning to install exchange 2013 mailbox server in an Exchange 2010 environment. we have 3 MB servers, 1 CAS 1 HUB which is installed with Exchange 2010 SP3 Enterprise Edition. how to install new exchange server 2013 and i have to add the 2013
servers in to existing DAG and migrate all mailboxes in to 2013 server. Please advise me from the scratch. also will it be create any impact in my existing setup.
Thanks, Venkatesh. "Hardwork Never Fails"

For a step by step follow the deployment assistant
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exch 2013 Installation Error "Database is mandatory on UserMailbox"

A previous admin installed a trail edition of Exchange 2013 in our 2007 environment for testing. When he tried to uninstall it there was an issue and it left some Exchange AD debris in the Active Directory structure.
Surprise, but now he is nowhere to be found.........
Now the company is going to upgrade and we cannot install Exchange 2013 because of these mailbox errors. The old server and database has been cleared out of ADSI and the one user that was in the old 2013 database has had all the Exchange attributes
cleared from their AD profile.
We are still getting the "Database is mandatory on UserMailbox" error when I try to install Exch2013 on the new server. I tend to think there is some other mail-enabled object in AD that is causing the conflict, but I cannot find it.\
Obviously I cannot nuke the entire ADSI Exchange folder, because I still need 2007 to work. :-)
Any help would be appreciated......

Exchangesetup.log file should indicate which mailbox is that. Then rehome it using adsiedit homeMDB attribute on E2007 database, or perhaps remove that, if it is system mailbox...
Refer: http://social.technet.microsoft.com/wiki/contents/articles/25342.exchange-2013-setup-error-database-is-mandatory-on-usermailbox.aspx ---
However you won't be able to use Powershell to get info as you don't have any Exchange 2013 server in org...
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exch 2013 SP1 Mutidomain set up. mail enabled user shows Forest Root Domain email address.

Hi,
First let me explain my Exch 2013 SP1 Multidomain set up.
1. DA as Forest Root domain, having schema master domain role installed.
DB as Tree Root domain in above forest
DC as Child domain in Tree root domain.
2. After set up, I ran 'netdom query fsmo' on each DC. It displayed schema master role on forest DC and domain role on individual DC on which command was run.
3. Now to install Exch 2013 SP1, ran appropriate command on forest DC (i.e PrepareAD, Prepareschema and alldomain).
4. Brought 1 machine in Child domain and installed Exch 2013 SP1 server on it.
Now, when I access ECP, Create user, new mailboxdatabse etc. options available only if login to ECP by ForestRootDomain\administrator credentials. please confirm.
while creating new user, it shows User Login Name with Child.TreeRootDomain.local default but after creating user, it shows [email protected] as Email address. Please confirm.
Thanks and regards,
Sudhir

Logged on Exch machine by child\administrator user credentials.
Unabel to get Set-ADServerSettings -ViewEntireForest $true command in exchange powershell.
can get only Set-AdServeiceAccount command.
Also if poosible, please confirm, weather multidomain set up is correct?

Public Folder access on Exch 2007 from exch 2013 user

I have an issue with my test user that I migrated from 2007 to exch 2013 being able to access public folders that reside on the 2007 server. 2007 users accessing public folders on 2007 have no issues. I have it narrowed down to autodiscover. Please see the
below exerpt from autodiscover. The "<PublicFolderServer>ex2013.accessDOMAIN.net</PublicFolderServer>" section shows that autodiscover is giving the name of the exchange 2013 server as the publicfolderserver
instead of the exchange 2007 server. My question is how do I reflect the correct server "Exch2007" on this autodiscover output?
<Account>
      <AccountType>email</AccountType>
      <Action>settings</Action>
      <MicrosoftOnline>False</MicrosoftOnline>
      <Protocol>
        <Type>EXCH</Type>
        <Server>[email protected]</Server>
        <ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
        <ServerVersion>73C0834F</ServerVersion>
        <MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
        <PublicFolderServer>ex2013.accessDOMAIN.net</PublicFolderServer>
        <AD>DC.domain.local</AD>
        <ASUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</ASUrl>
        <EwsUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</EwsUrl>
        <EmwsUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</EmwsUrl>
        <EcpUrl>https://ex2013.accessDOMAIN.net/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.local</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.local</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.local</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.local</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.local</EcpUrl-sms>
        <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=domain.local</EcpUrl-publish>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.local</EcpUrl-photo>
        <EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.local</EcpUrl-tm>
        <EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.local</EcpUrl-tmCreating>
        <EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.local</EcpUrl-tmEditing>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.local</EcpUrl-extinstall>
        <OOFUrl>https://ex2013.accessDOMAIN.net/EWS/Exchange.asmx</OOFUrl>
        <UMUrl>https://ex2013.accessDOMAIN.net/EWS/UM2007Legacy.asmx</UMUrl>
        <ServerExclusiveConnect>off</ServerExclusiveConnect>
      </Protocol>

Thank you for your time. I verified that the build number on outlook is greater than SP1. This would indicate that the hotfix was applied as it was included in cumulative rollups.
The output from the geet-outlookanywhere command is found below. I have adjusted the auth to basic as that is where I would like it to be.
[PS] C:\Windows\system32>Get-Outlookanywhere | fl Identity,*auth*,*hostname,*ssl
Identity                           : Exch07\Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
ExternalHostname                   : legacymail.DOMAIN.net
InternalHostname                   : legacymail.DOMAIN.net
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
Identity                           : Exch13\Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
ExternalHostname                   : webmail.DOMAIN.net
InternalHostname                   : webmail.DOMAIN.net
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email
I am running Exchange 2013 and I have an end user who connects to it via Outlook 2010. All was going well till he went to forward an email and he noticed that the From button appeared and auto populated the sender's email address.
I have clicked the Empty Auto Complete List in Outlook's Send messages... still displayed the From tab when forwarding.
I recreated the profile in outlook... same thing.
I created the profile with outlook 2013... same thing.
There is only one user profile setup in Outlook.
(I know the from tab usually appears when you have multiple profiles setup in Outlook and/or when you configure the "From" tab.)
I opened the end user's email in Exch 2013's OWA... what was different here was when I clicked on the email and it opened, it did NOT have the Reply or Forward option... and it displayed as a "Draft" email.
Does anyone have any ideas?

So are you saying that the from button is filling the option with the original senders address (eg the person who sent the message to your user), or that it's filling in the your users address (in which case I don't understand what the issue is, since
it IS going from your user)?

Outlook clients cannot connect Exchange 2013 cutover from 2010

Hello,
My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server.
We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
the external URLs are $null
Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
and 2013 CAS servers.
I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
It was only the Outlook 2010 and 2013 clients that could not connect.
We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
but the settings seem correct unless I'm missing something. Any help is appreciated.
Thanks!

Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

Sharepoint Foundation 2013 and Outlook 2010 Reminders

Hello, I have recently been informed by one of my users that they are experiencing a peculiar issue in regards to their SharePoint calendar. A brief history is that we are currently using SharePoint
Foundation 2013 with Outlook 2010, all of our users have calendars for their departments in SharePoint, and those calendars have been added to Outlook for their convenience. This particular user has a SharePoint alert set up on their calendar for all changes,
and receives an alert immediately. After some troubleshooting, this is how my user is getting the issue they described:
User1 will create an appointment from Outlook on the SharePoint calendar that User2 has their alert set up for. User2 will receive the appropriate alert email that there has been a new event
added to the calendar. User1 then receives an Outlook reminder that their event is coming up. If User1 clicks "dismiss" on that reminder, User2 will have another alert email generated hours later which informs them that the calendar event for User1
has been modified. If you view the event from SharePoint it will show a new modified time with User1's name, even though there have been no changes made. The other interesting part about the modified time is that it will not reflect when User1 clicked “dismiss”
on the reminder, instead it will reflect the time that the SharePoint alert email was generated.
This is not a fluke issue; I've been able to recreate the scenario 100% of the time if I follow this pattern. I can also simulate it on any calendar I create or that is already existing in our
environment.
I have been researching and trying to find an answer to this problem for several days now, but the only thing I have found is a post from someone else experiencing the same issue with no solution.
So any feedback would be greatly appreciated. If there is more information that is needed to better assist me, please let me know.
Thank you for your time.

Hello, if I remember correctly the issue was that I created the form with InfoPath 2013 and was trying to test using InfoPath 2010. This does not work.
Did you create the form using InfoPath 2013?

How to remove Office 2013 (Click to run) package?

I am having problems removing Office 2013 sequenced using Click to Run and is published to the machine as per MS guidelines.
It's a member of a connection group with another application.
I have tried many things:
get-appvclientpackage | stop-appvclientpackage | remove-appvclientpackage.
get-appclientconnectiongroup | remove-appvclientconnectiongroup
The connection group and both applications remain.
Error reported is that the application is still in use (no idea which one as it doesnt say). Task manager doesn't seem to list anything running from any virtual environment. I have tried viewing 'processes from all users' also.
I unpublished the connection group and the applications from the App-V Management Server, then retried the above commands which didnt work.
Tried rebooting after doing all the above, then retry PoSH commands and that didnt work either.
Any ideas?

Hello,
See this article;
http://blogs.technet.com/b/virtualvibes/archive/2013/12/03/pending-tasks-in-app-v-5-0-sp2.aspx
Nicke Källén | The Knack| Twitter:
@Znackattack

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

Removing Exch 2013 in Exch 2010 environment

Similar Messages

Maybe you are looking for