Automating the process of configuring an Azure VM as a standalone domain controller

%3CLINGO-SUB%20id%3D%22lingo-sub-2139353%22%20slang%3D%22en-US%22%3EAutomating%20the%20process%20of%20configuring%20an%20Azure%20VM%20as%20a%20standalone%20domain%20controller%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2139353%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20deployed%20an%20Azure%20virtual%20machine%20with%20Windows%20Server%202019%20Datacenter%20and%20our%20apps%20installed%20on%20it%20to%20provide%20a%20cloud%20solution%20of%20our%20apps%20to%20clients.%20The%20virtual%20server%20is%20configured%20as%20a%20standalone%20(or%20isolated)%20domain%20controller%20(DC)%20as%20well%20and%20domain%20users%20have%20been%20created%20as%20well.%20All%20the%20related%20configurations%20have%20been%20done.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThis%20is%20working%20well%20for%20our%20the%20client.%20We%20are%20now%20intending%20to%20publish%20this%20solution%20to%20Azure%20Common%20Marketplace%20-%20that%20is%2C%20publish%20Azure%20VM%20image.%20The%20challenging%20part%20is%20to%20automate%20the%20process%20of%20creating%20and%20configuring%20a%20standalone%20DC%2C%20because%20DC%20names%20will%20be%20variable.%20The%20following%20are%20the%20objectives%3A%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E1.%20To%20create%20some%20sort%20of%20scripts%20that%20let%20customers%20input%20the%20name%20of%20a%20standalone%20DC%20and%20therefore%2C%20add%20and%20configure%20DC%20roles%20and%20its%20features%20automatically.%3CBR%20%2F%3E2.%20Publish%20the%20scrips%20(mentioned%20in%201)%20along%20with%20our%20Azure%20VM%20image%20with%20our%20apps%20pre-installed%20on%20it.%3CBR%20%2F%3E3.%20A%20customer%20would%20be%20able%20to%20run%20the%20scripts%20after%20getting%20our%20image%20and%20scripts%20from%20Azure%20commercial%20marketplace.%3CBR%20%2F%3E4.%20A%20customer%20can%20then%20add%20domain%20users%20or%20contact%20us%20to%20use%20our%20support%20service%20in%20creating%20domain%20users%20and%20adding%20them%20to%20%22Remote%20Desktop%20Users%22%20group%20including%20all%20the%20required%20configurations.%3C%2FP%3E%3CP%3EI%20hope%2C%20the%20above%20makes%20sense%3F%3C%2FP%3E%3CP%3EI%20am%20aware%20that%20the%20alternative%20is%20to%20have%20an%20Azure%20VM%20deployed%20as%20Azure%20Active%20Directory%20(AAD)%20enabled%2C%20create%20a%20generalised%20image%20using%20sysprep%20and%20publish%20it%20to%20Azure%20commercial%20marketplace.%20With%20this%20approach%2C%20customers%20can%20sign%20in%20to%20Azure%20VM%20with%20their%20Azure%20AD%20accounts%2C%20if%20I%20have%20got%20it%20right.%3C%2FP%3E%3CP%3EThe%20reason%2C%20why%20we%20are%20pursuing%20for%20the%20method%20of%20publishing%20VM%20image%20used%20as%20a%20standalone%20DC%20because%2C%20we%20have%20already%20deployed%20a%20VM%20for%20a%20client%2C%20which%20is%20live%20and%20working%20well%20for%20the%20client%20and%20we%20are%20familiar%20with%20this%20method%20now.%3C%2FP%3E%3CP%3ECould%20someone%20please%20refer%20to%20documentation%20and%2For%20advise%20to%20help%20us%20in%20automating%20the%20process%20of%20creating%20and%20configuring%20an%20Azure%20VM%20as%20a%20standalone%20DC%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EBest%20regards%2C%3C%2FP%3E%3CP%3EMisbah%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

We have deployed an Azure virtual machine with Windows Server 2019 Datacenter and our apps installed on it to provide a cloud solution of our apps to clients. The virtual server is configured as a standalone (or isolated) domain controller (DC) as well and domain users have been created as well. All the related configurations have been done.


This is working well for our the client. We are now intending to publish this solution to Azure Common Marketplace - that is, publish Azure VM image. The challenging part is to automate the process of creating and configuring a standalone DC, because DC names will be variable. The following are the objectives:


1. To create some sort of scripts that let customers input the name of a standalone DC and therefore, add and configure DC roles and its features automatically.
2. Publish the scrips (mentioned in 1) along with our Azure VM image with our apps pre-installed on it.
3. A customer would be able to run the scripts after getting our image and scripts from Azure commercial marketplace.
4. A customer can then add domain users or contact us to use our support service in creating domain users and adding them to "Remote Desktop Users" group including all the required configurations.

I hope, the above makes sense?

I am aware that the alternative is to have an Azure VM deployed as Azure Active Directory (AAD) enabled, create a generalised image using sysprep and publish it to Azure commercial marketplace. With this approach, customers can sign in to Azure VM with their Azure AD accounts, if I have got it right.

The reason, why we are pursuing for the method of publishing VM image used as a standalone DC because, we have already deployed a VM for a client, which is live and working well for the client and we are familiar with this method now.

Could someone please refer to documentation and/or advise to help us in automating the process of creating and configuring an Azure VM as a standalone DC?


Best regards,

Misbah

1 Reply