サポートと今すぐチャット
サポートとのチャット

Enterprise Reporter 3.5.1 - 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

Loading the Enterprise Reporter cmdlets

You can create a profile file that displays the list of Quest Enterprise Reporter cmdlets each time you open Windows Powershell.

To create a profile to display the list of Enterprise Reporter cmdlets
1
On the system where Enterprise Reporter is installed, open Windows PowerShell.
2
Enter this command to set the registry value so you can run scripts:
Set-Executionpolicy RemoteSigned
3
Enter this command to create a Windows PowerShell profile file:
New-Item -path $profile -type file –force
4
Enter this command to open the profile file in Notepad:
notepad $profile
5
Add the following commands to load the Enterprise Reporter snapins, connect to the server, and display the list of cmdlets:
add-pssnapin Quest.Reporter.Configuration
add-pssnapin Quest.Reporter.Reporting
Connect-ERConfigurationServer localhost
Connect-ERReportingServer localhost
get-command -Module quest*
6
Save the profile and exit Notepad.
7
Exit Windows PowerShell, and then open it.
The snapins load and a list of commands display.

Using cmdlets to manage clusters and nodes

The examples in this section deal with the basics of Enterprise Reporter, which are clusters and nodes for the clusters. Without nodes, clusters cannot direct any work to be done and without clusters, nodes cannot do any work.

This section contains the following examples:

•
Creating a cluster
•
Creating a node
•
Disabling a node
•
Enabling a node
•
Finding a node by name
•
Piping cmdlets
•
Finding a cluster by name
•
Disabling a cluster
•
Enabling a cluster

Creating a cluster

The New-ERCluster cmdlet creates a new cluster in Enterprise Reporter Configuration Manager on which discoveries can be run. Nodes are associated with this cluster, which can be installed on systems in remote locations to allow jobs to run closer to the physical location.

Syntax
New-ERCluster [-Name] <String> [[-Description] <String>] [[-SharedDataLocation] <String>] [[-ConnectionTimeout] <String>] [[-CommandTimeout] <String>]
* 
NOTE: The only parameter that is required is Name. All other variables can be added at a different time. Any parameter that contains a space must be enclosed in quotation marks.
Example

In this example, the new cluster named Second Cluster is created.

New-ERCluster -Name "Second Cluster" -Description "This is a test description" –SharedDataLocation C:\Shared -ConnectionTimeout 100 -CommandTimeout 500

Creating a node

The Add-ERNode cmdlet creates a new node that is associated with a cluster in Enterprise Reporter Configuration Manager. Nodes run the jobs assigned to them by the cluster. A cluster can have numerous nodes installed on different systems, which allows for more efficient processing of jobs and returns quicker results.

Syntax
Add-ERNode [-Cluster] <String> [-ComputerName] <String> [-Credential] <PSCredential> [[-MaxJobSlots] <Int32>]
* 
NOTE: Only the -MaxJobSlots parameter is optional; all other parameters must be supplied.
Example

This example involves a three step process. The first step encrypts the password used by the service account before sending it across the network. The second step combines the encrypted password with the service account into a new system object containing the credentials for the service account. The third step indicates the cluster, identifies the server where the node is to be installed, supplies the credentials, and defines how many jobs slots the node is to use.

secpasswd = ConvertTo-SecureString 'pA$$w0d' -AsPlainText -Force
credentials = New-Object System.Management.Automation.PSCredential ('AMER\Administrator', $secpasswd)
Add-ERNode "Second Cluster" "AMERGEN02" $credentials 5

Now the cluster named Second Cluster, which was created in the previous example (see Creating a cluster), has a node associated with it and is ready to run a job.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択