Active Directory Configuration – JBSDC

-> Connect to Azure Virtual Machine JBSDC and open a PowerShell command window.

-> Execute below command for installing Active Directory Domain Services,

Install-WindowsFeature AD-Domain-Services -IncludeManagementTools

-> Execute below command to configure an appropriate domain,

Install-ADDSForest -DomainName JBSWIKI.com

-> Virtual Server JBSDC will restart after the configuration. Login to Virtual Server JBSDC using your domain account, in my case I will use account jbswikijbswiki.

Add Database Server JBSAG1 to Domain JBSWIKI.COM

-> Login to Database server JBSAG1 and execute below powershell script to add Database Server JBSAG1 to domain JBSWIKI.COM. Please modify $domain and $DNSIP with appropriate values before executing,

$domain = "JBSWIKI.COM"
$DNSIP = "172.20.1.4"
$IAlias = (Get-NetConnectionProfile -ErrorAction Stop).InterfaceAlias
Set-DnsClientServerAddress -InterfaceAlias $IAlias -ServerAddresses $DNSIP -ErrorAction Stop
Add-Computer -DomainName $domain -ErrorAction Stop

-> After you execute above powershell script, you will need to key in the admin account that has permission to access DNS Server JBSDC,

-> Restart Database Server JBSAG1 as requested,

Add Database Server JBSAG2 to Domain JBSWIKI.COM

-> Follow same procedure as detailed above to add Database Server JBSAG2 to domain JBSWIKI.COM.

Add Database Server JBSAG3 to Domain JBSWIKI.COM

-> Follow same procedure as detailed above to add Database Server JBSAG3 to domain JBSWIKI.COM.

Connecting to SQL Server Instances JBSAG1 and JBSAG2 using SQL Server Management Studio

-> When connecting to SQL Server JBSAG1\JBSAG2\JBSAG3 from SSMS, we will get below error,
_{^{TITLE: Connect to Server
Cannot connect to JBSAG1.
ADDITIONAL INFORMATION:}}
Login failed for user ‘JBSWIKIjbswiki’. (Microsoft SQL Server, Error: 18456)
^{For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-18456-database-engine-error
BUTTONS:}

-> I logged into Database Server JBSAG1\JBSAG2\JBSAG3 using Server\Login (eg: JBSAG1\jbswiki) or use a Run As on SSMS with account Server\Login (eg: JBSAG1\jbswiki) and then add the required logins to SQL Server JBSAG1\JBSAG2\JBSAG3.

More articles on this Series,

-> Always On Availability Group Configuration on Azure IaaS Virtual Machine utilizing Multi Subnet
-> Always On Availability Group Environment on Azure IaaS Virtual Machine Introduction – Part1
-> Configure appropriate Virtual Network and Subnet for Azure IaaS Virtual Machine – Part2
-> Deploy required Azure IaaS Virtual Machine – Part3
-> Configure Azure Load Balancer – Part5
-> Configure Always On Availability Group with Listener – Part6

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

Domain Controller – JBSDC

-> Below Azure Virtual Machine will be provisioned to be used as a Domain Controller. I have allowed In-Bound port 3389 for RDP as this is a Lab setup.

-> Disks Tab,

-> Networking Tab. Make sure a Standard SKU is selected for Public IP Address.

-> Tabs “Management”, “Advanced” and “Tags” are default in my case. Click “Create”,

Database Server – JBSAG1

-> Search for “SQL Virtual Machine” on Azure portal. Please note that I am selecting a “Free SQL Server License: SQL 2019 Developer Edition” as this is a lab. In reality you will need to utilize an enterprise edition.

-> Selecting an Image as mentioned here will have additional SQL Server components such as Analysis and Integration Services. You can either disableuninstall them if you don’t use or You can provision an Azure Virtual machine and then Install SQL Server on it which will allow you to select only required components.

-> Disks Tab,

-> Networking Tab. Make sure a Standard SKU is selected for Public IP Address.

->Tabs “Management” and “Advanced” are default in my case.

-> Tab “SQL Server Settings”. Click on “Change Configuration” under storage,

-> Please select appropriate settings to suit your performance requirement. In my case as this is a lab, I am utilizing a single disk for both data and log file and also selecting a smaller 64GB disk,

->Tab “Tags” is default in my case.

Database Server – JBSAG2

-> Follow the same method and provision an Azure virtual machine named JBSAG2 same as JBSAG1.

Database Server – JBSAG3

-> Search for “SQL Virtual Machine” on Azure portal. Please note that I am selecting a “Free SQL Server License: SQL 2019 Developer Edition” as this is a lab. In reality you will need to utilize an enterprise edition.

-> Selecting an Image as mentioned here will have additional SQL Server components such as Analysis and Integration Services. You can either disable\uninstall them if you don’t use or You can provision an Azure Virtual machine and then Install SQL Server on it which will allow you to select only required components.

-> Disks Tab,

-> Networking Tab. Make sure a Standard SKU is selected for Public IP Address.

->Tabs “Management” and “Advanced” are default in my case.

-> Tab “SQL Server Settings”. Click on “Change Configuration” under storage,

-> Please select appropriate settings to suit your performance requirement. In my case as this is a lab, I am utilizing a single disk for both data and log file and also selecting a smaller 64GB disk,

->Tab “Tags” is default in my case.

More articles on this Series,

-> Always On Availability Group Configuration on Azure IaaS Virtual Machine utilizing Multi Subnet
-> Always On Availability Group Environment on Azure IaaS Virtual Machine Introduction – Part1
-> Configure appropriate Virtual Network and Subnet for Azure IaaS Virtual Machine – Part2
-> Configure Domain Controller and Windows Cluster on appropriate Azure IaaS Virtual Machine – Part4
-> Configure Azure Load Balancer – Part5
-> Configure Always On Availability Group with Listener – Part6

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

Environment

-> JBSAG1 and JBSAG2 are Azure IaaS virtual machines provisioned on East US region. Azure IaaS virtual machine JBSAG3 is provisioned on West US region.

-> Azure virtual machine JBSAG1, JBSAG2 and JBSAG3 are part of Windows cluster JBSWikiClust without shared storage. Azure virtual machine JBSAG1 and JBSAG2 will be configured using Synchronous commit with automatic failover. JBSAG3 will be configured using Asynchronous commit with Manual failover.

-> Resources related to Virtual Machine JBSAG1 and JBSAG2 will be hosted on a Resource Group called JBSWiki and resources related to virtual machine JBSAG3 will be hosted on resource group JBSWiki_WestUS.

-> This environment will have a database called JBSWiki added to availability group JBSAG with Listener JBSAPP.

-> Database Servers JBSAG1 and JBSAG2 will be configured using common Virtual network and subnet configuration. Database Server JBSAG3 will have a separate Virtual network and subnet configuration.

More articles on this Series,

-> Always On Availability Group Configuration on Azure IaaS Virtual Machine utilizing Multi Subnet
-> Configure appropriate Virtual Network and Subnet for Azure IaaS Virtual Machine – Part2
-> Deploy required Azure IaaS Virtual Machine – Part3
-> Configure Domain Controller and Windows Cluster on appropriate Azure IaaS Virtual Machine – Part4
-> Configure Azure Load Balancer – Part5
-> Configure Always On Availability Group with Listener – Part6

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.