General discussion

Locked

Client Application permissions

By smithy ·
I am sure this is a staight forward question if you are uased to a Win 2K/NT4 network but i am used to win 98. I am now replacing Win 98 PC's with Win 2K PC's on a NT4 network. I would like to load the client machines with all of normal applicationsbut make these available to anyone who logs onto that machine. Basically who should i be logged on as when i load the applications. Do i initially log on as administrator and then add the local user to the local administrators group and then load all of the applications logged on as the user or load all of the applications logged on as administrator. Should all users be in only the local users group ?
Any help much appreciated.....

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Client Application permissions

by Curacao_Dejavu In reply to Client Application permis ...

This is a little complicated since not all programs are "aware" of w2k or even nt.
Ideally you are supposed to install the application as the local administrator and automatically all other users are supposed to have it when they login. Sometimes you have to create a shortcut for them in their if they don't have it. Those ones are they easy ones.
The difficult ones are the ones that only works whith the administrator but not with the users. Those are permissions issues of the installation folders or in the registry (hkey-local machine-software-softwarename) you gave to use regedt32 to give them the permissions. Sometimes what works also is to give the user temporary admin rights and install the software with that useraccount.
When normal installation with the administrator account doesn't work contact the software helpdesk as they should know how to solve it, if they don't know use the approach described earlier.

The users should be only local users.

regards,

Leopold

Collapse -

Client Application permissions

by smithy In reply to Client Application permis ...

Poster rated this answer

Collapse -

Client Application permissions

by curlergirl In reply to Client Application permis ...

For most applications, you need to be logged on to an NT/Win2K workstation as a local admin to install the application, because the install routine will create registry entries that non-admin users do not have permission to create. Once the app is installed, all you need to do to make sure any user can run it is to put a shortcut on the desktop and/or Programs menu for the Default User profile (/%systemroot%/Profiles/Default User for Winnt or /Documents and Settings/Default User for Win2K). In order to run some apps, the users need to be in the local Power Users group, so this is how we usually set them up (not as local admins). If you're on an NT/Win2K domain, one easy way to do this is to put the global domain group "Domain Users" intothe local Power Users group. Many programs do not create any further entries in the Current User registry hive but those that do will be able to function normally under these circumstances. The only exception to this would be if your workstations have NTFS partitions rather than FAT or FAT32. If so you have a higher level of workstation security and you would have to be sure that the users have appropriate local folder and/or file permissions for what they need to run. Hope this helps!

Collapse -

Client Application permissions

by smithy In reply to Client Application permis ...

Poster rated this answer

Collapse -

Client Application permissions

by smithy In reply to Client Application permis ...

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums