New-CMBoundaryGroup
Creates a new boundary group.
Syntax
New-CMBoundaryGroup
[-AddSiteSystemServer <IResultObject[]>]
[-AddSiteSystemServerName <String[]>]
[-DefaultSiteCode <String>]
[-Description <String>]
-Name <String>
[-DisableWildcardHandling]
[-ForceWildcardHandling]
[-WhatIf]
[-Confirm]
[<CommonParameters>] Description
The New-CMBoundaryGroup cmdlet creates a new boundary group. A boundary group is a collection of boundaries.
You can use boundary groups to manage network locations. You must assign boundaries to boundary groups before you can use the boundary group. Boundary groups enable client computers to find a primary site for client assignment, which is referred to as automatic site assignment, and a list of available site systems that have content. For more information about boundaries, see Planning for Boundaries and Boundary Groups in Configuration Manager and the New-CMBoundary cmdlet.
Note
Run Configuration Manager cmdlets from the Configuration Manager site drive, for example PS XYZ:\>. For more information, see getting started.
Examples
Example 1: Create a new boundary group
This example creates a new boundary group. After the new boundary group is created, the command displays an unpopulated list of boundary properties. To refresh and see a populated list, use the Get-CMBoundaryGroup cmdlet.
New-CMBoundaryGroup -Name "BGroup05"Parameters
-AddSiteSystemServer
Specifies the site system server and link speed as the key/value pair in a hash table. Valid values are:
- FastLink
- Slowlink
For example: @{"Server01.contoso.com" = "FastLink"}
Important: Starting in version 1610, FastLink is the only supported value for the hash table.
| Type: | IResultObject[] |
| Aliases: | AddSiteSystemServers |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-AddSiteSystemServerName
| Type: | String[] |
| Aliases: | AddSiteSystemServerNames |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Confirm
Prompts you for confirmation before running the cmdlet.
| Type: | SwitchParameter |
| Aliases: | cf |
| Position: | Named |
| Default value: | False |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-DefaultSiteCode
Specifies the default site code for the boundary group.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Description
Specifies a description for the new boundary.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-DisableWildcardHandling
This parameter treats wildcard characters as literal character values. You can't combine it with ForceWildcardHandling.
| Type: | SwitchParameter |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-ForceWildcardHandling
This parameter processes wildcard characters and may lead to unexpected behavior (not recommended). You can't combine it with DisableWildcardHandling.
| Type: | SwitchParameter |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Name
Specifies a name for the new boundary.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet doesn't run.
| Type: | SwitchParameter |
| Aliases: | wi |
| Position: | Named |
| Default value: | False |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
Inputs
None
Outputs
IResultObject