.png)
Block-CMConflictingRecord
Updated: March 1, 2013
Applies To: System Center 2012 Configuration Manager SP1
Block-CMConflictingRecord
Syntax
Parameter Set: SearchByNameMandatory Block-CMConflictingRecord -Name <String> [-Confirm] [-WhatIf] [ <CommonParameters>] Parameter Set: SearchByIdMandatory Block-CMConflictingRecord -Id <String> [-Confirm] [-WhatIf] [ <CommonParameters>] Parameter Set: SearchByValueMandatory Block-CMConflictingRecord -ConflictingRecord <IResultObject> [-Confirm] [-WhatIf] [ <CommonParameters>]
Detailed Description
The Block-CMConflictingRecord cmdlet creates a blocked record for a client that has a conflicting record in Microsoft System Center 2012 Configuration Manager.
When System Center 2012 Configuration Manager recognizes a new client, it uses hardware information to check whether it previously created a record for that computer. For example, you might have reinstalled the operating system. The previous client record still exists with the same hardware information. If you manually resolve conflicts, you have the option to merge the new record with the existing record, create a new record, or create a record as a blocked record. You can also configure System Center 2012 Configuration Manager to resolve conflicts automatically.
You can specify a conflict by using a name or ID or you can use the Get-CMConflictingRecord cmdlet to obtain one.
CMConflictingRecordAn object that represents the conflicting recordsSiteCodeThe site code of the Configuration Manager site where conflicting records existIdThe unique identifier given to a conflicting recordNameSpecifies the name of a conflicting recordConflictingRecordAn object that represents the conflicting records
Parameters
-ConflictingRecord<IResultObject>
Specifies a conflicting record object. To obtain a conflicting record object, use the Get-CMConflictingRecord cmdlet.
Aliases | none |
Required? | true |
Position? | named |
Default Value | none |
Accept Pipeline Input? | True (ByPropertyName) |
Accept Wildcard Characters? | false |
-Id<String>
Specifies an ID for the conflicting records.
Aliases | Smsid |
Required? | true |
Position? | named |
Default Value | none |
Accept Pipeline Input? | True (ByPropertyName) |
Accept Wildcard Characters? | false |
-Name<String>
Specifies a name for the conflicting records.
Aliases | AgentName |
Required? | true |
Position? | named |
Default Value | none |
Accept Pipeline Input? | True (ByPropertyName) |
Accept Wildcard Characters? | false |
-Confirm
Prompts you for confirmation before executing the command.
Required? | false |
Position? | named |
Default Value | false |
Accept Pipeline Input? | false |
Accept Wildcard Characters? | false |
-WhatIf
Describes what would happen if you executed the command without actually executing the command.
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.
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: Create a blocked record for a named conflict
This command creates a blocked record for the conflict named CR07.
PS C:\> Block-CMConflictingRecord -Name "CR07"
Example 2: Create a blocked record by using a variable
This example creates a blocked record for the conflict named CR07.
The first command gets a conflicting record named CR07 and saves it in the $CMCR variable.
The second command creates a blocked record for the conflict in $CRCM.
PS C:\> $CMCR = Get-CMConflictingRecord -Name "CR07"PS C:\>Block-CMConflictingRecord -ConflictingRecord $CMCR
