Chat now with support
Chat mit 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 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.

Disabling a node

There are times when a system may require maintenance or be taken down for some specific reason. During these times you will want to disable the node installed on that system. Disabling the node allows the cluster to manage the jobs based on the remaining nodes that are available for work.

* 
NOTE: Even though you may have disabled a node, any jobs running on the node continue to be processed until completed. Only new jobs are not assigned to the node. Therefore, if maintenance is planned for the system, consider disabling the node in plenty of time for any job to finish.
Syntax
Disable-ERNode [-Node] <Node> [-CancelTasks [<SwitchParameter>]] [-PassThru [<SwitchParameter>]]
Disable-ERNode [-Cluster] <String> [-ComputerName] <String> [-CancelTasks [<SwitchParameter>]] [-PassThru [<SwitchParameter>]]
Example 1

In this example, the node associated with the cluster named First Cluster that is installed on the computer named AMERGEN01 is disabled.

Disable-ERNode -Cluster "First Cluster" -ComputerName AMERGEN01
Example 2

In this example, the node information is stored in the variable $node. The information contained in $node is then used as input to the Disable-ERNode cmdlet.

$node = Get-ERNode -Node AMERGEN01.amer.sitraka.com
Disable-ERNode -Node $node
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen