bdel

vor 1 Minute schrieb NorbertFe:

Excellent. Good luck

Thanks Norbert

Sutpid Me.
used wrong parameter -PrincipalAllowedToDelegate instead of RetrievePassword.

Going to next steps... Yessss, reached next window in the wizzzzard !

Thanks for all !

Of course not, as I'm quite some NewBy these things....

After some other PowerShell Commands, I reached the Install-ADServiceAccount

and stupid Install-ADServiceAccount reply with an access denied, even after restarting server.

I created the account with the "PrincipalAllowToRetrivePassword" with the ComputerName$ of the server on which the service is used

Next Try: create, as mentioned, a managed service account manually (new-adServiceAccount), who's name not as long as the default one. The service has been created but does not launch because of wrong password. May be wait for the password to be generated.

Next try on a Server who is just Domain Member (not PDC nor BDC).
Just try to create the service (sc create) with binpath cmd.exe and obj with full username "<MyDomain>\ADSyncMSA_3139f$"

failed (206) : Same error "File Name or extention too long"

Hello,

Same trouble on Windows 2012 PDC.

The problems comes when creating the Service "ADSync" with the stupid username.

When using "fast parameters" the security context used to run the ADSync Service is mentioned in the log file : "<Domain Name>\ADSyncMSA_3139f$" and also the binary path.
I tried to create the service manualy (sc create ADSync BinPath= "blablabla.exe") , at first without the username , but it has been deleted when running Azure AD Connect, and a second time with the username : sc create ADSync BinPath= "blabla.exe" obj= "MyDomain\ADSyncMSA_3139f$" and i get the error "File Name or extention too long".
Next attempt : create the service without "obj" parameter (UserName) and then modify the service through the regular interface. Same error.
The problem comes with the stupid UserName used for service who seems to be too long.
May be, because of PDC, the <DomainName> prefixing the UserName is not mandatory and should be not used when using this Agent on the PDC.