[steve harrison]

hi
i want to set up another user in win2k pro.
One for admin - so I have full rights over everything..
The other user - default at the moment) can only Read files.how do i go about it..
thanks steve..

[Down8]

Start -> Settings -> Control Panel -> Administrative Tools -> Computer Management

System Tools -> Local Users and Groups -> Users

Right click in the display area -> New User...

Set up the account, then right click on the new account name and select -> Properties -> Member of -> Add...

Add the new user as one of the Geust users group. You can get an explanation of each group in the Groups folder below the Users folder.

I don't know of a way to let someone only read files, but this type of account will be the safest, as the user cannot play with you system files. It may be possible to set a folder as 'read only' as the administrator, and keep the Guest from writing things that way, but I'm not sure exactly how you would go about that without having to change it back to writable every time you login as the Administrator.

-bZj

------------------
- brian@infinitejones.com

Code:

==================             ===================
Home built system:             Also, just for fun:
Soyo SY-7VCA                   AST Bravo LC 4/66d
[VIA T82C694X]                 Intel 486 CPU
[onboard sound]                40MB RAM
PIII 500E [flip chip]          500 MB Conner Hdd
PNY 128MB PC100 RAM            3 1/2, 5 1/4, 2x CD
Stealth III S540               3com Etherlink II
3com Etherlink III             Adaptec AHA-1545 SCSI
Quantum Fireball 10.3GB Hdd    [to host some files on:]
HP A4331D 20" Monitor          1.3GB internal Seagate
Win2K Pro [v5.00.2195, SP-1]   2 2GB external Seagates
[format => clean install]      Windows 95 [v4.00.1111]
Covad 768kbps sDSL [shared]    pcAnywhere 9.2
                               [so I can leave it in the closet]

[felix]

Set the permissions on the folder in question to read/list for both files and directories for that specific user.

Right click on the folder > properties > security and go from there.

------------------
Written on Win2000 using:
PII 300
Aopen AX6B
160mb RAM
i740 8mb
SBLive! Value
20gb Seagate
6gb WDCaviar
Pioneer 32x CD-R (Slot)
Lifeview FlyVideo '98 FM
Realtek RTL8029AS 10mbit
Accton EN1660 10mbit
Osborne MO117 17"

Using 100% Australian Made recyclable electrons

[steve harrison]

thanks guys for the answers..
i may got a bit confused on what to say ,it should of said the second user at the minute can only read files but i want him/her to have more access so does the answers above still apply to what i,m saying..
steve..

[felix]

Yeah,
If the person does not have an account, create the account using the listed process.

Once the account is created, you can then, through the process I described, lock down specific drives, directories and even files to any combination of read/write/execute/list you wish to see.

By doing this you can ensure all users only have the access they require.

------------------
Written on Win2000 using:
PII 300
Aopen AX6B
160mb RAM
i740 8mb
SBLive! Value
20gb Seagate
6gb WDCaviar
Pioneer 32x CD-R (Slot)
Lifeview FlyVideo '98 FM
Realtek RTL8029AS 10mbit
Accton EN1660 10mbit
Osborne MO117 17"

Using 100% Australian Made recyclable electrons

[BigBucks]

I've created new users - no problem. But when the users log on they have great problems using alle the programs installed by me.
What do I have to do to make it possible for all users to use all the programs (also any future users i might create)?

[CUViper]

don't forget that your drives must be NTFS to use those security functions....

[MoreLight]

First off don't make your users members of the Guest group. That is disabled by default in Win2000 for good reason.

Make your users members of the built-in groups according to the amount of permissions they will need. Those programs you installed were more than likely installed when you were logged on as Administrator. You can do anything anywhere including system and hardware specific things that no other group can by default, unless you make them members of the different Admin groups, and that is probably what you are trying to avoid.

Other than Administrator, your best bet for giving someone power over running apps, but not making them GOD is to add them to "Power Users". They have the ability to create and modify local user accounts and share resources.

This is assuming that you running on a local computer with secure logon for each person using your computer or a small networked workgroup.