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
1. Install the Azure Arc agent (`azcmagent`) if not already present
66
-
2. Stamp site metadata as tags on the Arc machine resource
67
-
3. Connect the VM to Azure Arc with `--resource-name` set to `SiteCode`
86
+
2. Build the Arc resource name: `gw-hull-university-teaching-hospitals-nhs-trust-rwa-01`
87
+
3. Stamp site metadata as tags on the Arc machine resource
88
+
4. Connect the VM to Azure Arc with `--resource-name` set to the built resource name
68
89
69
90
Logs are written to `C:\ArcSetup\ArcSetup.log`.
70
91
71
-
**Verify**: In the Azure portal, navigate to `rg-manbgw-<env>-uks-arc-enabled-servers` → Azure Arc machines → `gw-RVJ-01`. Status should be **Connected**.
92
+
**Verify**: In the Azure portal, navigate to `rg-mbsgw-<env>-uks-arc-enabled-servers` → Azure Arc machines → `gw-hull-university-teaching-hospitals-nhs-trust-rwa-01`. Status should be **Connected**.
72
93
73
94
## Step 3 — Trigger Terraform to provision the Hybrid Connection
74
95
75
96
Run the ADO pipeline **Deploy Arc Infrastructure - \<env\>** manually. Terraform discovers the new Arc machine and creates:
76
97
77
-
-`hc-gw-RVJ-01` in the relay namespace (`relay-manbrs-<env>`)
98
+
-`hc-gw-hull-university-teaching-hospitals-nhs-trust-rwa-01` in the relay namespace (`relay-manbrs-<env>`)
78
99
-`listen` auth rule on that Hybrid Connection
79
100
80
-
**Verify**: In the Azure portal, navigate to `relay-manbrs-<env>` → Hybrid Connections → `hc-gw-RVJ-01` is present.
101
+
**Verify**: In the Azure portal, navigate to `relay-manbrs-<env>` → Hybrid Connections → `hc-gw-hull-university-teaching-hospitals-nhs-trust-rwa-01` is present.
81
102
82
103
## Step 4 — Deploy the gateway application
83
104
84
105
Run the ADO pipeline **Deploy Gateway - \<env\>** with:
|`-SiteCode`| No |*(hostname)*| Arc resource name and tag; format `gw-<ODSCode>-<instance>`|
121
-
|`-SiteName`| No |*(not set)*| Human-readable trust name; no spaces |
142
+
|`-SiteName`| No |*(hostname)*| Trust name, hyphen-separated, no spaces; used to build Arc resource name |
143
+
|`-ODSCode`| No |*(hostname)*| ODS code; used to build Arc resource name |
144
+
|`-Instance`| No |`01`| Zero-padded instance number; used to build Arc resource name |
122
145
|`-NHSRegion`| No |*(not set)*| NHS region code |
123
-
|`-PacsVendor`| No |*(not set)*| PACS system vendor |
124
146
|`-SiteType`| No |`static`|`static` or `mobile`|
125
147
|`-DeploymentRing`| No |`ring0`| Rollout ring (`ring0`–`ring4`) |
126
148
@@ -136,6 +158,26 @@ Check `C:\ArcSetup\ArcSetup.log` on the VM. Common causes:
136
158
-**SPN credentials wrong** — verify client ID and secret from Key Vault are current
137
159
-**VM already registered** — if the machine was previously connected under a different name, disconnect first: `azcmagent disconnect`
138
160
161
+
### Script execution blocked
162
+
163
+
If you see `running scripts is disabled on this system`, run this first in the same elevated session:
164
+
165
+
```powershell
166
+
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process
167
+
```
168
+
169
+
If the script was downloaded from the internet and is still blocked (error: `file is not digitally signed`), unblock the zone restriction first:
170
+
171
+
```powershell
172
+
Unblock-File -Path .\arc-setup.ps1
173
+
```
174
+
175
+
If the script is still blocked after `Unblock-File` (e.g. due to a stricter machine policy), use `Unrestricted` instead — still scoped to the current process only:
176
+
177
+
```powershell
178
+
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
179
+
```
180
+
139
181
### Arc machine shows as Disconnected after onboarding
0 commit comments