大网数据广告活动
Windows Server 管理

Deploy Hyperconverged Infrastructure with Windows Admin Center

· 52CE 我爱测

Learn how to deploy a hyperconverged infrastructure by using Windows Admin Center.

You can use Windows Admin Center version 1910 or later to deploy a hyperconverged infrastructure by using two or more suitable Windows servers. This feature takes the form of a multistage workflow that guides you through installing features, configuring networking, creating the cluster, and deploying Storage Spaces Direct and/or software-defined networking (SDN).

Important: Windows Admin Center doesn't support Azure Stack HCI OS deployment. To learn about deploying Azure Local infrastructure, see the Azure Local documentation.

Undo and start over

Use the following Windows PowerShell cmdlets to undo changes that the workflow made and start over.

Remove virtual machines or other clustered resources

If you created any virtual machines or other clustered resources, such as the network controllers for SDN, remove them first.

For example, to remove resources by name, use this cmdlet:

Get-ClusterResource -Name "<NAME>" | Remove-ClusterResource

Undo the storage steps

If you enabled Storage Spaces Direct, disable it by using the following script.

Warning: These cmdlets permanently delete any data in Storage Spaces Direct volumes. You can't undo this action.

Get-VirtualDisk | Remove-VirtualDisk
Get-StoragePool -IsPrimordial $False | Remove-StoragePool
Disable-ClusterS2D

Undo the clustering steps

If you created a cluster, remove it by using this cmdlet:

Remove-Cluster -CleanUpAD

To also remove cluster validation reports, run this cmdlet on every server that was part of the cluster:

Get-ChildItem C:\Windows\cluster\Reports\ | Remove-Item

Undo the networking steps

Run the following cmdlets on every server that was part of the cluster.

If you created a Hyper-V virtual switch, use this cmdlet:

Get-VMSwitch | Remove-VMSwitch

The Remove-VMSwitch cmdlet automatically removes any virtual adapters and undoes switch-embedded teaming of physical adapters.

If you modified network adapter properties such as name, IPv4 address, and VLAN ID, use the following cmdlets.

Warning: These cmdlets remove network adapter names and IP addresses. Make sure that you have the information that you need to connect afterward, such as an adapter for management that's excluded from the script. Also make sure that you know how the servers are connected in terms of physical properties like MAC address, not just the adapter's name in Windows.

Get-NetAdapter | Where Name -Ne "Management" | Rename-NetAdapter -NewName $(Get-Random)
Get-NetAdapter | Where Name -Ne "Management" | Get-NetIPAddress -ErrorAction SilentlyContinue | Where AddressFamily -Eq IPv4 | Remove-NetIPAddress
Get-NetAdapter | Where Name -Ne "Management" | Set-NetAdapter -VlanID 0

You're now ready to start the workflow.

Related content

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: davannaw-msft). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 11/04/2019
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。