Skip to content

Commit b4e53cb

Browse files
Merge pull request #15692 from alkohli/thupg1
Changes from Trent Helm's PR 3277
2 parents 039ab93 + 40ca26f commit b4e53cb

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

azure-stack/hci/upgrade/validate-solution-upgrade-readiness.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Follow these steps to set up the Environment Checker on a server node of your Az
8282
1. Install the Environment Checker on the server. Run the following PowerShell command from the PSGallery:
8383

8484
```powershell
85-
Install-Module -Name AzStackHci.EnvironmentChecker -allowclobber
85+
Install-Module -Name AzStackHci.EnvironmentChecker -AllowClobber
8686
```
8787

8888
### Run the validation
@@ -98,7 +98,7 @@ Follow these steps to set up the Environment Checker on a server node of your Az
9898
1. To validate other servers in the cluster, run the following PowerShell command:
9999

100100
```powershell
101-
$PsSession=New-Pssession -computername "MyRemoteMachine"
101+
$PsSession=New-Pssession -ComputerName "MyRemoteMachine"
102102
Invoke-AzStackHciUpgradeValidation -PsSession $PsSession
103103
```
104104

@@ -159,7 +159,7 @@ $windowsFeature = @(
159159
)
160160
foreach ($feature in $windowsFeature)
161161
{
162-
install-windowsfeature -name $feature -IncludeAllSubFeature -IncludeManagementTools
162+
Install-WindowsFeature -Name $feature -IncludeAllSubFeature -IncludeManagementTools
163163
}
164164
165165
#Install requires optional Windows features
@@ -223,7 +223,7 @@ $windowsOptionalFeature = @(
223223
)
224224
foreach ($featureName in $windowsOptionalFeature)
225225
{
226-
enable-windowsoptionalfeature -featurename $featurename -all -online
226+
Enable-WindowsOptionalFeature -FeatureName $featurename -All -Online
227227
}
228228
```
229229

@@ -234,7 +234,7 @@ Ensure that all the cluster members are up and that the cluster is *Online*. Use
234234
To verify all members of the cluster are online, run the following PowerShell command:
235235

236236
```powershell
237-
Get-ClusterNode -cluster "mycluster"
237+
Get-ClusterNode -Cluster "mycluster"
238238
```
239239

240240
## Remediation 3: Suspend BitLocker
@@ -295,7 +295,7 @@ Follow these steps to confirm the storage pool configuration:
295295
1. To confirm the storage pool size and allocated size, run the following PowerShell command:
296296

297297
```powershell
298-
Get-storagepool -IsPrimordial $false
298+
Get-StoragePool -IsPrimordial $false
299299
```
300300

301301
<details>
@@ -310,7 +310,7 @@ Follow these steps to confirm the storage pool configuration:
310310
1. To list all volumes in the storage pool, run the following PowerShell command:
311311

312312
```powershell
313-
Get-storagepool -IsPrimordial $false|Get-VirtualDisk
313+
Get-StoragePool -IsPrimordial $false | Get-VirtualDisk
314314
```
315315

316316
<details>
@@ -341,10 +341,10 @@ Follow these steps to confirm the storage pool configuration:
341341
1. To convert the volume to thin provisioned, run the following PowerShell command:
342342

343343
```powershell
344-
Set-virtualdisk -FriendlyName TestVolume -ProvisioningType Thin
344+
Set-VirtualDisk -FriendlyName TestVolume -ProvisioningType Thin
345345
```
346346

347-
1. To convert the volume to thin provisioned, run the following PowerShell command. Make sure you adjust the CSV name to match your system:
347+
1. To finish the convertion, the volume must be restarted. To do this, run the following PowerShell command. Make sure you adjust the CSV name to match your system:
348348

349349
```powershell
350350
Get-ClusterSharedVolume -Name "Cluster Disk 1" | Stop-ClusterResource
@@ -362,7 +362,7 @@ Follow these steps to confirm the storage pool configuration:
362362

363363
| FriendlyName | ResiliencySettingName | FaultDomainRedundancy | OperationalStatus | HealthStatus | Size | FootprintOnPool | StorageEfficiency |
364364
|--------------|-----------------------|-----------------------|------------------|--------------|------|-----------------|------------------|
365-
|ClusterPerformanceHistory | Mirror | 1 | OK | Healthy | 21 GB | 43 GB | 48.84% |
365+
| ClusterPerformanceHistory | Mirror | 1 | OK | Healthy | 21 GB | 43 GB | 48.84% |
366366
| TestVolume | Mirror | 0 | OK | Healthy | 1 TB | 36.5 GB | 98.63% |
367367
| TestVolume2 | Mirror | 0 | OK | Healthy | 750 GB | 28.5 GB | 98.25% |
368368

@@ -404,7 +404,7 @@ Make sure that the cluster functional level and storage pool version are up to d
404404
$SubscriptionId = "Your Subscription ID"
405405
Login-AzAccount –UseDeviceAuthentication –tenantid $tenantid –subscriptionid $SubscriptionId
406406
Install-module az.connectedmachine
407-
New-AzConnectedMachineExtension -Name "AzureEdgeLifecycleManager" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.AzureStack.Orchestration" -ExtensionType "LcmController" -NoWait
407+
New-AzConnectedMachineExtension -Name "AzureEdgeLifecycleManager" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.AzureStack.Orchestration" -ExtensionType "LcmController" -NoWait
408408
```
409409

410410
## Remediation 10: Check the MOC install state

0 commit comments

Comments
 (0)