Changing AD

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Andrew if you could bear with us, this is close to something I need to set up at work only with computer accounts. I'm looking at a couple of ways of doing it, first method you export the list of users in the OU into a text file then itterate throught the text file configuring each user. Second method (preferred) enumerates all the accounts in the OU and then works its way through them configuring each one. When I've come up with something I'll come back to you.

 

Sounds interesting guys, I'll be watching closley.

SimonV

 

Hi Andrew, nowhere near as complicated as I thought it was going to be

[code:1:45aad64594]
'This line attaches to the OU
Set colAccounts = GetObject("LDAP://ou=YEAR1,dc=DOM,dc=CO,dc=UK")

'This Line gets the users in the OU
colAccounts.Filter = Array("user")

'This For Next Loop itterates through each user
For Each objUser In colAccounts
'These lines set the profilepath for each user and saves
objUser.Put "profilePath", "\\SERVER\Profiles\MandatoryProfile"
objUser.SetInfo
Next
[/code:1:45aad64594]

Simple as that, Configure the LDAP info with your domain / OU details so that if you want to do the users in the FORM OU below YEAR1 it would read something like this

ou=FORM,ou=YEAR1,dc=DOM,dc=CO,dc=UK

Make sure you enter the correct path to the Profile for your network. Copy the script into a text file, save it as a vbs file then run it on a computer with access to AD and an account with the right priviliges.

 

No probs Andrew, give us a shout if it gives you any gyp.

 

I've adapted it so that it can shut down every machine on site, now if only *evil* worked in the forum

 

@Phil, Is this not the same as the scriprt you knocked up for me except i left the profile path blank? :?:

 

It's similar to the method I gave you for changing a single users derek, except the method for making the profile blank is different.

to write a new profilepath to the profile you use
[code:1:fe8a4818d6]
objUser.Put "profilePath", "\\SERVER\Profiles\MandatoryProfile"
[/code:1:fe8a4818d6]

to empty the profile path you use
[code:1:fe8a4818d6]
objUser.PutEx 1, "profilePath",0
[/code:1:fe8a4818d6]

The main difference between the scripts which search for users is that you use ADO to search the entire domain for users in your script including ou's and sub-ou's. Andrew's script will only search a single OU.