Chat now with support
Chat mit Support

Enterprise Reporter 3.2.1 - Configuration Manager User Guide

Product Overview Configuring the Configuration Manager
Starting the Configuration Manager Finding Answers and Getting Help An Overview of Enterprise Reporter Communications and Credentials Required Logged In User Details Setting Up Your First Collection Computers Modifying your Deployment Improving the Performance of Your Discoveries What does the status of a node or cluster indicate? Using the Credential Manager Changing the Credentials used by the Enterprise Reporter Server Configuring Global Settings Global Discovery Settings
Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your 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 Office 365 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

Finding a cluster by name

As with nodes you can retrieve information about clusters. This information includes whether the cluster is enabled or disabled, if the cluster is using a shared data location, and the path of the shared data location.

Syntax
Get-ERCluster [[-Cluster] <String>]
Example 1

This example returns information on all clusters associated with Enterprise Reporter.

Get-ERCluster
Example 2

This example returns information on the cluster named Second Cluster. Note that he cluster name is in quotes because Windows PowerShell® requires that any parameter containing spaces must be enclosed with quote marks.

Get-ERCluster -Cluster "Second Cluster"

Disabling a cluster

As with nodes, there are times when a system may require maintenance or you may want to stop the processing of specific jobs for some specific reason. During these times you will want to disable the cluster. Disable a cluster, effectively stopping new jobs and tasks from starting on any nodes within that cluster.

* 
NOTE: Even though you may have disabled a cluster, any jobs running on the cluster will continue to execute until completed. Disabling the cluster will disable all the nodes associated with it.
Syntax
Disable-ERCluster [-Cluster] <Cluster> [-CancelJobs [<SwitchParameter>]] [-PassThru [<SwitchParameter>]]
Disable-ERCluster [-Name] <String> [-CancelJobs [<SwitchParameter>]] [-PassThru [<SwitchParameter>]]
Example 1

In this example, the cluster named First Cluster is disabled.

Disable-ERCluster -Name "First Cluster"
Example 2

In this example, jobs scheduled to run on the cluster named First Cluster are canceled, and then the cluster is disabled. Jobs currently running will finish even though the cluster is disabled.

Disable-ERCluster "First Cluster" -CancelJobs
Example 3

In this example, the Get-ERCluster cmdlet first retrieves information about the cluster named First Cluster, and then stores it in the $cluster variable. Next, the cluster with the name stored in the $cluster.name variable is disabled.

If the Get-ERCluster cmdlet is executed without identifying a cluster, it returns the information on all clusters. This technique can be useful when there are a number of clusters since they can be looped through disabling each one.

$cluster = Get-ERCluster “First Cluster”
Disable-ERCluster $cluster.name
Example 4

In this example, the Get-ERCluster cmdlet retrieves information for the cluster named Second Cluster and pipes it into the Disable-ERCluster cmdlet.

Get-ERCluster "Second Cluster" | Disable-ERCluster

Enabling a cluster

Once a cluster is enabled, the nodes assigned to the cluster start processing jobs. As with disabling the cluster, enabling the cluster will enable all the nodes associated with it.

Syntax
Enable-ERCluster [-Cluster] <Cluster> [-PassThru [<SwitchParameter>]] [<CommonParameters>]
Enable-ERCluster [-Name] <String> [-PassThru [<SwitchParameter>]] [<CommonParameters>]
Example 1

This example enables the cluster named First Cluster.

Enable-ERCluster "First Cluster"
Example 2

This example first stores cluster information in the $cluster variable, and then uses it as input to the Enable-ERCluster cmdlet. Note that the cluster name does not need to be parsed out and passed to the Enable-ERCluster cmdlet.

$cluster = Get-ERCluster
Enable-ERCluster $cluster
Example 2

This example uses Get-ERCluster to retrieve information for the cluster named First Cluster and pipes it to the Enable-ERCluster cmdlet.

Get-ERCluster -Cluster "First Cluster" | Enable-ERCluster

Using cmdlets to manage jobs (discoveries)

An important aspect of Quest™ Enterprise Reporter, discoveries return information about the systems in your environment. Discoveries gather data about Active Directory®, computers, SQL Server®, and NTFS permissions for files and folders. When using Enterprise Reporter cmdlets, discoveries are referred to as jobs. The examples in this section demonstrate how to create and run jobs using cmdlets.

This section contains the following examples:

•
Getting job information
•
Creating a job
•
Running a job
•
Scheduling a job
•
Deleting a job
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen