Outlook 2003 becomes very slow to open

Outlook 2003 becomes very slow to open

Problem - when I shut down an old Windows 2000 server that USED TO BE a 
domain controller, though NEVER an Exchange server, Outlook 2003 becomes very 
slow to open on every machine on the network.

Environment: 
-single Exchange 2003, fully patched with all Microsoft updates / Outlook 
2003, also fully patched with all available updates.
- Network of about 40 users
- NO RPC over HTTP
- NO cached Exchange mode
- NO .pst or .ost files permitted
- no IMAP or POP3 connections are permitted
- No ActiveSync connections are permitted
- single Exchange server, no front end/back end configuration.
- Currently, there are 2 domain controllers on the network, both functioning 
without error (the Exchange server and another server).
-  Domain is in mixed mode.
- No firewalls, Windows or otherwise, between desktops and Exchange.
- No related errors in event logs of servers or desktops
- No AD errors on domain controllers
- No DNS issues


Issue:
We have an old Windows 2000 server, that was the original domain 
controller/file print server for the domain.  About 3 years ago, we installed 
a new Windows 2003 server and moved all of the AD rolls, DNS and DHCP off of 
the old server and onto the new server.  This server was NEVER an Exchange 
server.  We disabled DNS and DHCP serivces at that time and ran DCPromo to 
remove the old server from the domain.  All went well.  There were no issues 
or errors.  Unfortunately, we left the old server up and running just in case 
there was a file that someone needed.  The old server was left running in the 
rack and was forgotten about.

Now, we need to install some new servers and we need the rack space, so we 
have to fully decommission the old server.  Everything works fine when we 
shut it down, EXCEPT for Outlook 2003.  If the old server is shut down, 
Outlook takes over 3 minutes to open on every desktop on the network.  The 
minute the server comes back up, Outlook opens normally.

We moved from Exchange 2000 to Exchange 2003 (fresh install on new server, 
used Exmerge to move contents of mailboxes) about 2 years ago.  The old 
Exchange server has been off of the network since the upgrade.

If I open Outlook with the /rpcdiag switch with the old server down, the 
first 2 connections are made immediately, with normal speed.  The delay is 
between the second and third connection.

The Outlook web client continues to function normally, whether or not the 
old server is on.

I have tried all the safe mode switches.  /safe:1, safe:3 and safe:4 do not 
affect startup speed.  If I start in /safe:2 (starts Outlook without checking 
mail at startup), Outlook opens at normal speed.  I have also tried the 
/cleanprofile switch, which had no effect.

Other than the issue with Outlook, all logins/network applications and 
resources function normally, whether the old server is up or not.

I searched through the registry of one of the desktops.  I do not see any 
references to the old server by either name or IP address.

I would appreciate any ideas on how to resolve this problem.

date: Thu, 1 May 2008 13:34:00 -0700 author: cef

Re: Outlook 2003 becomes very slow to open

"If I open Outlook with the /rpcdiag switch with the old server down, the
first 2 connections are made immediately, with normal speed.  The delay is
between the second and third connection."

The delay is connecting to what EXACTLY?  The Exchange server or the Global 
Catalog server or what?

We are having a similar problem.  Running Exchange 2003 with Outlook 2003 
with all the latest patches.  Since we upgraded all our domain controllers 
to Server 2003 we are experiencing the same symptoms of Outlook taking 2 or 
3 minutes to open.  Running Outlook with /RPCDIAG I see that it takes quite 
awhile to connect to the GCs.  All other applications seem to run fine. 
Makes no sense to me.  My temporary fix is to make entries in the HOSTS file 
for the GCs.  That seems to fix the problem.  My first thought is a DNS 
issue.  However, doing an nslookup on the Exchange server(s) or GCs is 
lightening fast as is looking up any other host name.  I don't get it.  What 
is different about Outlook?

Anyone out there have any thoughts about this?


"cef"  wrote in message 
news:EA0E1113-EB51-494E-B58A-F9D7CB31A26A@microsoft.com...
> Problem - when I shut down an old Windows 2000 server that USED TO BE a
> domain controller, though NEVER an Exchange server, Outlook 2003 becomes 
> very
> slow to open on every machine on the network.
>
> Environment:
> -single Exchange 2003, fully patched with all Microsoft updates / Outlook
> 2003, also fully patched with all available updates.
> - Network of about 40 users
> - NO RPC over HTTP
> - NO cached Exchange mode
> - NO .pst or .ost files permitted
> - no IMAP or POP3 connections are permitted
> - No ActiveSync connections are permitted
> - single Exchange server, no front end/back end configuration.
> - Currently, there are 2 domain controllers on the network, both 
> functioning
> without error (the Exchange server and another server).
> -  Domain is in mixed mode.
> - No firewalls, Windows or otherwise, between desktops and Exchange.
> - No related errors in event logs of servers or desktops
> - No AD errors on domain controllers
> - No DNS issues
>
>
> Issue:
> We have an old Windows 2000 server, that was the original domain
> controller/file print server for the domain.  About 3 years ago, we 
> installed
> a new Windows 2003 server and moved all of the AD rolls, DNS and DHCP off 
> of
> the old server and onto the new server.  This server was NEVER an Exchange
> server.  We disabled DNS and DHCP serivces at that time and ran DCPromo to
> remove the old server from the domain.  All went well.  There were no 
> issues
> or errors.  Unfortunately, we left the old server up and running just in 
> case
> there was a file that someone needed.  The old server was left running in 
> the
> rack and was forgotten about.
>
> Now, we need to install some new servers and we need the rack space, so we
> have to fully decommission the old server.  Everything works fine when we
> shut it down, EXCEPT for Outlook 2003.  If the old server is shut down,
> Outlook takes over 3 minutes to open on every desktop on the network.  The
> minute the server comes back up, Outlook opens normally.
>
> We moved from Exchange 2000 to Exchange 2003 (fresh install on new server,
> used Exmerge to move contents of mailboxes) about 2 years ago.  The old
> Exchange server has been off of the network since the upgrade.
>
> If I open Outlook with the /rpcdiag switch with the old server down, the
> first 2 connections are made immediately, with normal speed.  The delay is
> between the second and third connection.
>
> The Outlook web client continues to function normally, whether or not the
> old server is on.
>
> I have tried all the safe mode switches.  /safe:1, safe:3 and safe:4 do 
> not
> affect startup speed.  If I start in /safe:2 (starts Outlook without 
> checking
> mail at startup), Outlook opens at normal speed.  I have also tried the
> /cleanprofile switch, which had no effect.
>
> Other than the issue with Outlook, all logins/network applications and
> resources function normally, whether the old server is up or not.
>
> I searched through the registry of one of the desktops.  I do not see any
> references to the old server by either name or IP address.
>
> I would appreciate any ideas on how to resolve this problem.
>

date: Mon, 5 May 2008 17:02:23 -0700 author: Randy