Configures a new entry point for multisite DirectAccess.
PowerShell · Risk: High · Documentation Verified
Last verified: 2026-10-26
Microsoft DirectAccessClientComponents reference: Configures a new entry point for multisite DirectAccess. 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 New-DAEntryPointTableItem. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Supported environments
Windows / DirectAccessClientComponents · Windows Server 2025 documentation; feature/module prerequisites apply
Parameters
-ADSite (required)
Specifies the Active Directory Domain Services (AD DS) site name associated with the entry point. When a client computer connects to an entry point, the computer becomes associated with the AD DS site specified.
-AsJob
Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete. The cmdlet immediately returns an object that represents the job and then displays the command prompt. You can continue to work in the session while the job completes. To manage the job, use the *-Job cmdlets. To get the job results, use the Receive-Job cmdlet. For more information about Windows PowerShell background jobs, see about_Jobs.
-CimSession
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
-Confirm
Prompts you for confirmation before running the cmdlet.
-EntryPointIPAddress (required)
Specifies the IPv6 address of the entry point to use for connectivity. The cmdlet fails if the IP address specified is not within the IP address range specified by *EntryPointRange*.
-EntryPointName (required)
Specifies the name of the entry point. The entry point name is usually the friendly name of the location, such as Redmond or Paris. Specify the name of the entry point by using double quotes (" ").
-EntryPointRange (required)
Specifies the IPv6 address range associated with computers connecting through this entry point. Specify the IPv6 range in classless inter-domain routing (CIDR) notation. The following is an example of an *EntryPointRange* entry: {2001:4898:e0:305d::100:1/128, 2001:4898:e0:305d::100:2/128, 2001:4898:e0:3084::/64}
-GPOSession (required)
Specifies the Group Policy session to send configuration information. You can use *GPOSession* with the NetGPO cmdlets to aggregate multiple operations performed on a Group Policy Object. *GPOSession* cannot be used in conjunction with *PolicyStore*.
-GslbIP
Specifies the IP address associated with the new entry point, if using DirectAccess in conjunction with global server load balancing (GSLB) site balancing.
-IPHttpsProfile
Specifies the IPHTTPs profile name to be used for connectivity. You specify the name of the profile in double quotes (" "). New-DAEntryPointTableItem fails if the profile does not already exist in the GPO that contains the configuration. For more information about IPHTTPs profiles, see the NetIPHTTPsConfiguration cmdlets in the NetworkTransition module.
-PolicyStore (required)
Specifies the policy store into which the cmdlet adds the entry point. To add the entry point to a Group Policy Object, specify the GPO name using the following format: "Domain\GPOName" To add the entry point information to a computer's local GPO, specify the computer's local GPO name in the following format: "GPO:\" *PolicyStore* cannot be used in conjunction with *GPOSession*.
-TeredoServerIP
Specifies the IP address of the Teredo server for the new entry point.
-ThrottleLimit
Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Prerequisites
Windows with the DirectAccessClientComponents 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.