Terminal Server slow since AD migration

[djmg2]

Hi all,

We aare undergoing an NT4 domain to 2003 Active Directory migration at
the moment. We have approx 7 or 8 servers all part of the NT4 domain,
one of these is a Windows 2000 Terminal Server (which is also a DNS
server). We are also migrating from Exchange 5.5 to 2003 at the same
time.

An external company are providing a lot of help with the migration.
However, since the initial stage last Tuesday, our Terminal Server has
started running very very slowly and has unexpectedly rebooted twice.
The event log shows a lot if event ID 9999 which I have found is not
too much of a worry. We also have a lot of 1008 - "the open procedure
for service McShield in DLL [path]dssdata.dll failed. Performance data
for this service will not be available" - this is appearing twice every
second and fills the event log up such, that I cannot work out when it
started.

Although we have had the correct number of licenses, only as part of
the A/D rollout did we have to create a license server for it.

We also run Novell Netware 6 and have the latest Novell client on the
server. It was running fine a few weeks ago.

Is there anything obvious you suggest I check as to why this server all
of a sudden has slowed down and become unstable?

Many thanks in anticipation,

Mat G
Birmingham, UK

 

[Vera Noest [MVP]]

How exactly have you migrated?
Installed a new 2003 DC and moved the W2K terminal Server into the
2003 AD domain, as a member server?

I would say that the EventID 9999, Source DNS, *is* the most
important one.
The description, taken from EventID.net:
http://www.eventid.net/display.asp?eventid=9999&eventno=281
&source=DNS&phase=1

"DNS Server has encounters numerous run-time events. These are
usually caused by the reception of bad or unexpected packets, or
from problems with or excessive replication traffic. The data is
the number of suppressed events encountered in the last 15 minute
interval."

I know that some of the KB articles about this event state that
"The occurrence of these event error messages does not necessarily
indicate a problem with the DNS service", but given the performance
problems, I would say that you have a DNS and/or replication
problem in the new domain. At least, that should be your first line
of research.

Regarding EventID 1008, Source perflib:
(again from EventID.net:
http://www.eventid.net/display.asp?eventid=1008&eventno=70
&source=Perflib&phase=1

Service: McShield - See "Network Associates Support Solution ID:
nai15090", "Network Associates Support Solution ID: nai6288", and
"Network Associates Support Solution ID: nai19416".

McShield - dssdata.dll - You may recieve an error in event viewer
about Mcaffe's Perfmon Counter's under NT4 Terminal server. To fix,
research the following SolutionID: nai6288 under Mcaffe's web site.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

(e-mail address removed) wrote on 13 mar 2006 in
microsoft.public.win2000.termserv.apps:

Hi all,

We aare undergoing an NT4 domain to 2003 Active Directory
migration at the moment. We have approx 7 or 8 servers all part
of the NT4 domain, one of these is a Windows 2000 Terminal
Server (which is also a DNS server). We are also migrating from
Exchange 5.5 to 2003 at the same time.

An external company are providing a lot of help with the
migration. However, since the initial stage last Tuesday, our
Terminal Server has started running very very slowly and has
unexpectedly rebooted twice. The event log shows a lot if event
ID 9999 which I have found is not too much of a worry. We also
have a lot of 1008 - "the open procedure for service McShield in
DLL [path]dssdata.dll failed. Performance data for this service
will not be available" - this is appearing twice every second
and fills the event log up such, that I cannot work out when it
started.

Although we have had the correct number of licenses, only as
part of the A/D rollout did we have to create a license server
for it.

We also run Novell Netware 6 and have the latest Novell client
on the server. It was running fine a few weeks ago.

Is there anything obvious you suggest I check as to why this
server all of a sudden has slowed down and become unstable?

Many thanks in anticipation,

Mat G
Birmingham, UK