Open Office won't start in terminal session as regular user

[dasein47]

I have a somewhat strange problem.

W2K with terminal services enabled in application mode. I've installed open office. When logging in as administrator i can run open office just fine. But if i log in as a regular user - as members of the Users group only, it will not run any office program when starting starting them. after launching it, it runs in taskmanager for about 5 seconds or so and then disappears with no error or event log, indicating that it is running or has crashed or anything.

If i put them in the administrators group or even the power users group, they can launch the program. I need to prevent them from installing software on their terminal sessions.

Any ideas?

Kip Tobin

 

[Lightspeed1]

Hey Kip,
Do you have any kind of Group Policy enabled? The only thing that I can think of is to create a TS users group, add your users and then go into the admin tools-domain security policy-Local policies(I think)-there should be something called User Rights Assignments, the macro view has pretty much every right possible and if you right click on the permission that you want then click security it will allow you to assign a specific right to that group (TS users)Just add rights until you get your most restrictive security while still enabling users to run your app. There is also a tool in the (again, I think) support directory on the server CD that is a MMC snap-in that will allow you to analyze the permissions you have assigned. Security Configuration and Analysis I believe is the name of the snap-in. Sorry so much of this is ambiguous!!
Hope this helps in some small way
Regards,
LightSpeed1

 

[Techojunkie]

It sounds to me like you have a permissions problem somewhere along the line, the creation of a TS user group as stated in the previous posting, sounds like a good idea. If the users have other domain rights, these could be conflicting too, specified user rights can get you into all sorts of wonderful areas of Windows 2000. I know my response may not offer the world, but I do think there is a permissions problem, either on the TS server or could be domain permissions as well.

Hope you find an answer to your problem, actually if you do let us know, I'm sure other tech's will be interested in your findings.

Cheers,

Techojunkie