Edit

Share via

Test-MbamCMIntegration

  • Reference
Module:
MBAM

Checks server prerequisites and validates parameters.

Syntax

Test-MbamCMIntegration
    [-Detailed]
    [-SsrsServer <String>]
    [-SsrsInstance <String>]
    [-ReportsOnly]
    -ReportsCollectionID <String>
    -BitLockerProtectionBaselineLogicalName <String>
    -OperatingSystemDriveConfigurationItemLogicalName <String>
    -FixedDataDriveConfigurationItemLogicalName <String>
    [<CommonParameters>]
Test-MbamCMIntegration
    [-Detailed]
    [-SsrsServer <String>]
    [-SsrsInstance <String>]
    [<CommonParameters>]

Description

The Test-MbamCMIntegration cmdlet checks the server prerequisites and validates the parameters for the Microsoft BitLocker Administration and Monitoring (MBAM) Microsoft Endpoint Configuration Manager Integration feature.

Examples

Example 1: Check prerequisites to enable integration

PS C:\> Test-MbamCMIntegration

This command tests the prerequisites for enabling the MBAM Microsoft Endpoint Configuration Manager Integration on the local Configuration Manager server. The MBAM reports are deployed on the default SQL Server Reporting Services instance, MSSQLSERVER.

Example 2: Check prerequisites to enable integration with detailed output

PS C:\> Test-MbamCMIntegration -Detailed


ID             Type  Message
--             ----  -------
CmInstallation Error This feature can be installed only on a server that is running Microsoft Endpoint Configuration Manager.

This command checks the prerequisites to enable the MBAM Microsoft Endpoint Configuration Manager Integration feature on the local Configuration Manager server with detailed output.

Parameters

-BitLockerProtectionBaselineLogicalName

Specifies the logical name of the BitLocker protection baseline.

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

-Detailed

Indicates that the cmdlet displays detailed information about the prerequisite check and parameter validation failures.

Type:SwitchParameter
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-FixedDataDriveConfigurationItemLogicalName

Specifies the logical name of the fixed data drive configuration item.

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

-OperatingSystemDriveConfigurationItemLogicalName

Specifies the logical name of the operating system drive configuration item.

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

-ReportsCollectionID

Specifies an existing collection ID. This ID is used by the reports to set the default collection for which the reports display compliance data.

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

-ReportsOnly

Indicates that only the Configuration Manager reports are deployed.

Type:SwitchParameter
Position:Named
Default value:None
Required:True
Accept pipeline input:False
Accept wildcard characters:False

-SsrsInstance

Specifies the SQL Server Reporting Services instance. This instance hosts the Configuration Manager reports. This parameter is ignored if the server has Configuration Manager installed.

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

-SsrsServer

Specifies the server with the SQL Server Reporting Services point role. This server hosts the Configuration Manager reports. If you do not specify a server, the Configuration Manager reports are deployed to the local server.

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

Outputs

bool