[hunterleej]

We've got a Primary Domain server and two terminal servers... 4 offices app. 40 users who log in to either #1 or #2... a couple of years ago we had Scansoft Omni 15 installed on the terminal servers... its never worked satisfactory and so yesterday I removed it from both terminals through add/remove... users are having error windows pop up that relate to Omni... I've rebooted everything and it still happens... the pop up windows can be "OK'D through and everything works just fine but is certainly annoying. I need help!! Thanks

[jstrike]

Sounds like there's still some info left in either the registry or the startup group that wants to start an Omni driver.
Not sure if CCLeaner runs on Server '03 but it's worth a shot. (It'll make a backup of your registry before it makes changes too)
If not...
Login as the administrator and run regedit.
Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run.
Look for anything in there related to Omni.
Typically what I do is double click on the Name and put :: in front of the Value Data to disable it. That way if you mess something up... something I NEVER do :D... you can go back and easily undo your changes.
You can also do a Find for Omni in the registry and remove or disable what you find.

Don't forget to make a backup of your registry before you start.
(Sorry, had to say it)

[chuckhole]

Terminal Server is a totally different beast when it comes to adding and removing applications. Depending on what version of WTS you are running, you may have to manually change it to Install Mode (at cmd prompt: change user /install). In any case, you must use the Control Panel Add/Remove Programs. Do not just run the executables.

Not all applications are written to be multi-user aware in an evironment like Terminal Services. I have had particular problems with some of the HP Plotter drivers and some of the Adobe products. Some applications require that you run an application compatibility script which allows some of the DLL's to be run in multi-user mode.

Since you have already removed the application, there will be a lot of registry cleanup to perform since each of the user profiles may have some entries to be removed. If you allow your TS Clients to logon with Admin level permissions, this makes it even worse.

Check out a 3-part series of articles devoted to the specific differences in the use of the Registry in Terminal Servers - How Applications use the Registry in Terminal Server Environments (Part 2 of 3) - From BrianMadden.com.