G
Guest
Guest
Archived from groups: microsoft.public.win2000.general (More info?)
I have a Windows 2000 AS that is setup as a Terminal Server. The server is
not used over the weekend. Every Sunday night I login to the server remotely
and check the speed. Most of the time it is running very slowly. At this
time, no one is on the server, other than myself. There is only one batch
process (AV update check and scan) which runs at 1:00 AM. If it is running
slow, I reboot the server and all is fine. If I do not reboot the server, it
will be so slow that users logging in on Monday have a great deal of
difficulty connecting. I have checked to see what is running on the server
and every time it is "spoolsv" pegging the CPU. Is there a known issue with
the print spooler peggin the server? During time when the server should be
pretty much idle?
Thanks!
I have a Windows 2000 AS that is setup as a Terminal Server. The server is
not used over the weekend. Every Sunday night I login to the server remotely
and check the speed. Most of the time it is running very slowly. At this
time, no one is on the server, other than myself. There is only one batch
process (AV update check and scan) which runs at 1:00 AM. If it is running
slow, I reboot the server and all is fine. If I do not reboot the server, it
will be so slow that users logging in on Monday have a great deal of
difficulty connecting. I have checked to see what is running on the server
and every time it is "spoolsv" pegging the CPU. Is there a known issue with
the print spooler peggin the server? During time when the server should be
pretty much idle?
Thanks!