Removing Exchange 2007 hub server

Hi, my company has last remaining hub 2007 server while the rest is already migrated to Hub 2010 servers. All hub servers subscribed to Edge 2007 servers. i have issue when i want to remove last hub 2007 servers with error like "This
computer is configured as a source transport server for 1 connector(s) in the organization. These must be moved or deleted before Setup can continue". i read other post that i need to remove 'send connectors' from hub 2007. Do i need to remove
edge subscriptions too in hub 2007 server ? If i remove send and egde subscription from hub 2007 server, is it the action will impact the hub 2010 servers ?
2nd question, let say if i want to remove edge server, do i need to re-create send and receive connectors in hub 2010 servers?

If you are removing edge servers, you need to configure your systems so that Internet email bypasses them (in both directions).  In answer to your #2 above, your send and receive connectors have to be configured for this
before you remove the edge servers.  Whether you create new ones or modify existing ones for this depends on how the rest of your architecture is designed.  Once this is done, you can remove your edge subscriptions and uninstall your
edge servers.

Similar Messages

  • Exchange 2007 HUB Server Faulting application edgetransport.exe

    Hello,
    I'm having wired problem with my Exchange Server "Hub transport". it keeps queuing the mails and SMTP Gateway unable to send them to the Exchange HUB Server.
    Environment:
    Exchange Mailbox Role on separate server
    Exchange HUB/CAS on separate server
    IMSS Trend Micro as Edge SMTP Transport Server.
    Faulting application edgetransport.exe, version 8.1.436.0 error keeps coming in the event viewer.
    I have stopped the MS Exchange Services and Deleted/Renamed the Queue Directory Under C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue. When I started the services again, new Queue Directory created and mail flow started again.
    When I try to access the Queue Viewer in Exchange,  got the following error;
    Any help would be appreciated.
    edgetransport (6376) Transport Mail Database: Database 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue\mail.que': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over 796 non-visible nodes
    in 160 pages. It is likely that these non-visible nodes are nodes which have been marked for deletion but which are yet to be purged. The database may benefit from widening the online maintenance window during off-peak hours in order to purge such nodes and
    reclaim their space. If this message persists, offline defragmentation may be run to remove all nodes which have been marked for deletion but are yet to be purged from the database.
        Name: MailRecipTable
        Owning Table: MailRecipTable
        ObjectId: 9
        PgnoRoot: 51
        Type: 2
        Unversioned Deletes: 796
        Uncommitted Deletes: 0
        Committed Deletes: 0
        Non-Visible Inserts: 0

    Hi All,
    Prior to this Application Error (1000) starts; I can see there is another warning which appears.
    Recipient group membership cache loaded. Group:
    [email protected], Time: 00:00:00.5304918, Members: 1490
    Faulting application edgetransport.exe, version 8.2.176.0, time stamp 0x4a5b9add, faulting module MSVCR90.dll, version 9.0.30729.4148,
    Failed extract of third-party root list from auto update cab at:
    Anti-spam agents are enabled, but the list of internal SMTP servers is empty. If there are any MTAs between this server and the Internet, populate this list by using the Set-TransportConfig cmdlet in the Exchange
    Management Shell.
    edgetransport (5076) Transport Mail Database: The database engine (8.02.0176.0000) started a new instance (0).
    edgetransport (5076) Transport Mail Database: The database engine has begun replaying logfile C:\Program Files\Microsoft\Exchange
    Server\TransportRoles\data\Queue\trn.log.
    The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 server mubex01.Domain.com in Routing Group CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative
    Groups,CN=Domain Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com in routing tables with the timestamp 11/13/2014 11:38:50 AM.
    A route to Mailbox server CN=MUBEX01,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com could not be found
    for store CN=Public Folder Store (MUBEX01),CN=Staff Storage Group,CN=InformationStore,CN=MUBEX01,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=RCSI MUB,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com in routing tables
    with timestamp 11/13/2014 11:38:50 AM. Recipients will not be routed to this store.
    The Microsoft Exchange Transport service has started the background scan of the queue database. All messages that have not yet been delivered will be loaded.
    The background scan of the transport queue database has completed. 25 message(s) were found.
    Journal rules were loaded.
    Recipient group membership cache loaded. Group:
    [email protected], Time: 00:00:00.5148891, Members: 1490
    Faulting application edgetransport.exe, version 8.2.176.0, time stamp 0x4a5b9add, faulting module MSVCR90.dll, version 9.0.30729.4148, time stamp 0x4a594e3d, exception code 0xc0000417, fault offset 0x00000000000552c0,
    process id 0x13d4, application start time 0x01cfff366342a0f4.
    Appreciate if someone could point me to the right direction on this dilemma.
    Thanks,

  • Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

    I'm trying to remove Exchange 2007 from an SBS 2008 server
    (Server 2008 Standard FE).  My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
    We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
    I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers.  We have two full blown DC's in the environment.
    I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server.  I can NOT seem to find a TechNet article that shows me how
    to proceed in this kind of scenario.  I am trying to use the TechNet article:
    http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
    This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard. 
    When I go to Disable Mailboxes I get the following error:
    Microsoft Exchange Error
    Action 'Disable' could not be performed on object 'Username (edited)'.
    Username (edited)
    Failed
    Error:
    Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
    OK
    I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010.  I just want
    to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
    Can someone point me in the right direction?
    Thanks!

    Hi,
    Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
    2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
    On current situation, please refer to following articles and check if can help you.
    Transition
    from Small Business Server to Standard Windows Server
    Removing SBS 2008 –
    Step 1: Exchange 2007
    Removing SBS 2008 – Step 2:
    ADCS
    Removing
    SBS 2008 – Step 3: remove from domain / DCPROMO
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
    does not guarantee the accuracy of this information.
    Hope this helps.
    Best regards,
    Justin Gu

  • Removing Exchange 2007 from SBS 2008 after Migrating to Office 365 Mid Sized with DirSync and SSO

    We have recently completed off a Migration of Exchange 2007 to Office 365 Mid Sized platform.
    I now need to decomission the old SBS 2008 server as they have moved to a Windows Server 2012 R2 server setup for DC, File and print and application servers.
    I need to know what are the ramifications of removing the Exchange 2007 server from the SBS 2008 server and will this remove the LegacyDN details from AD and cause any issues with internal emails between users using Outlook linked through to Office365.
    I understand that after removing Exchange 2007 there will be no friendly GUI to update and maintain proxyAddress, targetAddress and LegacyDN addresses, I am comfortable doing this in ADSI edit or with a script.
    Will this remove the x500 addresses relating to the on premise Exchange Orgainisation and just leave behind the x500 addresses for Exchange Labs which I assume is the x500 addresses for the Azure AD intergration for Office365.

    Hi ,
    Thank you for posting your issue in the forum.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Best Regards,
    Andy Qi
    Andy Qi
    TechNet Community Support

  • Exchange 2007 edge server with ironport

    I currently have a frontend exch 2003 and backend exch 2003 server with ironport. my mx record is the ironport which then forwards into the backend server. The frontend server was only used for owa and using outlook with https connection to exchange.
    With 2007 it has more functionality and the front end server is now called an edge server. Should I have mx go there then to ironport or vice versa? I'm thinking ironport to edge server to hub transport server. Is that correct? will it work?
    anyone have exchange 2007 edge server with ironport? what are you doing?

    well that wouldve been nice to know a little earlier. anyway I have ironport successfully sending mail to the edge server who sends it on to the hub transport server. right now the client access server is on the same as the hub but can be easily moved later. this is for very few people so its not like I need to off load anything as its a powerful dual core server. anyway now with the edge server I can test how effective it is versus the ironport. I'll let everyone know when you can ditch the ironport for msft's edge server. (Don't hold your breath).

  • Remove Exchange 2007 from an Exchange 2013 coexistence.

    Hey everyone,
    I've just installed Exchange 2013 on a new server and all is working great.  It is currently in coexistence with our old Exchange 2007 server.  I've since shut the server down and Exchange 2013 has been working without issue.  However, I haven't
    been able to find any articles on this matter so I figured I would ask the question here.
    How do you remove Exchange 2007 from the coexistence.  Do I just uninstall Exchange 2007 from the old server and it will remove itself from the server and the domain?  Any help/link on this matter would be greatly appreciated.
    Thank you,
    Chris

    Hi Simon,
    I am about to do the same exercise as Chris,  I just would like some clarity.  
    1) When you say mailbox Database, do you mean make sure there are no more mailboxes that you want to move over, or are you actually meaning delete the physical DB on the exchange 2007 server.
    2) If there is no use of public folders does anything need to happen?
    Thanks,
    Terry

  • Remove Exchange 2007

    Hi,
    I just moved all mailboxes from exchange 2007 to Office 365 with Exchange 2010 Hybrid setup. I believe that all local Exchange 2007 contact list and Distribution Group are syncing from Dirsyc tool. It is no migration for this type object. From now, we will
    decide to remove Exchange 2007 from network. What we need to do before to safety remove the Exchange 2007 Server ?
    thanks
    Keith

    Hi Keith,
    Agree with both MAS and Gulab Prasad.
    Please shut down Exchange 2007 and monitor whether the new environment works well.
    Then, please remove Exchange 2007 from a server by using Setup Wizard. Details to see:
    http://technet.microsoft.com/en-us/library/bb123893(EXCHG.80).aspx
    (Optional) Last, remove the Exchange 2007 administrative group by using ADSIEdit. The Exchange 2007 administrative group is called
    Exchange Administrative Group (FYDIBOHF23SPDLT)
    Thanks
    Mavis Huang
    TechNet Community Support

  • Demoting and Removing Exchange 2007 Server

    Oh, I mistakenly saw 2003, and I thought you were removing Exchange 2003.  My bad.
    Run the uninstaller on the old system. It will take care of the rest.  It will probably error out and give you reasons, clean up the reasons and run the uninstaller again.  Once it's uninstalled properly, then you can power off the server and everything should be good.  Don't forget your send connectors. I forgot that in my travels once.

    At one of our locations we recently migrated all exchange mailboxes to a new Exchange 2007 on new OS platform, moving away from Server 2003. Everything to my knowledge has been migrated, users should be all connecting to new server, all connector headends have been updated, etc. As a test, I shutdown the old Exchange server (without uninstalling) but we ran into issues that day with Outlook constantly (every 5-10 minutes) asking for the user's password, slow loading of folder data, etc.; reboots/application restarts did not resolve. We turned the old Exchange server back on and all is now well. My theory is this is due to the schema still containing info about the old Exchange server. If I uninstall Exchange completely, thus removing it form schema, could I expect to have this issue resolved? Obviously I only get one chance on this, so...
    This topic first appeared in the Spiceworks Community

  • Removing Exchange 2007 Server from Management Console List

    Hello,
    We have an organization with a single Exchange 2007 Server running in production. It is working fine.
    However, we brought up another server (we'll call it the secondary server for purposes of this thread) and linked it into this organization several months ago. Our plans for this box changed and we have kept it powered off, unlicensed, and unused.
    Now, when we manage our production server, the management console keeps complaining about how the secondary server is almost at the end of its trial period, needs licensed, etc.
    Since we might or might not use the secondary server in the future, it is possible to "unlink" it (or set it dormant somehow) from the server list to stop the license warnings? Or is our only recourse to remove Exchange and take it down if we don't
    intend to license it and bring it into production? Our hope is that it can wait in the wings until such time as we decide to user & license it.
    What are the implications if we ignore the license warnings and continue not to use it? Will it impact management of the production server at all or just continue to annoy?
    TIA, Tom W.
    JTW

    Hello,
    "What are the implications if we ignore the license warnings and continue not to use it? Will it impact management of the production server at all or just continue to annoy?"
    You should have all production servers licensed but after trial period expiration the server will have all Exchange capabilities and features. Also trial period expiration should not have any negative impact on your environment. The EMC will simply prompt
    to license that server correctly.
    "Our plans for this box changed and we have kept it powered off, unlicensed, and unused."
    In my opinion it is bad idea to have Exchange server installed but powered off. Note that this server still resides as object in Active Directory and it may complicate any future modifications of your environment (migration to newer versions of Exchange
    etc.). I think you should use this server to provide some kind of high availability (and provide proper license for it) or remove it completely.
    Once again: trial expiration is not a problem from server's functionality perspective, Exchange server powered down - it can be a problem.

  • Decommission Exchange 2007 Mailbox Server from Cluster

    Hi! I realize this is an Exchange 2013 forum, however as I do not see any forums for older flavors of Exchange I'm going to post this here. If a better forum exists please let me know and I'll happily move to that forum for my answers.
    I am just finishing a migration from Exchange 2007 to Exchange 2013.  In the Exchange 2007 environment I have 2 CCR Mailbox Clusters.  While working to decommission the first of the two clusters I successfully evicted the passive node, however
    I mistakenly evicted the active node rather than removing it by running the Exchange Setup Wizard as outlined in the TechNet article "How to Remove the Active Mailbox Role from a CCR Environment".
    Now, when attempting to uninstall Exchange 2007 using the Setup Wizard in Add/Remove Program I get the following error during the prerequisite check for the 'Mailbox Role':
    Error:
    Exchange server FQDN was not found. Please make sure you have typed it correctly."
    Setup then completes.
    Is there a way to cleanly uninstall Exchange 2007 and clean-up Active Directory?
    Thanks!

    Hi Jesse,
    Thank you for your question.
    We could run “ADsiedit.msc” in run, then navigate
    Configuration [<domainController>.contoso.com]> CN=Configuration,DC=contoso,DC=com> CN=Services> CN=Microsoft Exchange> CN=<OrganizationName> CN=Administrative Group> CN=Exchange Administrative Group>CN=Server
    We could check if mailbox server is existed in this container, we could remove it.
    Notice: Before we remove it, we could make a backup for AD database. We suggest you call MS engineer for help.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Keep exchange 2007 Hub transport & CAS during migration to Exchange 2010

    Hello,
    during a migration from exchange 2007 to exchange 2010 is it supported to keep the old exchange 2007HUB and CAS in charge of the outside mail flow (send/receive) and OWA service.
    Here is the scenario :
    Actual OWA url : https : // webmail . compagnie . com  (2007)
    Future OWA url : https : // owa . compagnie . com 2010)
    Keep the old url accessible for the users which have not be migrated to the new exchange 2010 MBX server.
    Indicate to the migrated users to use the new url instead of the old one.
    Keep the old hub transport server (2007) handle the mail flow (send/receive) to the outside.
    At the end, when all the users will be migrated, configure the new 2010 Hub/cas to handle the mail flow (send/receive) to the outside.
    Thanks a lot for your answers.
    David

    Thanks for your answers.
    So if I have understood right, the only thing I have to take care about (in order to let the 2007 cas/hub server handle the external mail flow (on which the MX is bind) until all mailboxes are migrated) is to add the 2010 cas/hub server in :
    Organization Configuration ---> send connector ---> Actual 2007 send connector --> Source server
    Thanks a lot.
    David
    That will take care of the outbound message flow, yes.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • How to decomission a Exchange 2007 Mailbox server

    Hello, 
    We are running Exchange 2007 SP3 servers. We currently have a Mailbox server we want to decommission. I'd like help on how to achieve this. I want to make sure that all mailboxes have been moved from that server and remove the Public Folder database as well.
    I understand that the Public Folders needs to stop replicating to this server, can someone please guide me on how to do that?
    All kinds of help are appreciated. Thanks!

    For the public folder stuff, see these scripts: https://technet.microsoft.com/en-us/library/aa997966(v=exchg.141).aspx
    The system folders can be replicated with the '\non_ipm_subtree' identifier, but some system folders are per-server and don't need to replicate.  OAB distribution however
    is one that might matter.
    Mike Crowley | Microsoft MVP
    Baseline
    Technologies

  • Remove Exchange 2007 from AD (manually)

    In the lab I had Exchange 2007 running and someone pulled my VM.  It's not the end of the world because I'm done with what I was doing in 2007 however I've got other things running in the lab and I'd rather not rebuild the domain.
    Does anyone know what the process would be to clean up AD (remove the Exchange org) without having the Exchange server to do an uninstall on?  Can I Install the Exchange admin console on another box and than remove the mail attributes from the accounts that has them and just remove the Exchange Systems Object container in AD or is there more?
    Erik

    I did run into one problem while trying to install RTM:
    Organization Preparation
    Failed
    Error:
    The well-known object entry B:32:A7D2016C83F003458132789EEB127B84:CN=Exchange Servers\0ADEL:e60b372e-cd97-4fc2-bc8f-907728f0bc8d,CN=Deleted Objects,DC=domain,DC=com of the otherWellKnownObjects attribute on container object CN=Configuration,DC=domain,DC=com
    points to an invalid DN or a deleted object.  Please remove the entry and rerun the task.
    I was able to resolve the issue by launching adsiedit.msc (part of the support tools) and going to the Configuration partion and bringng up the properties for Configuration,DC=domain,DC=com
    I edited the "othereWellKnownObjects" attribute to be "not set" (which it should be) by leaving it blank and clicking "add" (adding nothing) than applying the changes and re-running setup.
    Kudos to this thread for the fix:
    http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=839779&SiteID=17
    Cheers,
    Erik
    otherWellKnownObjects is a multi-valued object.  You need to remove the bad value, NOT ALL OF THEM!!
    Mike Crowley | MVP
    My Blog --
    Planet Technologies

  • Exchange 2007 hub transport MAPIdelivery queued

    Hi,
    I just encountered problem that Hub server cannot route mail to mailbox server and pending on MAPIdelivery queue. But there is no error on queue and I need to restart information store service on mailbox server but after a minute, it pending on MAPIdelivery
    queue again.
    anyone can help me for solve this urgent issue.
    thanks
    Keith

    Hi,
    To narrow down the issue, as what Rich mentioned above, we can use the Performance Monitor tool to collect related information and then analyze it.
    A related article:
    Getting started with Exchange 2007 Performance monitoring and Windows 2008
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Can't connect to Exchange 2007 SP2 server

    When I try and set up a new Exchange account to our internal Exchange 2007 server I get the following error message:
    "The Exchange Server '<server name>' doesn't have the minimum required version installed. To use Mail with Exchange, the server must be running Update Rollup 4 for Exchange Server 2007 Service Pack 1 or later. Contact your server administrator.'
    in spite of Service Pack 2 being installed on the server.
    Exchange Web Services are running as expected at the URL '/EWS/Exchange.asmx'.
    If anyone has suggestion on how to diagnose the exact problem I would very much appreciate the assistance.
    N.

    Hello,
    I don't have any ideas yet but can chime in with "me too".
    A customer has an Exchange 2003 SP2 server (MS Server 2003 for SBS). It has a self-signed SSL certificate that does not expire until June 2011.
    One user has some species of Blackberry that can pick up his email (but not contacts or calendar) via OWA. I can see his accesses in the IIS log and they are coming from IP addresses resolving to (stuff).bise.na.blackberry.com and are not getting 404's.
    Another user is trying to set up his new Blackberry via BIS. His accesses in the IIS log are coming from different IP addresses that resolve to (stuff).bis.ap.blackberry.com and these are getting 404's.
    An ExpertsExchange.com article - http://www.experts-exchange.com/Software/Server_Software/Web_Servers/Microsoft_IIS/Q_22806090.html - suggested putting the full email address into the OWA URL. This works fine in a browser but not in BIS. I still get the same error message from BIS and 404's in the IIS log.

Maybe you are looking for