COMMAND EVERYTHING.

New-NetworkControllerNodeObject

Creates a network controller node object.

Networking / Security · Risk: High · Documentation Verified

Last verified: 2026-10-26

Microsoft NetworkController reference: Creates a network controller node object. 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.

New-NetworkControllerNodeObject -Name <String> -Server <String> -FaultDomain <String> -RestInterface <String>
 [-NodeCertificate <X509Certificate2>] [-NodeCertificateFindBy <X509FindType>]
 [-CertificateSubjectName <String>] [-WhatIf] [-Confirm] [<CommonParameters>]

Copied 0 times

Required permissions

Use an account with the target resource permissions documented for New-NetworkControllerNodeObject. 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.
-Confirm: Prompts you for confirmation before running the cmdlet.
-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, a network controller considers the fault domains in the cluster and attempts 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.
-Name (required): Specifies the name of the computer to be added to the deployment.
-NodeCertificate: Specifies the certificate used for authenticating the computer. You only need to specify this parameter if the cluster is using certificate based authentication.
-NodeCertificateFindBy: Specifies the method by which to find the node certificate.
-RestInterface (required): Specifies the name of the interface on the node that will receive requests from the 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 authentication is being used for cluster authentication, FQDN must be provided.
-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: Create a network controller node object

New-NetworkControllerNodeObject -Name "Node1" -Server "NCNode1.contoso.com" -FaultDomain "fd:/rack1/host1" -RestInterface "Ethernet"

This command creates a network controller node object named Node1. The fully qualified domain name of the computer is 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.

Sources

https://github.com/MicrosoftDocs/windows-powershell-docs/blob/b7645dd8c687139b28e845119da30ec670526507/docset/winserver2025-ps/NetworkController/New-NetworkControllerNodeObject.md

https://learn.microsoft.com/powershell/module/networkcontroller/new-networkcontrollernodeobject?view=windowsserver2025-ps

Personal collections

Explain or customize this command with AI

Related commands

Get-NetIPInterface

Add-MpPreference

Get-MpPerformanceReport

Add-DhcpServerInDC