 |
 |
(Typing this whole email again as I left my OWA window open too long and timed out when I hit the send button....d'oh) Dennis: Thanks for your reply. The first option i definately investigated first. I used a custom AD search from the domain root for all users whos homefolder property began with \\oldserver and came up with the appropriate search results. From there if I selected any more than ONE user the properties option was disabled and therefore would kill that whole idea. I don't know what the deal is with that but its OK because I got it figured out today (more on that later) on DFS - My original issue was not getting the actual files to the new location but a good discussion on DFS nonetheless as it is mighty powerful. We use DFS for many things in our environment but not for the user home drive shares as the server that they are on is not upgraded to R2 and therefore uses the older FRS instead of DFRS (difference between day and night[mare]). I may implement this eventually since the server the user shares will be on now is R2 upgraded. [Takes a small break to watch Brad Paisley's music video called "Online" on his website, if you haven't seen it check it out www.bradpaisley.com] I spent most of the day today digging around Google and other various technical resources trying to figure out this issue with ADMODIFY and found the solution finally, which was not very intuitive. In admodify apparently the ole % notation used for most other things to script ad doesn't do squat. You have to use %'variable'% (percent singlequote, instead of just percent). Not only that but instead of using %'username'% you need to use %'sAMAccountName'% for it to auto insert the username of the person. So if anyone plans on doing anything like this you may want to take a note. ADMODIFY seems to be an incredibly powerful tool once you figure out the quirks and add in some LDAP filtering. Highly reccomend. Ehren J. Benson, MCSE Windows Systems Administrator Department of Physics and Astronomy Michigan State University 1209 A Biomed Phys Sci [log in to unmask] <mailto:[log in to unmask]> 517-355-9200 x2569 ________________________________ From: [log in to unmask] on behalf of Dennis Kelly Sent: Thu 8/2/2007 5:11 PM To: Ehren Benson Cc: [log in to unmask] Subject: Re: [MSUNAG] Anyone use ADMODIFY.NET? 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