Automatic creation of user folders for home, roaming profile and redirected folders.
Here is great step-by-step instructions on creation of Home, roaming profiles, and redirected folders.
I need to review this and see what impact it would have if these locations are over the WAN. I’d also like the redirected ‘My Documents’ to be the same place as the home drive. Then I need to setup offline folders for the home drive.
Periodically we’re asked "what is the best way to auto-create home, roaming profile, and folder redirection folders instead of Administrators creating and configuring the NTFS permissions manually?" The techniques in this post requires you to use the environment variable %USERNAME% in the user’s home folder attribute when you create the users account.
[tags]active directory[/tags]
Hi great article, we've been using that technique for a while to create user folders. I know, I know, User Home folders are a thing of the past, but we do use them here. We typically place the “My Documents” folder in the “Home Folder”. Recent security changes imposed on us have taken the ability to use NET.EXE and NET1.EXE away from us for quick and dirty drive mapping capabilities via .cmd files. As an interim solution to get over-the-hump of implementing this security we have turned on the Home Folder setting in ADUC for all users.
Our Environment is one of using 2003 (equivalent) DCs, and strictly running XPSP3. One interesting issue we have experienced is that when attempting to use RunAs off of the Start Menu in order to elevate credintials for certain tasks, systems don't seem to be able to find the application. If we drill down via explorer to the actual file and right-click RunAs there, no problem. Is this normal behavior? and what is causing it?
Hi great article, we've been using that technique for a while to create user folders. I know, I know, User Home folders are a thing of the past, but we do use them here. We typically place the “My Documents” folder in the “Home Folder”. Recent security changes imposed on us have taken the ability to use NET.EXE and NET1.EXE away from us for quick and dirty drive mapping capabilities via .cmd files. As an interim solution to get over-the-hump of implementing this security we have turned on the Home Folder setting in ADUC for all users.
Our Environment is one of using 2003 (equivalent) DCs, and strictly running XPSP3. One interesting issue we have experienced is that when attempting to use RunAs off of the Start Menu in order to elevate credintials for certain tasks, systems don't seem to be able to find the application. If we drill down via explorer to the actual file and right-click RunAs there, no problem. Is this normal behavior? and what is causing it?