User organisation details
The organization tab on the user properties can hold a number of items – job title, department, company, manager & direct reports
The first four we can set directly. The direct reports attribute is a backlink meaning it is filled with the distinguished names of the users who have a particular user set as their manager.
The properties we can set are managed like this
if (-not (Get-Module ActiveDirectory)){
Import-Module ActiveDirectory
}
$ou = "OU=England,DC=Manticore,DC=org"
$dept = "Secret Squirrel stuff"
$comp = "Hush Hush Co Ltd"
$manager = "CN=HORNBLOWER Horatio,$ou"
"`nMicrosoft"
$name = "UserA"
$title = "VP for stuff"
Get-ADUser -Identity $name |
Set-ADUser -Title $title -Department $dept -Company $comp -Manager $manager
"`nAD provider"
$name = "UserB"
$title = "VP for something or other"
$dn = "cn=$name,$ou"
Set-ItemProperty -Path AD:\$dn -Name title -Value $title -Force
Set-ItemProperty -Path AD:\$dn -Name department -Value $dept -Force
Set-ItemProperty -Path AD:\$dn -Name company -Value $comp -Force
Set-ItemProperty -Path AD:\$dn -Name manager -Value $manager -Force
"`nQuest"
$name = "UserC"
$title = "VP for things"
Get-QADUser -Identity $name |
Set-QADUser -Title $title -Department $dept -Company $comp -Manager $manager
"`nScript"
$name = "UserD"
$title = "VP for other things"
$dn = "cn=$name,$ou"
$user = [adsi]"LDAP://$dn"
$user.title = $title
$user.department = $dept
$user.company = $comp
$user.manager = $manager
$user.SetInfo()
The cmdlets have parameters for each attribute while the provider and script have to work a bit harder