Edit

Add-CMObjectSecurityScope

  • Reference
Module:
ConfigurationManager

Add a security scope to an object.

Syntax

Add-CMObjectSecurityScope
   -InputObject <IResultObject[]>
   [-Scope] <IResultObject[]>
   [-DisableWildcardHandling]
   [-ForceWildcardHandling]
   [-WhatIf]
   [-Confirm]
   [<CommonParameters>]
Add-CMObjectSecurityScope
   -Id <String>
   -InputObject <IResultObject[]>
   [-DisableWildcardHandling]
   [-ForceWildcardHandling]
   [-WhatIf]
   [-Confirm]
   [<CommonParameters>]
Add-CMObjectSecurityScope
   -InputObject <IResultObject[]>
   [-Name] <String>
   [-DisableWildcardHandling]
   [-ForceWildcardHandling]
   [-WhatIf]
   [-Confirm]
   [<CommonParameters>]

Description

Use this cmdlet to add a security scope to a Configuration Manager object.

For more information on security scopes, see Fundamentals of role-based administration in Configuration Manager.

Note

Run Configuration Manager cmdlets from the Configuration Manager site drive, for example PS XYZ:\>. For more information, see getting started.

Examples

Example 1: Add a security scope to application objects

The first command creates a security scope object named Scope1 and stores it in the $Scope variable.

The second command gets all application objects whose name begins with "Central". It then uses the pipeline operator to pass the objects to Add-CMObjectSecurityScope. This cmdlet adds the security scope to each application object.

$Scope = New-CMSecurityScope -Name "Scope1" -Description "Security scope 1"
Get-CMApplication -Name "Central*" | Add-CMObjectSecurityScope -Scope $Scope

Parameters

-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

-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

-Id

Specify the ID of a security scope to add to a Configuration Manager object. This value is the CategoryID property, for example SMS00UNA for the Default scope.

Type:String
Aliases:SecurityScopeId
Position:Named
Default value:None
Required:True
Accept pipeline input:False
Accept wildcard characters:False

-InputObject

Specify an array of Configuration Manager objects to add the security scope. To get this object, use the Get cmdlet for the object type. For example, Get-CMApplication for app objects.

Type:IResultObject[]
Position:Named
Default value:None
Required:True
Accept pipeline input:True
Accept wildcard characters:False

-Name

Specify the name of a security scope to add to a Configuration Manager object.

Type:String
Aliases:SecurityScopeName
Position:0
Default value:None
Required:True
Accept pipeline input:False
Accept wildcard characters:False

-Scope

Specify an array of security scope objects to add. To get this object use the Get-CMSecurityScope cmdlet.

Type:IResultObject[]
Aliases:SecurityScope, SecuredCategory, Scopes, SecurityScopes, SecuredCategories
Position:0
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

Microsoft.ConfigurationManagement.ManagementProvider.IResultObject[]

Outputs

System.Object