A
Al Williams
Server 2003 Standard TS, SP2, all patches.
We have a recurring problem where a particular (older) client/server LOB
application (Visual Manufacturing) slows down and becomes pretty much
unusable immediately after the TS user changes their domain password. The
user can quit the application and logoff terminal server then login again
and it continues to be slow, rebooting their PC also has no effect. Other
TS applications (like Word/Excel/Outlook) run fine for the affected user,
it's just this one older application. Other TS users have no issues with
this same application.
The only thing that fixes it is a reboot of the terminal server.
This has happened to pretty much all the users at one time or another and
seems to be related to changing the domain password after being prompted it
is expiring. Not really sure why the domain password would affect this
application. It doesn't use it for it authentication, it has it's own
password mechanism and a LINUX based SQL server.
Any ideas on why a reboot fixes it or what I should look for next time?
Thanks.
--
Allan Williams
We have a recurring problem where a particular (older) client/server LOB
application (Visual Manufacturing) slows down and becomes pretty much
unusable immediately after the TS user changes their domain password. The
user can quit the application and logoff terminal server then login again
and it continues to be slow, rebooting their PC also has no effect. Other
TS applications (like Word/Excel/Outlook) run fine for the affected user,
it's just this one older application. Other TS users have no issues with
this same application.
The only thing that fixes it is a reboot of the terminal server.
This has happened to pretty much all the users at one time or another and
seems to be related to changing the domain password after being prompted it
is expiring. Not really sure why the domain password would affect this
application. It doesn't use it for it authentication, it has it's own
password mechanism and a LINUX based SQL server.
Any ideas on why a reboot fixes it or what I should look for next time?
Thanks.
--
Allan Williams