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

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

Enabling a node

Once any work has been done on the system and you want to bring the node back into use, you need to enable the node so that the cluster knows the node is available and ready for work. Once the node is enabled, the cluster will assign the jobs waiting to be processed.

Syntax
Enable-ERNode [-Node] <Node> [-PassThru [<SwitchParameter>]]
Enable-ERNode [-Cluster] <String> [-ComputerName] <String> [-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 enabled.

Enable-ERNode -Cluster "First Cluster" -Passthru -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 Enable-ERNode cmdlet.

$node = Get-ERNode -Node AMERGEN01.amer.sitraka.com
Enable-ERNode -Node $node

Finding a node by name

As nodes are an important part of the job processing, knowing about the nodes is vital so that you can ensure they are functioning properly and that the cluster has enough nodes to process jobs. The Get-ERNode cmdlet retrieves information about a node. You In addition, a cluster can be specified to show all nodes associated with the cluster. A computer can also be queried to see if there is a node install on it.

Syntax
Get-ERNode [[-Node] <String>] [[-Cluster] <String>]
Example 1

This example returns information from all nodes in all clusters.

Get-ERNode
Example 2

This example returns all nodes on the computer named AMERGEN01.

Get-ERNode -Node AMERGEN01
Example 3

This example returns all nodes in the cluster named First Cluster.

Get-ERNode -Cluster "First Cluster"

Piping cmdlets

Cmdlets can pipe the output from one cmdlet into another cmdlet. This feature is useful and powerful when you pipe the Get-ERNode cmdlet into Enable-ERNode and Disable-ERNode cmdlets.

Example 1

This example disables all nodes associated with the cluster named First Cluster. The data for all nodes is retrieved by the Get-ERNode cmdlet, and then piped into the Disable-ERNode cmdlet.

Get-ERNode -Cluster "First Cluster" | Disable-ERNode
Example 2

This example enables all nodes associated with the cluster named First Cluster. The data for all nodes is retrieved by the Get-ERNode cmdlet, and then piped into the Enable-ERNode cmdlet.

Get-ERNode -Cluster "First Cluster" | Enable-ERNode
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen