Removing Exchange 2000 server from Exchange 2007 environment

I installed a new Exchange 2007 Server that ran concurrently with
an Exchange 2000 Server. I gradually moved all the mailboxes until I
finally had them all. There was still the problem of a certain
application that had server information hardcoded in that finally got
changed this week. Everything is now on the New Exchange Server,
including Public Folders and offline address books.

So I shut it down to see if everything would function ok. It did,
with the exception of a single client computer. When I shut down the
2000 box, Outlook will receive EMAIL but will not send. It asks for a
password for the user to logon to the old Exchange Server. The
Outlook client is set up exactly the way every other Outlook Client
is. The Version is Outlook 2003.

Send Connectors are on both Servers. They route to a spam filter I
use as a smart host.

No Routing groups exist between the two servers. I deleted them
earlier this week.

Why is this one computer still trying to route through the old
exchange server?

John
Sat May 03 20:01:01 CDT 2008

Did you recreate the Outlook Profile?

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner

"Andy" <andy.lisowski@gmail.com> wrote in message
news:028f391a-d1c4-4abd-8657-a9ece55e9ac9@8g2000hse.googlegroups.com...
>
> I installed a new Exchange 2007 Server that ran concurrently with
> an Exchange 2000 Server. I gradually moved all the mailboxes until I
> finally had them all. There was still the problem of a certain
> application that had server information hardcoded in that finally got
> changed this week. Everything is now on the New Exchange Server,
> including Public Folders and offline address books.
>
> So I shut it down to see if everything would function ok. It did,
> with the exception of a single client computer. When I shut down the
> 2000 box, Outlook will receive EMAIL but will not send. It asks for a
> password for the user to logon to the old Exchange Server. The
> Outlook client is set up exactly the way every other Outlook Client
> is. The Version is Outlook 2003.
>
> Send Connectors are on both Servers. They route to a spam filter I
> use as a smart host.
>
> No Routing groups exist between the two servers. I deleted them
> earlier this week.
>
> Why is this one computer still trying to route through the old
> exchange server?

Andy
Tue May 06 14:57:49 CDT 2008

On May 3, 8:01 pm, "John Oliver, Jr. [MVP]" <jcolive...@hotmail.com>
wrote:
> Did you recreate the Outlook Profile?
>
> --
> John Oliver, Jr
> MCSE, MCT, CCNA
> Exchange MVP 2008
> Microsoft Certified Partner
>
> "Andy" <andy.lisow...@gmail.com> wrote in message
>
> news:028f391a-d1c4-4abd-8657-a9ece55e9ac9@8g2000hse.googlegroups.com...
>
>
>
> > I installed a new Exchange 2007 Server that ran concurrently with
> > an Exchange 2000 Server. I gradually moved all the mailboxes until I
> > finally had them all. There was still the problem of a certain
> > application that had server information hardcoded in that finally got
> > changed this week. Everything is now on the New Exchange Server,
> > including Public Folders and offline address books.
>
> > So I shut it down to see if everything would function ok. It did,
> > with the exception of a single client computer. When I shut down the
> > 2000 box, Outlook will receive EMAIL but will not send. It asks for a
> > password for the user to logon to the old Exchange Server. The
> > Outlook client is set up exactly the way every other Outlook Client
> > is. The Version is Outlook 2003.
>
> > Send Connectors are on both Servers. They route to a spam filter I
> > use as a smart host.
>
> > No Routing groups exist between the two servers. I deleted them
> > earlier this week.
>
> > Why is this one computer still trying to route through the old
> > exchange server?

On the Client? No..but I havn't had to do it on any other computer
either.

I'm going to be rolling out Office 2007 to a few select users starting
tomorrow and the person with the computer in question is one of
them.......so I'll probably try recreating it then.

Andy

John
Tue May 06 19:19:50 CDT 2008

I would try that first.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner

"Andy" <andy.lisowski@gmail.com> wrote in message
news:0446b57d-573e-471e-bef6-7b31e1e6ad80@56g2000hsm.googlegroups.com...
> On May 3, 8:01 pm, "John Oliver, Jr. [MVP]" <jcolive...@hotmail.com>
> wrote:
>> Did you recreate the Outlook Profile?
>>
>> --
>> John Oliver, Jr
>> MCSE, MCT, CCNA
>> Exchange MVP 2008
>> Microsoft Certified Partner
>>
>> "Andy" <andy.lisow...@gmail.com> wrote in message
>>
>> news:028f391a-d1c4-4abd-8657-a9ece55e9ac9@8g2000hse.googlegroups.com...
>>
>>
>>
>> > I installed a new Exchange 2007 Server that ran concurrently with
>> > an Exchange 2000 Server. I gradually moved all the mailboxes until I
>> > finally had them all. There was still the problem of a certain
>> > application that had server information hardcoded in that finally got
>> > changed this week. Everything is now on the New Exchange Server,
>> > including Public Folders and offline address books.
>>
>> > So I shut it down to see if everything would function ok. It did,
>> > with the exception of a single client computer. When I shut down the
>> > 2000 box, Outlook will receive EMAIL but will not send. It asks for a
>> > password for the user to logon to the old Exchange Server. The
>> > Outlook client is set up exactly the way every other Outlook Client
>> > is. The Version is Outlook 2003.
>>
>> > Send Connectors are on both Servers. They route to a spam filter I
>> > use as a smart host.
>>
>> > No Routing groups exist between the two servers. I deleted them
>> > earlier this week.
>>
>> > Why is this one computer still trying to route through the old
>> > exchange server?
>
> On the Client? No..but I havn't had to do it on any other computer
> either.
>
> I'm going to be rolling out Office 2007 to a few select users starting
> tomorrow and the person with the computer in question is one of
> them.......so I'll probably try recreating it then.
>
> Andy