Forum Discussion
Requirement to have an on-prem AD
- Mar 25, 2019
HandA
on-prem AD is not required.
AD requirements:
Option 1: Domain controller that is synchronized with Azure Active Directory. The domain controller can be on-prem or in cloud. To synchronize with Azure Active Directory install Azure Active Directory Connect.
Option 2: Azure AD Domain Services domain in Azure (automatically synced with Azure Active Directory)
Thanks. I have this working now using Azure ADDS. Documentation seemed a bit unclear when I first looked at it
HandA Did you get it to work without need of on-premise AD or AD Connect?
- Alberto RodriguezMay 02, 2019Copper ContributorI keep getting the following deployment fail error:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"VMExtensionProvisioningError\",\r\n \"message\": \"VM has reported a failure when processing extension 'joindomain'. Error message: \\\"Exception(s) occured while joining Domain 'mnetpr.com'\\\".\"\r\n }\r\n ]\r\n }\r\n}"}]}- Christian_MontoyaMay 02, 2019
Microsoft
Alberto Rodriguez : Do you have access to those VMs? If you can RDP into them, please look at C:\Packages and navigate down to the JsonADDomainExtension folder, you should be able to find a "status" file (or equivalent). If you open it up, it will typically give you the reason that it errored out. Unfortunately, I do not have too many details at the moment because the documentation on the extension is fairly light.
- Alberto RodriguezMay 03, 2019Copper Contributor
Christian_Montoya [{"version":"1","timestampUTC":"2019-05-02T15:37:19.805151Z","status":{"name":"ADDomainExtension","operation":"Join Domain/Workgroup","status":"error","code":1,"
formattedMessage":{"lang":"en-US","message":"Exception(s) occured while joining Domain 'azure.mnetpr.com'"},"substatus":[{"name":"JoinDomainException for Option 3 meaning 'User Specified'","status":"error","code":1,"formattedMessage":{"lang":"en-US","message":"ERROR - Failed to join domain='azure.mnetpr.com', ou='', user='arodriguez@azure.mnetpr.com', option='NetSetupJoinDomain, NetSetupAcctCreate' (#3 meaning 'User Specified'). Error code 1326"}},{"name":"JoinDomainException for Option 1 meaning 'User Specified without NetSetupAcctCreate'","status":"error","code":1,"formattedMessage":{"lang":"en-US","message":"ERROR - Failed to join domain='azure.mnetpr.com', ou='', user='arodriguez@azure.mnetpr.com', option='NetSetupJoinDomain'
(#1 meaning 'User Specified without NetSetupAcctCreate'). Error code 1909"}}]}}]