Thanks Chris
I have created folders on the server's harddrive in the structure you recommended. However I'm not sure how to make it so that the home folder for each user is automatically generated to the Users folder. The document you provided only provides *recommendations* on how to set it up, but doesn't provide instructions on how to do it.
Same goes for offline files, don't know how to configure it. Some steps would be appreciated.
Also I've googled for some Active Directory resources and didn't really find anything great - I found a lot of technical mumbo jumbo that has nothing to do with practically setting up users and their shares etc. So if you know of any good resources, please share :p





by: Chris-DentPosted on 2009-06-03 at 08:32:15ID: 24537676
> Should I create users or computers?
Users, yes. Computers will be created as you join them to the domain. You can create the account in advance of that if you wish, but it won't do any good until the computer links to it.
> How should I structure the file shares?
There are no hard rules for this. Your structure would ideally aim to be logical and easy to for you to manage.
For example, I have a structure like this:
SomeDrive
| - Data
| - Users (Contains a home directory per user)
| - Departments (a directory per department. So departments can share things)
| - Projects (a directory per project)
| - Shared
Shared has a note. It's hidden and read only. The only person that can add to it is me, in my experience areas which everyone has access to and which can contain anything quickly become exceptionally messy.
In addition to structuring the data in a way that is clear and easy to manage the permissions applied to those also need to be easy to manage.
When assigning permissions try to avoid assigning permissions to user accounts at all costs. It can become very difficult to manage permissions when assigned like that. Instead, permissions should be assigned to groups, users should be placed into appropriate groups.
> Do I need any login scripts? If so what do I put in them?
Are there any repetitive tasks that you normally perform on login?
My scripts map a few drives, copy over a few templates, and updates a VPN profile file. Not much, but nice to have it done automatically.
> Should I map any drives?
If it is convenient for everyone to have that available then sure, why not. It's nice to have consistency and worth not having to repeat "how to map a drive" instructions to everyone.
> What else can I do that might be useful and impressive?
Hmmm....
You might consider redirecting My Documents for everyone, and making it available Offline. Then you can get away from them storing everything locally. To your end-users it should still seem like it's stored locally.
MS have a few recommendations on this:
http://technet.microsoft.c
HTH
Chris