Solarwinds bulk AD User creation

Hi

I am trying to use the Solarwinds AD tool to bulk create user accounts. We are moving from having generic year group logins to individual logins for all pupils, so I have quite a few to create.

So far I've successfully created test users, but I can't get the syntax right in the csv to create them in the required OU. The example given is:

When you leave the OrganizationalUnit field blank, it automatically creates the account in the Users OU at the top level in the domain, i.e. SCHOOL.LOCAL/Users. The format it populates to achieve this is: CN=Users,DC=SCHOOL,DC=LOCAL

I want to create the users in SCHOOL.LOCAL/schoolname/users/pupils/intake_*

Any ideas what the format should be for this program? (We don't have any Forest or Tree structure - it's a single server for the whole school for all functions including DC.) I'd rather not manually move them after creation as there is a reasonable number of accounts in there already for Sophos, Backup, Admin, Lightspeed etc and I'd be bound to make a mistake and miss one or move one that I don't want to....

Thanks

OU=intake_*,OU=pupils,OU=users,OU=schoolname,DC=SCHOOL,DC=LOCAL

Ben

OU=intake_*,OU=pupils,OU=users,OU=schoolname,DC=SCHOOL,DC=LOCAL

 

Ben

You sir, are a gentleman and a scholar 8)

Don't suppose you know how to make user a member of a specified security group by any chance? Haven't worked out which field on the solar winds application it should be, or the syntax. I have read about using powershell, so it could be fine retrospectively, but I'd rather not...

Only other thing stumping me at the minute is allowing simpler passwords, as per my other thread.

Thanks again.

I've no idea as I've never used it if you look at properties of a group you can see the ldap string for it.

Ben

Thanks Ben.

I've been reading more about it and there are quite a few users reporting issues - I think I was doing it correctly (matches what others have been told to do), but always inclined to suspect user error when something doesn't work the first time I try it!

Just installed the wisesoft bulk AD tool and have now added the users to the group required. Worked straight away without even reading the instructions! I think it's something I'll be using quite a lot - widely recommended on here

The ldap property in question from the user perspective is

memberof

from the group perspective it is

members

Turn on advanced view in ADUC and go to the attribute editor tab of an account.

You can find the full DN there for easy copy and paste.

I've never used the solar winds tool either, I use powershell.

I've not seen your other thread yet, but;

• create a new security group
  
• create a fine grained password policy
  
• add the accounts to that group and they get the new password policy.
  

I create a user group for each year. I then add the lower year groups to the password policy group. Keeps it neater that way, when the move up I just remove the year group and add the new Y0 group.

Hope this helps

Thanks @ADMaster.

You've confirmed that I had identified the correct property - it's possible I picked the wrong thing to map it to in Solarwinds, but it has proved so easy to use the Wisesoft updater that it's not worth spending any more time on.

It took me a few attempts to get the Solarwinds product configured the way I wanted it, but it's now the work of minutes to create hundreds of users in the desired security groups - including setting passwords. And still retaining my ignorance of Powershell

One gotcha on the Solarwinds product that almost got me at the final hurdle, after you import all of the details and get a preview of the accounts to be created, you have to click "select all" and scroll to the bottom of the list - otherwise it only seems to pick up the first few records. Didn't occur in testing as I used small samples...

I still need to sort the password policy - current workaround is Solarwinds product allows you to set variables: require password change on next log on, never expire and prevent user changing password. I have removed the complexity requirement temporarily - ssshhhh, don't tell the staff!