Terminal Server registry

[Guest Jeff]

On our stand-alone terminal server users can use one of our applications as

normal domain users. The initialization of the app writes registry entries

that configure database connections, etc. When I move the user to one of my

farms, which is identical on apps, etc as the stand-alone, the user gets an

automation error when trying to log into the application. If I make domain

users local administrators it works flawlessly. I have even made the app

work as local admin for the user, logged out and had it save to the roaming

profile, remove the domain users from the local administrators to preserve

all the settings. once i do this the user gets the automation error again.

Any ideas on why this is happening? Any ideas on where the terminal server

configuration may differ from the stand-alone server to the farm? As far as

I can tell they are identical. Any ideas to check would be greatly

appreciated.

[Guest Jeff Pitsch]

Re: Terminal Server registry

 

Use process monitor (update regmon/filemon) to track down permission

errors in the registry and file system. You can download it from

http://www.sysinternals.com

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

Jeff wrote:

> On our stand-alone terminal server users can use one of our applications as

> normal domain users. The initialization of the app writes registry entries

> that configure database connections, etc. When I move the user to one of my

> farms, which is identical on apps, etc as the stand-alone, the user gets an

> automation error when trying to log into the application. If I make domain

> users local administrators it works flawlessly. I have even made the app

> work as local admin for the user, logged out and had it save to the roaming

> profile, remove the domain users from the local administrators to preserve

> all the settings. once i do this the user gets the automation error again.

> Any ideas on why this is happening? Any ideas on where the terminal server

> configuration may differ from the stand-alone server to the farm? As far as

> I can tell they are identical. Any ideas to check would be greatly

> appreciated.