Re: Decommissioning the last Exchange 5.5 server

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Karsten (hhamburgerjung_at_yahoo.com)
Date: 10/06/04


Date: Wed, 06 Oct 2004 16:54:28 -0700

I will just qoute Neil - he put it so well:

>> Are you saying your outbound SMTP mail queues? If so, that is to be
>> expected if the only outbound route is on the 5.5 server. Therefore,
>> yes, you'd need to create an SMTP Connector on the Exchange 2003
>> server. Set the address space to * and set the cost to 1. Then set
>> the cost of the Exchange 5.5 IMS to something higher than 1, say 10,
>> and let replication occur (or force a replication of the ConfigCA in
>> ADC). This way, the E2k3 server should then process outbound SMTP
>> mail rather than the 5.5 server.

So, in my words ;) creating an SMTP connector with a higher priority
solved it. The Exchange 5.5 server is shut off now and mail is flowing
through 2003. Phew :)

In article <#DCSRs$qEHA.644@tk2msftngp13.phx.gbl>,
 "Susan" <susan@nospam.com> wrote:

> what was it?
>
> <hhamburgerjung@yahoo.com> wrote in message
> news:hhamburgerjung-20F933.16054306102004@msnews.microsoft.com...
> > Oops, I meant that I already had verified that the e-mails in that queue
> > were directed towards external recipients.
> >
> > The problem seems to be solved now. Thanks for all your help.
> >
> >
> > In article <eRO59F$qEHA.516@TK2MSFTNGP09.phx.gbl>,
> > "Susan" <susan@nospam.com> wrote:
> >
> > > you should be able to tell where the messages were supposed to go by
> > > examining them in the queue...
> > >
> > > <hhamburgerjung@yahoo.com> wrote in message
> > > news:hhamburgerjung-7F2126.15070406102004@msnews.microsoft.com...
> > > > In article <e3k#Eu#qEHA.2732@TK2MSFTNGP09.phx.gbl>,
> > > > "Susan" <susan@nospam.com> wrote:
> > > >
> > > > Not sure, I have to admit. I have observed though that as soon as I
> stop
> > > > the MTA Agent on the 5.5 server, outbound mails were queued in a queue
> > > > [5.5Server] with Protocol X400 and Source Exchange MTA. Am I
> misreading
> > > > something?
> > > >
> > > > > the mails that went into the MTA queue were mails to the Internet?
> how
> > > does
> > > > > your email go to the Internet? forwarded to a host or using DNS?
> > > > >
> > > > > <hhamburgerjung@yahoo.com> wrote in message
> > > > > news:hhamburgerjung-832370.14220306102004@msnews.microsoft.com...
> > > > > > I am in the process of removing the last Exchange 5.5 server from
> our
> > > > > > network after installing and migrating to Exchange 2003. I have
> read
> > > the
> > > > > > Exchange Deployment Guide as well as KB articles 284148, 822450
> and
> > > > > > 285090. So far everything went well until I came to section 11 in
> KB
> > > > > > 284148, where it says:
> > > > > >
> > > > > > >> At this point you may want to just power down the Exchange
> Server
> > > 5.5
> > > > > > computer to ensure that everything functions properly before
> actually
> > > > > > uninstalling Exchange from the server. When you are convinced that
> > > > > > everything is functioning properly, you can uninstall Exchange
> from
> > > the
> > > > > > server. <<
> > > > > >
> > > > > > I shut down the Exchange Server 5.5, and immediately mails were
> > > spooled
> > > > > > into the Exchange 5.5 MTA queue instead of being sent out. When
> the
> > > > > > Exchange 5.5 server came back up the mails were sent.
> > > > > > So my question is, does this behaviour change, that is, is the
> > > Exchange
> > > > > > 2003 queue being used, as soon as the 5.5-server is deleted?
> > > > > > Also, do I need to manually create an SMTP connector to replace
> the
> > > > > > Internet Mail connector from the 5.5-server?
> > > > > > Lastly, if I delete the 5.5-server from the organization, can I
> bring
> > > it
> > > > > > back if things get awry?
> > > > > >
> > > > > > Thank you for your help
> > > > > > Karsten
> > > > >
> > > > >
> > >
> > >
>
>



Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
    (microsoft.public.windows.server.active_directory)
  • Re: adding 64-bit R2 DC to existing domain
    ... Server 2003 standard edition 32-bit domain controllers. ... The schema master did not complete a replication cycle ..." ... server1 failed test KnowsOfRoleHolders ... ForestDnsZones failed test CrossRefValidation ...
    (microsoft.public.windows.server.setup)