CODEWITHSUNDEEP
powershellmoduleactive-directory
user1564894616487456
user1564894616487456

Reputation: 25

POWERSHELL - Module Active Directory command New-AdGroup Problem with Spaces in value OU="Servers Of Files"

I would need your help with the use of New-AdGroup command.

The goal of my script is to verify if an Active Directory group exists and if it doesn't exist the script create the group and add the member of the group in a specific OU.

But my problem is when I use the script with a combination of OU and one of them contains some spaces in its name (ex : "OU=Servers of Files"), the script returns an error.

Example: I need to add the group in "OU=Fileserver1" which is a sub OU of "OU=Servers of Files" which is a sub OU of "OU=Groupes". When I call New-AdGroup with a path's value : "Ou=ServerFile1,OU=Servers of Files,OU=Groupes,DC=Contoso,DC=lan", I get the following error.

New-ADGroup : Objet de l’annuaire non trouvé At line:29 char:5 + New-ADGroup -Name "$DLGroupName" -Path "$Orga" -GroupCategory "Se ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (CN=G_GROUP1...ONTOSO,DC=lan:String) [New-ADGroup], ADIdentityNotFoundException + FullyQualifiedErrorId : Objet de l’annuaire non trouvé,Microsoft.ActiveDirectory.Management.Commands.NewADGroup

The problem is caused by "OU=Servers of Files" because I tried with an OU without spaces and it was working.

Please find a part of the script below, let me know how I can manage spaces under a path :

#Variable    
$CurrentDomain = Get-ADDomain | Select -Property DistinguishedName
$TargetOU = "OU=FileServer1,OU=Servers of Files,OU=Groupes" #
$OrganizationalUnitDN = $TargetOU+","+ $CurrentDomain.DistinguishedName
$Orga = $OrganizationalUnitDN
$DLGroupName = "DL_FileServer1_TEST"
$Description = "\\FileServer1\Share\Test"


    New-ADGroup -Name "$DLGroupName" -Path "$Orga" -GroupCategory "Security" -GroupScope "Global" -Description "$Description" -PassThru

Note : $Orga = Ou=ServerFile1,OU=Servers of Files,OU=Groupes,DC=Contoso,DC=lan

Upvotes: 0

Views: 1711

Answers (1)

FoxDeploy
FoxDeploy

Reputation: 13567

When we encounter weird bugs like this, a good first test is to manually run the command with no variables to find the root cause of the error. Doing this shows us that we don't need to escape spaces with a \ or \20 sequence and that route won't help us.

Because I can run your command with no errors when I manually expand the variables like so:

New-ADGroup -Name "DL_FileServer1_TEST" -Path "OU=Servers Of Files,DC=FoxDeploy,DC=local" `
   -GroupCategory "Security" -GroupScope "Global" -Description "Test" -PassThru


DistinguishedName : CN=DL_FileServer1_TEST1,OU=Servers Of Files,DC=FoxDeploy,DC=local
GroupCategory     : Security
GroupScope        : Global
Name              : DL_FileServer1_TEST1
ObjectClass       : group
ObjectGUID        : 5889f8ea-9d80-4609-ad47-92e50a574088
SamAccountName    : DL_FileServer1_TEST1
SID               : S-1-5-21-3818945699-900446794-3716848007-32100

Now that I know this works, I know I can then store the values in variables to make it cleaner to read, like this:

$params = @{
    Name = "DL_FileServer1_TEST1";
    Path = "OU=Servers Of Files,DC=FoxDeploy,DC=local";
    GroupCategory = "Security";
    GroupScope = "Global";
    Description = "My Test Group"
    PassThru = $true 
    }

New-ADGroup @params

If I had to guess, I bet that you need to run the entire script to populate all of the variables, and instead you are rerunning the last command over and over but one of the variables is $null.

If that doesn't work... If not that, then are we sure the container of Ou=ServerFile1 actually exists too?

Upvotes: 0

Related Questions