Discussion Locked

Home Directory Privileges

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I inherited responsibility for a Win 2000 Server and found that no user home directories were assigned. I assigned home directories in the user profiles, and the mapped drive does now appear in the user's My Computer. But the mapped drive icon cannot be opened - the message says the user has insufficient privileges. Yet, all privileges to the directory are assigned to the user at the server. What am I missing here?

17 replies

by jacksanders

I've had problems with our Windows 2000 Servers by creating the Home directory and user space before entering in the path in Active Directory Users and Computers. My solution for that situation was to let Active Directory create the Home folder path for me:

First try creating a temp/test user. Open Properties on the test user whom you want to create a Home directory for using Active Directory Users & Computers. Go to the Profile tab and use \\comp_name\homepath\%username%

(of course, change comp_name and homepath to match your own) Keeping %username% , as typed, is the key - this will let Active Directory create the user Home folder and assign the default permissions for you. Later you can break the permissions inheritance and add your own, such as Administrator access.

May not be what you're experiencing, but allowing AD to create the folders solved my own "permission denied" problems.

Good luck!

by cal.williams

I was quite sure I had tried this, but after reading your well-written answer I went over and tried it again. Unfortunately, no, sorry to say this still does not work. I must have walked into a little trap here, because apparently the previous (and long-gone) support guy, who installed this server, was never able to to get it to work either.

by cal.williams

Sorry, I added a comment above instead of here where it should be. If you have any further thoughts, please answer again. I do think that inheritance could be involved here, but don't see how to decipher it other than what I see as privleges on the resulting folder, which are full for both administrator and user (and then ignored by the workstation.)

by cal.williams

This may be the interesting part. The parent directory is "shared for adminstrative purposes" and I cannot see or modify the permissions. So, I can't tell or control what permissions the home directory is inheriting. Either something is wrong here or I am (again) missing something obvious.

by jacksanders

I assume your Win2000 Server is NTFS formatted. The "shared for adminstrative purposes" appears in Win2000 default-mapped shares, such as the C$ default hidden share. I would suggest, for now, abandoning the existing home directory and creating another to test on.

Try creating a new home folder, say c:\tempdir, and share it with default permissions (Everyone group, full control). Go to AD, create a test user, and assign drive X:\ (for example) to \\comp_name\tempdir\%username% and see if you can't login as the test user and use the new X: drive.

If you can, then there is a problem with the existing home directory. The good news is, if no one was able to use it, you can easily abandon and remove it.

by cal.williams

More info: Whoever set this up sold his client MUCH more server than they needed. There are four SCSI hard drives, C: through E:. I found the home directories set up in \\servername\users, which is the whole damn E: drive!! And the other drives are at most 25% used. Sigh.

by shanghai sam

About your comment on 4/9/02.
You can try two options:
-on parent folder which is "shared for administrative purposes" make other share which will allow you to control share permissions.
-on home directory disable and set the permission as you need.
About your comment to the answer 3
-I has a bad experience with setting the permission on server from my workstation. I use on my workstation for test only and after that I ignore it. Surprise!When I try to modify the permissions for a folder at server from my workstation in fact the results was different.
I don't have time to check the problem but you can try to assign the permissions from other location.

by cal.williams

Yes, a directory in another partition will work, and if that is the work-around I ultimately have to use, findmattk@yahoo.com will get my points. But I am severely irritated that I have 25% of my available hard drive space named "Users" and I can'tuse it as it was intended! Darned if I can see any difference between the partion I can use and the one I cannot. So I will hang in there awaiting more suggestions for a while longer.

by cal.williams

We finally gave up and mapped the home directories in the local accounts on each workstation. Very inconvenient and labor intensive. I am convinced that something went wrong when my predecessor did the original installation.

This discussion is closed to new replies.