You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/get-started/azure-template.md
+18-8Lines changed: 18 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,8 +30,8 @@ For more information, see [Configuration Manager on Azure](../understand/configu
30
30
## Prerequisites
31
31
32
32
This process requires an Azure subscription in which you can create the following objects:
33
-
- Two Standard_B2s virtual machines for domain controller, management point, and distribution point.
34
-
- One Standard_B2ms virtual machine for the primary site server and the SQL Server database server.
33
+
- Two Standard_B2s virtual machines for domain controller, management point, and distribution point. Choice available to choose client count(0-3) as a parameter.
34
+
- One Standard_B2ms virtual machine for the primary site server and the SQL Server database server and one other Standard_B2ms virtual machine for Central Administration Site if choosing to create hierarchy bench.
35
35
- Standard_LRS storage account
36
36
37
37
> [!Tip]
@@ -62,6 +62,8 @@ This process requires an Azure subscription in which you can create the followin
62
62
-**Admin Username**: The name of a user on the VMs with administrative rights. You use this user to sign in to the VMs.
63
63
64
64
-**Admin Password**: The password must meet the Azure complexity requirements. For more information, see [adminPassword](/rest/api/compute/virtualmachines/createorupdate#osprofile).
65
+
66
+
-**Configuration**: User can choose "Standalone" or "Hierarchy". This setting is available for Current Branch template only.
65
67
66
68
> [!Important]
67
69
> The following settings are required by Azure. Use the default values. Don't change these values.
@@ -72,22 +74,30 @@ This process requires an Azure subscription in which you can create the followin
72
74
>
73
75
> -**Location**: The location for all resources
74
76
77
+
> [!NOTE]
78
+
79
+
> If the azure template was edited before being deployed then the _artifactsLocation value needs to be changed. For Tech Preview template the value is “https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/sccm/sccm-technicalpreview/azuredeploy.json”.
80
+
For Current Branch template value is “https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/sccm/sccm-currentbranch/azuredeploy.json”.
81
+
75
82
4. Read the terms and conditions. If you agree, select **I agree to the terms and conditions stated above**. Then select **Purchase** to continue.
76
83
77
84
Azure validates the settings, and then begins the deployment. Check the status of the deployment in the Azure portal.
78
85
79
86
> [!NOTE]
80
87
> The process can take 2-4 hours. Even when the Azure portal shows successful deployment, configuration scripts continue to run. Don't restart the VMs during the process.
81
88
82
-
To see the status of the configuration scripts, connect to the `<prefix>PS1` server, and view the following file: `%windir%\TEMP\ProvisionScript\PS1.json`. If it shows all steps as complete, the process is done.
89
+
To see the status of the configuration scripts, connect to the `<prefix>PS01` server, and view the following file: `%windir%\TEMP\ProvisionScript\PS01.json`. If it shows all steps as complete, the process is done.
90
+
91
+
[!NOTE]
92
+
> When using the Current Branch Template, the json file used is CAS.json at same location in `<prefix>CS01` server.
83
93
84
94
To connect to the VMs, first get from the Azure portal the public IP addresses for each VM. When you connect to the VM, the domain name is `contoso.com`. Use the credentials that you specified in the deployment template. For more information, see [How to connect and log on to an Azure virtual machine running Windows](/azure/virtual-machines/windows/connect-logon).
85
95
86
96
87
97
88
98
## Azure VM info
89
99
90
-
All Three VMs have the following specifications:
100
+
All Three VMs (VM count depends upon which configuration/clients count was chosen) have the following specifications:
91
101
- 150 GB of disk space
92
102
- Both a public and private IP address. The public IPs are in a network security group that only allows remote desktop connections on TCP port 3389.
93
103
@@ -98,7 +108,7 @@ The prefix that you specified in the deployment template is the VM name prefix.
98
108
99
109
- Active Directory domain controller
100
110
- Standard_B2s, which has two processors and 4 GB of memory
101
-
- Windows Server 2019 Datacenter edition
111
+
- Windows Server 2022 Datacenter edition
102
112
103
113
#### Windows features and roles
104
114
- Active Directory Domain Services (ADDS)
@@ -109,7 +119,7 @@ The prefix that you specified in the deployment template is the VM name prefix.
109
119
### `<prefix>PS01`
110
120
111
121
- Standard_B2ms, which has two processors and 8 GB of memory
112
-
- Windows Server 2016 Datacenter edition
122
+
- Windows Server 2019 Datacenter edition
113
123
- SQL Server
114
124
- Windows 10 ADK with Windows PE
115
125
- Configuration Manager primary site
@@ -133,8 +143,8 @@ The prefix that you specified in the deployment template is the VM name prefix.
133
143
- Internet Information Service (IIS)
134
144
- Background intelligent transfer service (BITS)
135
145
136
-
### `<prefix>CL01`
146
+
### `<prefix>CL01`
137
147
138
148
- Only for Configuration Manager current branch evaluation template
0 commit comments