This assumes familiarity with Azure Portal, virtual networks and virtual machines. It is a lab only configuration using the default RDP access which should not be used for production machines.
For the virtual network that you are working on configure a custom DNS server with the IP address of the DC to be created below. This can be done after the DC is created if necessary.
This page is a very useful resource
https://www.systemcenterdudes.com/complete-sccm-installation-guide-and-configuration/
Create a DC
This is based on this page which is out of date.
Machine 1 DC and Hyper-V machine(installed later).
Name e.g. DSHV0
type D4sv3
OS Windows Server 2019 Datacenter
128Gb Standard SSD system
8Gb Standard SSD data
257Gb Standard SSD VMs disk.
Once the VMs are created configure the dnsname of the machine and use the connect blade to download the RDP connection file.
Initialise as GPT type and attach the disks in disk management as simple volumes, NTFS quick formatted. i.e. use defaults F: = 8Gb G:=256Gb
Add the Active Directory Domain Services role, install the feature and Promote this server to a domain controller - New Forest, enter a root domain name e.g. mylab.com
Enter the Directory Services Restore Mode password
On DNS options, ignore the warning and click next
Accept the NETBIOS default name and click next
Configure the Database, Log files, and SYSVOL folders to F: locations on the disk created earlier
On the Review Options page, click the View Script button. A PowerShell script snippet will be displayed in a Notepad window. This snippet includes the cmdlets needed to Install a new Active Directory forest via PowerShell with the options selected in the wizard. Save this snippet to your Documents folder for future reference as a file named PSSnippet-Install-ADDSForest.ps1 and close the Notepad window. Click Next
On the Prerequisites Check page, ignore the warnings displayed and click the Install button. The warnings displayed are due to the dynamic IP addressing used within Windows Azure Virtual Networks and do not apply to this cloud environment.
The Active Directory Domain Services configuration process will be begin for the new AD Forest.
When the Active Directory configuration process is complete, the server will automatically restart.
DC build complete
Note that during this process the local administrator user name and password are converted from local accounts to, well, the domain admin. For a test environment consider setting the password of the account to never expire. Password expiration of the domain admin account could be inconvenient.
Create a SCCM/SQL Server
This is based on this page which is out of date.
Machine 2 - The SCCM / SQL server
Name e.g. SCCMSQL0
Type D4s_v3
OS Windows Server 2019 Datacenter
128Gb Standard HDD system HDD are cheaper storage for test purposes.
128Gb Standard HDD data
Login as the local admin and attach the data disk.
Click WORKGROUP in the Local Server section of the server manager to join the domain e.g. mylab.com. If the mylab.com domain controller is not contactable check you have set the custom DNS server correctly and pointing to the DC for the virtual network.
Activate the required features for an SCCM server.
Add Roles and Features
Install the WSUS Server Role with defaults.
On the Select Features page, check the checkboxes for the following features and sub-features, leaving all other options at the default checkbox state:
- .NET Framework 3.5 with both HTTP Activation and Non-HTTP Activation selected.
- .NET Framework 4.7 with both HTTP Activation and TCP Activation selected.
- Background Intelligent Transfer Service ( BITS )
- Remote Differential Compression
-Telnet Client (not essential but a useful diagnostic tool to have ready)
Whenever prompted during the feature selection process above, click the Add Features button to add all features that are required for a select feature or sub-feature option.
Click the Next button to continue.
On the IIS Web Server Role Services page, check the checkboxes for the following options, leaving all other options at their default checkbox state:
- Windows Authentication, located under the IIS with Security section.
- ASP.NET 3.5, located under the Application Development section.
- IIS 6 WMI Compatibility, located under the Management Tools | IIS 6 Management Compatibility section.
Click the Next button and then click the Install button to begin the feature installation.
Now it's time to install the SCCM bits and bobs. This link may provide eval downloads.
https://www.microsoft.com/en-us/evalcenter/evaluate-system-center
In this procedure SCCM 1902 base version is being used and has been copied and extracted to the local F:
Login as the domain admin on the SCCM machine and run "F:\installfiles\SC_Configmgr_SCEP_1902\SMSSETUP\BIN\X64\extadsch.exe"
to extend the AD schema. After running this command, review the log output located in C:\extadsch.log to confirm that the schema extension operations were successfully completed.
Using the Active Directory Users and Computers tool from the domain controller virtual machine remote desktop console, setup the required Active Directory permissions and objects.
In the Active Directory Users and Computers tool, select View | Advanced Features from the menu bar. In the left navigation pane of the Active Directory Users and Computers tool, right-click on the System container and select Properties from the pop-up menu. On the Security tab, add the Active Directory computer account for the ConfigMgr site server to the Groups or user names list and assign Full Control permissions to it. Click OK when completed.
In the left navigation pane of the Active Directory Users and Computers tool, right-click on the Users container and select New | User from the pop-up menu. Create the following domain user accounts for SQL Server and ConfigMgr site system roles: Enter passwords as required and note them down.
- SQLService domain user account: uncheck User must change password at next logon optionand check Password never expires option.
- CMAdmin domain user account: uncheck User must change password at next logon option and check Password never expires option. Add this domain user account to the Domain Admins global group.
Go to your selected SQL Server installation media source. Below refers to 2012 but it is still similar in the 2019 version
Double-click the F:\setup.exe installation executable to launch the SQL Server 2012 Installation Center. In the SQL Server 2012/9 Installation Center window, click the Installation link located in the left navigation pane. In the SQL Server 2012/9 Installation Center window, click New SQL Server stand-alone installation or add features to an existing installation in the right content pane. This will launch the SQL Server 2012/9 Setup program.
Click through
Keep the free Eval version unless you have a product key you wish to use.
Note the firewall warning
Select the Database Engine Services, and use the web download link for reporting services (2019)
Modify the install locations to F:
Keep the default instance
Enter DomainName\SQLService account for the SQL Server Database Engine and enter the password.
Database Engine Configuration: Click Add Current User button
Use defaults and click through the nexts to start the install.
Install SQLServerReportingServices.exe downloaded from the link above.
Named Pipes
Launch SQL Server Configuration Manager
Expand SQL Server Network Configuration
Select protocols and Enable Named Pipes in the right window.
Next install the Windows 10 ADK downloaded from here.
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install
Use defaults.
Also obtain the WinPE Addon for the selected Win10 version and install it. This is checked by the SCCM install later.
Create this file D:\NO_SMS_ON_DRIVE.SMS to stop SCCM creating any files on the Azure VM temporary drive.
Finally time to run SCCM setup :)
Reboot and ensure login is the domain admin.
Run "F:\installfiles\SC_Configmgr_SCEP_1902\SMSSETUP\BIN\X64\setup.exe"
Install a Configuration Manager primary site - don't use the "typical" tick box it is not fun!
Select Eval unless you want to use a key.
Accept all the terms tick boxes.
Create a suitable folder for the setup downloads and specify it in the downloaded file path.
Select Languages
Select Install the primary site as a stand-alone site.
Use defaults for the database specification
Click Next on data and log file locations
Click Next on the SMS Provider
Client Computer Communications Settings - Configure the communication method on each site system role. Doing this enables HTTP and avoids the complexities of PKI certicates. As this is lab HTTP is acceptable. Production systems should have all reasonable security applied.
Site System Roles - Next
Prerequisite Check
Some warnings may appear with links to resolve. Check the warnings and carry out any other necessary actions as advised.
Begin Install
When the install wizard has completed, which may take about an hour, the top status message should be "Core setup has completed". The next button will not be available, only the Close button. Close.
