>>Subject line changed to accurately reflect contents, so that those
>>of you with killfiles can ignore it.
>>>> [ ... ] we have a PPro 200 with 128MB of RAM
>>>>and F/W SCSI drives running *only* NT and Exchange [ ... ]
>>The above system supports NT4.0SP3 and Exchange 5.0SP1, and it's only
>>dog-slow since we put in the extra 64MB. Before that, it was hitting
>>100% CPU utilization regularly, and averaging over 90% all day. Dog-slow
>>is a big improvement.
>Dog-slow AFTER adding RAM? Something's up. Have you done any
Besides trying to watch Performance Monitor, checking Event Viewer, shutting
down all services we didn't need on the server, digging through Help, and
searching Knowledge base? If we shut down the cc:Mail Connector it works
better, but still slow. Before doubling the RAM, it'd take minutes to
open Exchange Administrator, now it's about one and a half.
[ ... ]
Quote:>You're doing it wrong. Yes, it can be done through the GUI, but it
>doesn't *have* to be. It is clear you haven't done much research on
Well, I can't seem to feed them in through Import (Export sure won't
save aliases, just the primary address of each type)--even if I could do
it that way, trying to figure out the format would take as long as
going through the GUI. Besides, I thought the GUI was the whole purpose
of all Windows products. All the data is stored in the Information Stores
anyway, which can't be directly edited. Forgive me if I find entering
"alias: userid" in a text file easier and faster.
[ ... ]
Quote:>In Linux, you can manage a lot of things in X-Windows, but a lot of
>times it's faster to do it at the CLI. Same with a lot of things in NT
>and Exchange. Research your topic before flaming.
NT and Exchange make it difficult to do most things from a command line,
usually by burying things in "databases" which aren't accessible from
anything other than the GUI tools, and those are somewhat haphazard at
Quote:>>If there's some magical competence issue here that controls the speed of
>>the boxes opening, please post it, Oh Mighty Admin. I've been working
>>with computers for over 25 years, doing network and system admin for the
>>last twelve or so. If you want to claim that I don't know what I'm doing
>>when I report the (hideous) responsiveness of an NT Server, go ahead. I
>>know what I'm seeing happen in front of me, and what hassles we've had
>>to go through with NT and Exchange. If you're not having them, you're
>>lucky--and the software is more inconstent than I thought.
>Good. With that much time in the field, you're used to reading
>documentation. Why you're not doing it here I don't know.
I've read everything that came with the software--which was the cover
of the CD case and the installation key. I'd be reading the Exchange
Resource Kit in the near future, but as we got halfway through our
MCSE effort, the owner decided he's not going to buy any more books
(we're not even getting formal training; the IS&T manager is, and he
tries to pass it on to the rest of us), just two subscriptions to
Technet which will have to live with the servers. I'll probably go
buy the Exchange RK myself, as it's hard to make notes in the margins
of a screen from the CD. I'm nearly finished with the NT Server
Networking Guide, and haven't seen anything in it that appears to
relate to the performance problems we're seeing. (Even being a speed
reader, I can only go through and absorb so much in a given time.)
Quote:>Luck has nothing to do with it. With that many years in the industry,
>you're fully aware of that. In looking over schematics for hardware
>and source code, I've yet to come across a box that says "and here
>luck makes it work."
>>We had Linux installed on one of the G6-200s for a while; it was rock
>>solid and blazingly fast. NT isn't coming close to it in performance.
>>It's not a hardware issue, because we were forced to format the Linux
>>installation and install NT instead, so it is literally running on the
>>exact same hardware (plus 64MB).
>Are you referring to the console or network access?
Console. In both cases.
Quote:>>>For every horror story you dredge up about NT, as you've done above, I
>>>can dredge up ones for Mac, Solaris, Linux, OS/2...
>>Seems to be a lot more for NT. I don't think any of the others reboot
>>if you hit CTL-ALT-SPACEBAR on the consoles.
>Just tried it on all three of my NTS boxes here. Nada. Seems like a
>localized issue to me, rather than an OS-specific one.
Happens to all the NT 4.0 servers we're tried it on; certainly happens
to all six of ours.
Quote:>>By the way, our servers were configured by a consultant, who is a
>>Microsoft Certified type--MCSE and MCT. [ ... ]
>Just as with the CNE/CNA documentation, there are MCSEs and there are
>MCSEs. My alphabet soup is MCSE, MCSD, MCT, CNE, CNA, IEEE and
>contributing IETF author. None of my certifications are paper-only. I
>use them, and have been using them.
I'm familiar with the term "paper CNE". However, none of these tests
require any real experience, it's all just answering questions. I was
under the impression that Microsoft had seen the paper CNE problem and
were trying to make the MCP process require actual knowledge. Either
I am wrong, or they failed--I don't think I have to install one NIC
to pass any of the tests.
Quote:>One instance of one machine having problems just doens't wash with me.
>I literally cannot count the thousands of NT servers I've touched this
>year. Some had problems (which I fixed), most, the large majority, did
We have the four primary servers, all of which exhibit different degrees
of problems. They were initially set up in August, and I believe we've
had to reinstall all of them at least once. One is the PDC, one a BDC,
and two are running Exchange. We went through rebuilding the Exchange
server in my building about a month ago. The BDC needed it a couple of
weeks before that. We're getting some more software that may help us
with recovery, as we can't stand the kind of downtime we're seeing.
Quote:>Where are your troubleshooting steps?
Hard to troubleshoot a server that won't boot, as our Exchange server
ended up when we tried to restore a backup while fighting an Exchange
problem. Since rebuilding, we're running the same (slow), but we lost
the databases. Our users were *real* happy. As I recall, that crash
centered around user32.dll failing to initialize, and nothing we did
(replacing the "failing" file with a clean copy, different rev copies,
searching KB) helped. Restoring was a disaster.
Quote:> What have you done to isolate
>why Ctrl-Alt-Del (which is not an OS key combination - just did it on
>the three boxes here and they just looked at me, all stupid) reboots
CTL-ALT-SPACEBAR. It's killed all four of our primary servers at one
time or another. All of them are Gateway G6-200 systems. It's real
easy to snag the left end of the spacebar when hitting the left ALT
key with the thumb, especially when in a hurry. One guy in the other
building (where the PDC and other Exchange server are located) also
did not believe it would happen--so he tried it. He's a believer, now.
We'd heard there was something about it on KB, but a search didn't
turn up anything.
All in all, I'd rather we had a Unix box doing nothing but POP3 service,
with no databases to get corrupted. But as I said previously, the decision
"Mother! I didn't expect to see you here so soon!" "Nor I you, Princess."