Run the Task Manager on your Exchange Server and see what's eating up
all the CPU Pocesses.
We have this problem occasionally with mssdmn.exe running 100%
utilization. We just kill this process and things go back to normal.
As of yet, no one at MS has been able to explain why this occurs.
Until recently, our Exchange 5.5 Server has been running
smoothly. Lately however, it has been running S..L..O..W
on occasions.
The only thing that's changed is we
have recently started upgrading some of our NT 4.0
workstations to Windows XP workstations.
Almost all those users
Running fine for us in a mixed nt/2k/xp area. We have about 800 users on a
PIII-450 Xeon with 1gig of ram and 3 arms. No performance problems for any
of the users. Have you checked your DNS and WINS setting on the XP systems,
how does name resolution to your exchange server work from the cmd
Administrator
Central Community College - Grand Island, NE
(V) 308.398.7361(F) 308.398.7399
[EMAIL PROTECTED]
-Original Message-
From: Bob Sadler [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2003 8:48 AM
To: Exchange Discussions
Subject:RE: Exchange 5.5 Server hammer-age
Just to give you a comparison, I'm running a Dell PE 6600, 2 Gigs RAM,
dual 1.4 GHz processors, 900 users spread over 3 Message Databases and
two RAID arrays. We still get the flag. I get the flag when I'm sitting
still too, no manual activity on the laptop that I'm using.
The flag is set by
:[EMAIL PROTECTED]
Sent: Monday, August 18, 2003 08:52
To: Exchange Discussions
Subject: RE: Exchange 5.5 Server hammer-age.
Just to give you a comparison, I'm running a Dell PE 6600, 2 Gigs RAM, dual
1.4 GHz processors, 900 users spread over 3 Message Databases and two RAID
arrays. We still get
6 matches
Mail list logo
