azure-docs
azure-docs copied to clipboard
MicrosoftDocs
issues on step Add-ADDCloudSyncADDomain, with powershell
having performed all the steps, using admin user I have this error, last step of the domain when provisioning the agent via powershell
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: b137e370-23ff-b91f-1d27-91d443eb6622
- Version Independent ID: 6c827baa-592b-3c2a-bea6-dceaf6d394ba
- Content: Install the Azure AD Connect cloud provisioning agent using a command-line interface (CLI) and PowerShell - Microsoft Entra
- Content Source: articles/active-directory/cloud-sync/how-to-install-pshell.md
- Service: active-directory
- Sub-service: hybrid
- GitHub Login: @billmath
- Microsoft Alias: billmath
@hiran-filho It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!
@RohitMungi-MSFT,
sorry
in issues, i'm use this doc, see that the problem appears almost at the end when it is to add the domain, in step 13
https://docs.microsoft.com/en-us/azure/active-directory/cloud-sync/how-to-install-pshell
before doing the script above, I performed the prerequisites below, because I was having some problems, but unfortunately the one I'm facing I didn't find how to solve it
https://docs.microsoft.com/en-us/azure/active-directory/cloud-sync/reference-powershell
on another server another error is appearing at the same point, where it informs that it was not possible to find the domino
@hiran-filho
I reviewed the issue and came up with solution that at place of -DomainName hmf.local . You can try with -DomainName "hmf.local". If you still getting the same issue. Please feel free to reach out to us.
@YashikaTyagi-MSFT
I tried that, but I got the same error.
I tried "hmf.local" and I tried 'hmf.local'
This process is a laboratory I'm doing, I used a 2016 base server, and using the same steps on a base 2019 server I got another error about the kds key and even using the command Add-KdsRootKey -EffectiveTime ((get-date).addhours(-10))
I promise to send here as soon as possible the steps I'm using and the errors on each server.
my idea is to create an automation to upload a VM with windows server installing AD and already interconnecting with Azure via cloud sync
@hiran-filho We are working on the issue and will get back to you. Thanks for your quick response.
Thank you for submitting this issue. Unfortunately, due to high volumes I was unable to respond to this in a timely manner. At this point, I am going to close this due to it's age and the possibility that it may have been addressed. If this is still a problem, please consider submitting a new issue. Thank you.
#please-close
