 |
 |
No we haven't, and there shouldn't be much of a performance hit or overhead because DFS is only a pointer to the actual share, so the DFS server doesn't handle/proxy the data traffic. Once the client is told the share resides on serverX, it goes straight to serverX for data. It probably helps using domain DFS root, so requests are load balanced, but that too should be negligable... I do domain DFS root to have redundancy, because if a DC goes offline, I shouldn't lose any DC services. dpk On 8/2/07, Troy Murray <[log in to unmask]> wrote: > Dennis, > > In the past I've tried to use DFS for users shares and found that the > performance was very poor compared to just a straight share UNC. Have > you seen any performance degradation from using DFS? > > -t > > > On 8/2/07, Dennis Kelly <[log in to unmask]> wrote: > > If you're only concerned about home directories, you can use the > > native Administrative Tool "Active Directory Users and Computers". > > Select all the users you want to modify and > > right-click "Properties". You can go to the profile tab and click > > "Home Directory" to > > modify a property for multiple objects. It does allow the use of %username% > > > > Also, to avoid this problem in the future, you may want to investigate > > the use of DFS... it's a very flexible way to mange, load-balance, > > etc. your network shares. I use domain DFS root so that I can > > replicate the published links across both domain controllers for > > additional reliability. You can then use notation like this for > > mapping user directories: > > > > \\domain.com\dfs\User\%username% > > > > where \\domain.com\dfs is my dfs root. The link "User" points to a > > share \\some-server\User. If some-server is replaced with > > some-other-server, I only need to update the DFS link on one of the > > domain controllers to point to \\some-other-server\User. > > > > Boom it's replicated, and boom no headache of remappings. I use this > > for any/all network shares here in Jackson Hole. I can send you my > > documentation on it if interested. > > > > dpk > > > > > > > > > > > > On 8/2/07, Ehren Benson <[log in to unmask]> wrote: > > > Nag- > > > > > > I was wondering if any of you windows folks ever used the tool admodify.net > > > to do mass AD changes. I am trying to use it with a LDAP filter to find all > > > users who currently have a home directory and then select all of those users > > > and change the location of their home directory (we got a new box for home > > > directories). However it seems when I use the %USERNAME% it does not > > > enumerate the variable…it just sets each users profile path to > > > \\server\users\username (instead of replacing %username% with their actual > > > username). > > > > > > > > > > > > Wondering if anyone else has used it and possibly ran into this issue, or > > > has had good luck with some other scripts/tools. > > > > > > > > > > > > NOTE: I decided to use admodify with the LDAP filter because I don't want > > > to change the path for EVERY user, because some do not have home > > > directories, and those who do not have them I would like to remain that way. > > > > > > > > > > > > Thanks > > > > > > /Ehren > > > > > -- > Troy D Murray > Blog: http://troymurray.blogspot.com/ > AIM: troymurray72 > Yahoo!: [log in to unmask] > MSN: [log in to unmask] > Google Talk: [log in to unmask] >