• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Copy a user's setting to another user in Active Directory

LuckyTaxi

Diamond Member
Just finished entering over 400 accounts into AD. Then I realized these users need to have
a drive mapped to drive Z to a specific folder on the PDC.

So, I created a login script to map drive Z to \\school-house\students\%username%

Well, it works and everything, but now I have to put the file name (login.bat) into each
of their profiles! Is there an easier way to do this? I just realized I couldve created the
users from a template by filling in everything that was needed. I hate to go back into all
400 accounts and add that one line
 
Use group policy to assign the logon script.
If every user in your AD needs the mapped drive, you could apply the GP at the domain level, otherwise, apply it to the OU's you need it on.

The setting is...
User configuration> Windows Settings> Scripts (logon/logoff).
Right click the logon object in the right hand pane, select properties, and then point it to your script.
Make sure the script is in the default folder it brings up when you hit the Browse button (i.e the Script should be on the Domain controller)


If you do it this way, you won't have to modify any accounts at all.
 
Thats where I'm a little lost. I need to assign this logon script to the 400 accounts, but not to the other 50. The 400 accounts are students while the rest are administrative and the IT ppl.
 
Put the 50 exclusions into a security group and in Group Policy deny the group permissions to read and apply the policy.
 
^ That will work well.

You also may want to organize your users into different OU's based on thier needs/role. IT folk shouldnt be in the same OU as users.
That said, perhaps there are some other constraints that forced you to design your OU's the way they are, in that case go with the security group!
 
Back
Top