RE: User rights on Terminal Services
From: Jay Lagorio (firstname.lastname@example.org)
Date: Thu, 6 Mar 2003 17:30:28 -0500 From: "Jay Lagorio" <email@example.com> To: <firstname.lastname@example.org>
To see what application uses what parts of the registry (and when),
System Internals (http://www.sysinternals.com/) has a tracer that I
swear by, along with a network stack and file system monitor to back it
Your ActiveX situation reminds me of one I have whenever I want a
standard IUSR_MACHINENAME user in an ASP page to use one of my ActiveX
DLLs. You'll need to find the OCX and DLL files that the application
uses and assign read ACLs on them for the user or group. They're most
likely located in the %root$\Winnt\System32 folder, but being a custom
app, they could be anywhere else.
Win2k Server with all latest patches and Terminal Services installed.
We have a custom built application that we got from a third-party that
is causing problems through terminal services. Through my login the
program works w/o problems but I am an administrator and do not wish to
have to assign admin rights to every user who may need to access the
Can anyone give me an indication as to what rights one may need for:
1) Opening and closing files from a folder on the server (I gave the
respective users full rights on these folders, but the problems still
2) Creating/loading/using ActiveX Controls and COM servers.
I am not sure if there is any registry tomfoolery in it - what is the
best way to discover if the program uses the registry? (I'm slightly new
at this; I realise this is a newbie question, so go easy on me)
Oh, FYI, the problems I refer to are all ActiveX related and refer to
the fact that some controls cannot be loaded and/or created properly.
Indecision is the key to flexibility.