Adds a network controller node to an existing network controller deployment.
Networking / Security · Risk: High · Documentation Verified
Last verified: 2026-10-26
Microsoft NetworkController reference: Adds a network controller node to an existing network controller deployment. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for Add-NetworkControllerNode. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Supported environments
Windows / NetworkController · Windows Server 2025 documentation; feature/module prerequisites apply
Parameters
-CertificateSubjectName
Specifies the subject name of the certificate used to perform this action.
-CertificateThumbprint
Specifies the digital public key X.509 certificate of a user account that has permission to perform this action. Specify this parameter only if you run this cmdlet on a computer that is not part of the network controller cluster.
-ComputerName
Specifies the name of the network controller node on which this cmdlet operates.
-Confirm
Prompts you for confirmation before running the cmdlet.
-Credential
Specifies a user credential that has permission to perform this action. The default is the current user. Specify this parameter only if you run this cmdlet on a computer that is not part of the network controller cluster.
-FaultDomain (required)
Specifies the servers that are likely to experience failure at the same time due to shared physical dependencies such as power and networking sources. Fault domains typically represent hierarchies that are related to these shared dependencies, with more servers likely to fail together from a higher point in the fault domain tree. During runtime, network controllers enumerate the fault domains in the cluster and attempt to spread out the network controller services so that they are in separate fault domains. This process helps ensure, in case of failure of any one fault domain, that the availability of that service and its state is not compromised. Fault domains are specified in a hierarchical format. For example: /DC1/Rack1/Host1, where DC1 is the datacenter name, Rack1 is the rack name and Host1 is the name of the host where the node is placed.
-Force
Forces the command to run without asking for user confirmation.
-Name (required)
Specifies the friendly name of the computer to be added to the deployment.
-NodeCertificate
Specifies the certificate used for authenticating the computer. You should only specify this parameter if the cluster is using certificate based authentication.
-NodeCertificateFindBy
Specifies the method by which to find the node certificate.
-PassThru
Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.
-RestInterface (required)
Specifies the name of the interface on the node that will receive requests from Representational State Transfer (REST) clients.
-Server (required)
Specifies the fully qualified domain name (FQDN), IP address, or hostname of the computer to be added to the deployment. If Kerberos is being used for cluster authentication, the FQDN must be provided.
-UseSsl
Indicates that the remote computer uses the Secure Sockets Layer (SSL) protocol to establish a connection to the Network Controller node. The default value of this parameter is false. Specify this parameter only if you run this cmdlet on a computer that is not part of the network controller cluster.
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Prerequisites
Windows with the NetworkController module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
Security considerations
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.
Examples
Example 1: Add network controller to an existing network controller deployment
This command adds a network controller node named Node1 to the existing network controller deployment. The FQDN of the computer is named NCNode1.contoso.com and the interface on the computer listening to REST requests is named Ethernet. Source: Microsoft, CC BY 4.0; transcript prompt/output removed. This example was not executed.