J
Jon
We're a ~700 person organization spread across 9 sites.
We've got 12 domain controllers, most of which are GC's.
We're Win2ksp4 _everywhere_.
We recently closed one office; all the folks moved to
another office. That offices DC was retired per a set of
steps I found either in TechNet or in a KB article
somewhere. We didn't have any problems -- or so we
thought.
Here's the thing -- users from the closed office are
experiencing strange latency. It's most visible the
first time a user attempts to print. Printing can take 2-
3 minutes to complete, during which time the application
from which they printed is completely unavailable.
We've since asked users to delete all printers that were
from the old office. No improvement -- or, at least, no
noticable improvement.
I'm also seeing lots of _successful_ security events
listing the retired domain controller as the service.
How can that be?
Anyways .. what could I be missing in this scenario which
is causing us these problems?
Thanks,
Jon.
We've got 12 domain controllers, most of which are GC's.
We're Win2ksp4 _everywhere_.
We recently closed one office; all the folks moved to
another office. That offices DC was retired per a set of
steps I found either in TechNet or in a KB article
somewhere. We didn't have any problems -- or so we
thought.
Here's the thing -- users from the closed office are
experiencing strange latency. It's most visible the
first time a user attempts to print. Printing can take 2-
3 minutes to complete, during which time the application
from which they printed is completely unavailable.
We've since asked users to delete all printers that were
from the old office. No improvement -- or, at least, no
noticable improvement.
I'm also seeing lots of _successful_ security events
listing the retired domain controller as the service.
How can that be?
Anyways .. what could I be missing in this scenario which
is causing us these problems?
Thanks,
Jon.