Chat now with support
Chat with Support

Enterprise Reporter 3.5 - Configuration Manager User Guide

Product Overview Configuring the Configuration Manager
Starting the Configuration Manager Finding answers and getting help Overview of Enterprise Reporter Communications and Credentials Required Using the Credential Manager Setting Up Your First Collection Computers (Nodes) Modifying Your Deployment Configuring Global Settings Customizing the Configuration Manager View
Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery (Name) Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your on-premises discoveries
Choosing your Active Directory Scopes Choosing your Computer Scopes Choosing Your Exchange Scopes Choosing Your File Storage Analysis Scopes Choosing Your Microsoft SQL Scopes Choosing Your NTFS Scopes Choosing Your Registry Scopes
Step 2b: Choose scopes for your cloud discoveries Step 3. Schedule your Discovery Step 4: Review the summary
Managing Discoveries Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Using cmdlets to run reports

Now that you have collected data for your environment, you will want to produce reports with the data. Normally this is done using the Report Manager, but there are a number of cmdlets available to provide reports. The examples in this section demonstrate how to run reports using cmdlets.

This section contains the following examples:

Connecting to the server

Before you can use the report cmdlets, you must establish a connection to the Enterprise Reporter server. If you do not have your profile set up (see Loading the Enterprise Reporter cmdlets), you will need to establish a connection.

In this example, a connection is established to the AMERGEN01 server through port 7738.

Getting report information

Report Manager has a report library that is broken into a logical folder structure with reports in each folder. The functional cmdlets require the ID and path associated with each report and not just the report name. To get the report ID and path, use the Get-ERReport cmdlet. You can use wildcard expressions with this cmdlet. The wildcard search is performed on the full report path including folder names and report name.

This example returns all information on the Domain Accounts report.

Output

This example returns all the reports that begin with Domain.

Exporting a report definition

Reports in Report Manager can be modified and configured. The modified report can be exported to a designated location for disaster recovery or to share with others. The complete report information obtained from the Get-ERReport cmdlet is required when performing the export. For more information, see Getting report information.

In this example, the Get-ERReport cmdlet places the report information for a report in the Report Library into the $rpt variable. Next, the report definition is exported to the c:\ drive. The exported definition contains the report name and the report Id: Domain Users_95ccdb73-b815-47d2-af98-bc359201b6cd.xrd.

In this example, the Get-ERReport cmdlet places the report information for a report located in My Reports into the $rpt variable. Next, the report definition is exported to the c:\ drive. The exported definition contains the report name and the report Id: Domain Computer Information_e4067d44-b100-46e9-94da-8c3348584b50.xrd.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating