A
Arthur
Hello,
We have an application that runs in Terminal Services. The users log in and
load the app and use it. They view their reports via an ActiveX control
viewer that we've customized.
Their windows profile doesn't seem to allow them access to load the control
so they get the usuall "unsupported function..." message when the
application tries to load it under their user profile. If we make the users
all administrators, then it works fine.
Any words of wisdom from the security experts out there? Any settings or
policies we should be looking at? I'm not the security guy but one of the
developers. Our security folks can't seem to figure this one out and your
help would be greatly appreciated. Thanks very much.
We're running Windows 2003 Enterprise Edition with the latest service
pack/fixes.
Arthur
We have an application that runs in Terminal Services. The users log in and
load the app and use it. They view their reports via an ActiveX control
viewer that we've customized.
Their windows profile doesn't seem to allow them access to load the control
so they get the usuall "unsupported function..." message when the
application tries to load it under their user profile. If we make the users
all administrators, then it works fine.
Any words of wisdom from the security experts out there? Any settings or
policies we should be looking at? I'm not the security guy but one of the
developers. Our security folks can't seem to figure this one out and your
help would be greatly appreciated. Thanks very much.
We're running Windows 2003 Enterprise Edition with the latest service
pack/fixes.
Arthur