Test-MbamReport

Checks server prerequisites and validates parameter values for the Reports feature.

Syntax

Test-MbamReport
    [-ComplianceAndAuditDBConnectionString <String>]
    -ComplianceAndAuditDBCredential <PSCredential>
    [-Detailed]
    -ReportsReadOnlyAccessGroup <String>
    [-SsrsInstance <String>]
    [<CommonParameters>]

Description

The Test-MbamReport cmdlet checks server prerequisites and validates parameter values for the Microsoft BitLocker Administration and Monitoring (MBAM) Reports feature.

Examples

Example 1: Check prerequisites and validate parameters for the Reports feature

PS C:\> Test-MbamReport -ComplianceAndAuditDBConnectionString "Data Source=MyDatabaseServer;Initial Catalog=MBAM Compliance Status;Integrated Security=True" -ReportsReadOnlyAccessGroup "MyDomain\MyReportsGroup"
True

This command checks the prerequisites and validates the parameters for the Reports feature on the local server. The connection string specifies that ContosoDatabaseServer hosts the Compliance and Audit Database. The cmdlet prompts you to enter credentials for the Compliance and Audit Database. The reports group is ContosoDomain\ReportsGroup.

Example 2: View details about prerequisites and validation for the Reports feature

PS C:\> Test-MbamReport -ComplianceAndAuditDBConnectionString "Data Source=MyDatabaseServer;Initial Catalog=MBAM Compliance Status;Integrated Security=True" -ReportsReadOnlyAccessGroup "MyDomain\MyReportsGroup" -Detailed
ID                  Type  Message
--                  ----  -------
ReportsInstallation Error Unable to connect to the Reporting Services web service. Error message: The request failed with HTTP status 504: Proxy Timeout (The connection timed out.).
False

This command displays detailed information about prerequisites and validation of parameters for the Reports feature. This command specifies the Detailed parameter.

Required Parameters

-ComplianceAndAuditDBCredential

Specifies the domain account credentials that the local SQL Server Reporting Services instance uses to connect to the Compliance and Audit Database. The domain user in the credentials must be the same as or a member of the report account of the Compliance and Audit Database.

Important: For improved security, use an account that has limited privileges. Also, configure the account so that the password never expires.

Type:PSCredential
Aliases:ComplianceDBCred
Position:Named
Default value:None
Accept pipeline input:True (ByPropertyName, ByValue)
Accept wildcard characters:False
-ReportsReadOnlyAccessGroup

Specifies a domain user group. Specify a group that has read permissions for the reports.

Type:String
Aliases:ReportsGroup
Position:Named
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False

Optional Parameters

-ComplianceAndAuditDBConnectionString

Specifies a connection string. The local Microsoft SQL Server Reporting Services uses the string that this parameter specifies to connect to the Compliance and Audit Database feature. The connection string must contain values for the Integrated Security and Initial Catalog fields.

Type:String
Aliases:ComplianceDB
Position:Named
Default value:None
Accept pipeline input:True (ByPropertyName)
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
Accept pipeline input:False
Accept wildcard characters:False
-SsrsInstance

Specifies the SQL Server Reporting Services instance. After installation, this instance hosts the reports. If you do not specify an instance, the cmdlet uses the default instance, MSSQLSERVER.

Type:String
Position:Named
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False

Outputs

bool