Add-NTFSAccess : Cannot bind parameter

[RobRGitHub]

I have a PS script that creates new AD groups then adds those new groups with Add-NTFSAccess. Most of the time the addition fails with this error:

Add-NTFSAccess : Cannot bind parameter 'Account'. Cannot convert value "" to type "Security2.IdentityReference2". Error: "The trust relationship between the primary domain and the trusted domain failed.

If I wait a bit I can issue the same Add-NTFSAccess and it works without issues. I tried adding a sleep delay which seems to help sometimes but still get the error. Is there a check I should be doing before hand to verify something has sync'd in AD before using this command?

[Sup3rlativ3]

What does your code look like? I've tested this and it seems to work for me.

New-ADGroup -Name $ACLFullName -SamAccountName $ACLFullName -GroupCategory Security -GroupScope DomainLocal -Path $OUPath
Add-NTFSAccess "$SharePath" -Account "internal.domain.com\$ACLFullName" -AccessRights ReadAndExecute, Synchronize -AccessType Allow -AppliesTo FilesOnly

[RobRGitHub]

It does work for me also in my code but often I get this error, if I run the same Add-NTFSAccess command again after I get the error it usually works. It seems to not have an issue adding existing AD groups as they always work but it has this problem when I create new AD groups in my script then try to add them to a folder with the command. I'm trying to identify what is causing this response so that I can try to test for it with powershell in my script first before issuing the Add-NTFSAccess command for the new AD groups I'm creating.

I tried adding a 20 second pause after creating the AD Groups which helped to reduce the frequency but not eliminate it. My command looks just like yours above except I also tried adding the -server to the New-ADGroup command to make sure I was using the local DC as opposed to some other global one in case that caused some delay.

I'm not implying that there is an issue with the commands, there isn't from what I can tell, just trying to find what is causing this response so that I can test for it first.

[raandree]

@RobRGitHub, sorry, I didn't take care about this project for quite a while. Do you still have this issue or are interested to solve it? Then I would like to get your PowerShell code to reproduce the issue.

[RobRGitHub]

@RobRGitHub, sorry, I didn't take care about this project for quite a while. Do you still have this issue or are interested to solve it? Then I would like to get your PowerShell code to reproduce the issue.

Hello...

No I'm good, I made a change to my PowerShell script that when it fails to add the group to wait 10 seconds and try again until it succeeds. I still don't know why I get this response at times...

"The trust relationship between the primary domain and the trusted domain failed."

...but waiting those 10 seconds in between attempts seems to do the trick and works in 0-30 seconds most of the time.

Thanks for your reply!!
Rob!

[dmckee-ebsco]

@RobRGitHub - I know this was a few years ago, but for anyone else landing here:

"The trust relationship between the primary domain and the trusted domain failed." - This is typically seen when a computer is joined to a domain that already contains a computer of the same name. I'll typically see this when a servers server is cloned (new server from image) if I don't change the computer name with Rename-Computer or in some other way. Cheers!

ps- possibly related to this error is a computer that is not joined to a domain, but you're trying to Add-NTFSAccess using an AD user name. This was my issue, I finally discovered.