kiln <> wrote on 13 okt 2006 in
microsoft.public.windows.terminal_services:
> In article <#>,
> ....atya hoo.com
> says...
>> In news: om,
>> kiln <> typed:
>> > In article <>,
>> > ....atya hoo.com
>> > says...
>> >> In news: om,
>> >> kiln <> typed:
>> >>> On a non-AD windows 2003 std server acting as a terminal
>> >>> server, regular users used to be able to install programs
>> >>> no problem. I've done nothing to that box other than
>> >>> service packs in the last two months. However now when they
>> >>> try they get a permissions error: "You don't have the
>> >>> required priviledges to continue the installation. blah
>> >>> blah (couldn't get write access to HKLM\Software)" Any help
>> >>> appreciated.
>> >>
>> >> Well, my first question would be, "why on earth would anyone
>> >> want users installing anything at all, let alone on a TS
>> >> box?" You say "regular users" - but what groups are they in,
>> >> in local users & groups?
>> >>
>> > They are members of the users group and the remote desktop
>> > users groups. The odd part is that they were able to install
>> > before. I've changed nothing in the meantime, other than the
>> > service packs.
>>
>> Non-administrators do not have permission to install (most)
>> software. I don't know how this was working before, although
>> it's possible that whatever they were trying to install wasn't
>> touching the restricted portions of the registry & file system.
>> If you'd manually reset permissions on both, previously, that
>> might've explained it - or loosened restrictions via group
>> policy, maybe that's the reason they could before. Also,
>> remember that in TS, most software needs to be installed at the
>> console, using add/remove programs - not by running setup
>> files.
>>
>> But seriously. think about this. Why would you want them to
>> have that ability at all? I don't even like to permit that on
>> regular workstations, but on a terminal server? No freakin'
>> way. Too much can go wrong that would affect *all* users on
>> that box.
>>
> It's a software package that each user installs if they need it,
> via rd. This is a testbed server deployment. The software that
> 'regular users' were able to install two months ago is the very
> same software that won't install now. No one has admin rights on
> the box but me, and I didn't change anything other than the
> service packs. The main parts of the app are being installed via
> the control panel add/remove by an admim; the client parts used
> to be installed by running the separate exe directly.
Seems to me that the error message is pretty self-explanatory:
> "You don't have the required priviledges to continue the
> installation. (couldn't get write access to HKLM\Software)"
No user should require write access to HKLM.
This application seems not to be TS compatible, since it wants to
write user settings to HKLM in stead of HKCU.
As lanwench pointed out, normal users should never have been
allowed to do this, SP or not. But I guess that you installed the
Terminal Server in "Relaxed Security" compatibility mode. That is
more or less equal to making all users Power Users, and allows
software installation by users. It's one of the fastest routes to
an unstable TS.
Understanding Terminal Server's Permissions Compatibility Options
http://www.brianmadden.com/content/content.asp?id=480
__________________________________________________ _______
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Similar Threads
Linear Mode
