Set-CMBoundary
Set-CMBoundary
Modifies boundary settings.
Syntax
Parameter Set: SetById
Set-CMBoundary -Id <String[]> [-NewName <String> ] [-Type <BoundaryTypes> {ADSite | IPRange | IPSubnet | IPV6Prefix} ] [-Value <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]
Parameter Set: SetByName
Set-CMBoundary -Name <String[]> [-NewName <String> ] [-Type <BoundaryTypes> {ADSite | IPRange | IPSubnet | IPV6Prefix} ] [-Value <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]
Parameter Set: SetByValueMandatory
Set-CMBoundary -InputObject <IResultObject> [-NewName <String> ] [-Type <BoundaryTypes> {ADSite | IPRange | IPSubnet | IPV6Prefix} ] [-Value <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]
Detailed Description
The Set-CMBoundary cmdlet modifies boundary settings.
In Microsoft System Center 2012 Configuration Manager, a boundary is an intranet location that contains one or more devices that you can manage. A boundary can be an IP subnet, Active Directory site name, IPv6 prefix, or an IP address range.
Parameters
-Id<String[]>
Specifies an array of boundary identifiers (IDs).
Aliases |
BoundaryId |
Required? |
true |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-InputObject<IResultObject>
Specifies an input object to this cmdlet. You can get the input object by using the Get-CMBoundary cmdlet.
Aliases |
none |
Required? |
true |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-Name<String[]>
Specifies an array of boundary names.
Aliases |
DisplayName |
Required? |
true |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-NewName<String>
Specifies a new name for a boundary.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-Type<BoundaryTypes>
Specifies a boundary type. Valid values are: ADSite, IPV6Prefix, IPSubnet, and IPRange.
Aliases |
BoundaryType |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-Value<String>
Specifies the data that describes the boundary. For example, an Active Directory site value can be Default-ADSite.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-Confirm
Prompts you for confirmation before running the cmdlet.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
<CommonParameters>
This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
Inputs
The input type is the type of the objects that you can pipe to the cmdlet.
Outputs
The output type is the type of the objects that the cmdlet emits.
Examples
Example 1: Rename a boundary
This command changes a boundary name from Default-ADSite to ADSiteBoundary01.
PS C:\> Set-CMBoundary –Name "Default-ADSite" –NewName "ADSiteBoundary01"
Example 2: Modify the value of a boundary by using an InputObject
In this example, the first command gets a boundary that has the ID of 16777217 and inserts it into the input object $BoundaryObj.
The second command identifies the boundary by using the input object $BoundaryObj and modifies its value to IPSubnet17.
PS C:\> $BoundaryObj = Get-CMBoundary –Id "16777217"PS C:\> Set-CMBoundary –InputObject $BoundaryObj –Value "IPSubnet17"