There's not hard set rule of course, but I'll tell you what I do.
First, I make the users parent folder which will contain all of the user home folders, and I generally name this parent USERS. For NTFS permissions, I turn off propogation from its parent, and I set Administrator and Domain Admins to have full control, and then in Advanced NTFS permissions, I set domain users to have only list directory contents and on this folder only.
I then create a share on this parent, and I make it a hidden share, i.e. users$, and I set the share permissions as: Administrator, Domain Admains, and Domain users each with Full Control. Domain users need full control on this share because it's through this share that they each will access their individual home folder.
IN ADUC when I create a user, I go into the user properties / Profile tab / Home Folder Connect To: / and enter \\servername\users$\%username%
The home folder is automatically created with appropriate permissions on the folder itself. I do a couple of folders and then test for desired permissions and functionality before I create or modify users en masse.
I generally set the user home folder and all network shares through drive letter mappings in a logon script, as I do not encourage any of my clients' users to browse Network Neighborhood / Network Places. If one happens to browse, the users$ share is hidden, and if they know enough to find it by UNC \\servername\users$, sure they will see all of the users home folders, but should be greeted with "Access is Denied" if they attempt to browse into anyone's home folder except their own.
Hope this helps.