Tchater maintenant avec le support
Tchattez avec un ingénieur du 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

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 run 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 run 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 discoveries

An important aspect of 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
•
Enabling a cluster

Getting job information

You probably have configured and run discoveries in the Enterprise Reporter Configuration Manager. These job definitions are useful in understanding how the cmdlets work and provide good examples for you to follow when creating new jobs using cmdlets. The Get-ERJobDefinition cmdlet returns information on the jobs.

Syntax
Get-ERJobDefinition [-ClusterId <Nullable`1[Guid]>] [-ClusterName <String>] [-JobDefinitionName] <String>
Get-ERJobDefinition [-Unassigned [<SwitchParameter>]]
Get-ERJobDefinition -JobDefinitionId <Guid>
Get-ERJobDefinition -JobDefinition <JobDefinition>
Example 1

In this example, information about a job identified with the name of Active Directory is returned.

Get-ERJobDefinition -JobDefinitionName "Active Directory"

Output

JobDefinitionId : ecaae8bb-f0f8-48ee-91ff-da959a937dfa
JobTypeId : bec47934-cadf-4b94-8ff7-68efadc88165
Name : Active Directory
Description :
Configuration : <DiscoveryResolutionTask subType="ActiveDirectory"><Scopes><Scope
type="ActiveDirectory"><Content><Root class="Domain" inex="Include"><Ldap>LDAP:
//AMER.amer.sitraka.com/DC=AMER,DC=amer,DC=sitraka,DC=com</Ldap><Dns>
AMER.amer.sitraka.com</Dns><DC>AMERGENDC.AMER.amer.sitraka.com</DC>
</Root></Content></Scope></Scopes><Parameters><Parameter
key="GatherSharedEntities"><Value>False</Value></Parameter><Parameter
key="CollectDCs"><Value>True</Value></Parameter><Parameter
key="CollectAccounts"><Value>True</Value></Parameter><Parameter
key="CollectComputers"><Value>True</Value></Parameter><Parameter
key="CollectOUs"><Value>True</Value></Parameter><Parameter
key="CollectSites"><Value>True</Value></Parameter><Parameter
key="CollectTrusts"><Value>True</Value></Parameter><Parameter
key="CollectPhysicalComputerInfo"><Value>False</Value></Parameter><Parameter
key="FindForeignMember"><Value>False</Value></Parameter><Parameter
key="SyncLogon"><Value>False</Value></Parameter><Parameter
key="CollectPermissions"><Value>False</Value></Parameter><Parameter
key="CollectRemoteServices"><Value>False</Value></Parameter><Parameter
key="CollectPhotosForUsers"><Value>False</Value></Parameter>
</Parameters></DiscoveryResolutionTask>
AssignedClusterId : af0e6da4-10b9-4b20-bf5a-f19f0d71b589
CredentialId :
AssignedClusterName : First Cluster
IsTombstoned : False
Schedule : <Trigger Type="RunOnceTrigger" StartDateTime="2014-07-14T13:50:00Z"
Expression="2014-07-14 13:50:00Z@0 50 13 14 7 ? 2014" />
NextRun :
Example 2

In this example, information about all the jobs (the * wildcard is used in -JobDefinitionName) located on the cluster named Second Cluster is returned.

Get-ERJobDefinition -ClusterName "Second Cluster" -JobDefinitionName *

Output

JobDefinitionId : 7a8d758b-15e8-4f84-a30e-1c8545eed4f5
JobTypeId : bec47934-cadf-4b94-8ff7-68efadc88165
Name : Computer
Description :
Configuration : <DiscoveryResolutionTask subType="Computer"><Scopes><Scope type="Computer">
<Content><Rootclass="Domain" inex="Include"><Ldap>LDAP://AMER.amer.sitraka.com
/DC=RPTCH,DC=dev,DC=hal,DC=ca,DC=qsft</Ldap><Dns>AMER.amer.sitraka.com
</Dns></Root></Content></Scope></Scopes><Parameters><Parameter
key="GatherSharedEntities"><Value>False</Value></Parameter><Parameter
key="CollectAccounts"><Value>True</Value></Parameter><Parameter
key="CollectEventLogConfig"><Value>True</Value></Parameter><Parameter
key="CollectPolicies"><Value>True</Value></Parameter><Parameter
key="CollectPrinters"><Value>True</Value></Parameter><Parameter
key="CollectServices"><Value>True</Value></Parameter><Parameter
key="CollectShares"><Value>True</Value></Parameter><Parameter
key="CollectVolumes"><Value>True</Value></Parameter><Parameter
key="CollectExtendedWMIEntities"><Value>True</Value></Parameter><Parameter
key="PingTimeout"><Value>0</Value></Parameter></Parameters>
</DiscoveryResolutionTask>
AssignedClusterId : 390b0bd1-6488-4ace-b2cc-616925b55c06
CredentialId :
AssignedClusterName : Second Cluster
IsTombstoned : False
Schedule : <Trigger Type="RunOnceTrigger" StartDateTime="2014-07-15T13:58:00Z"
Expression="2014-07-15 13:58:00Z@0 58 13 15 7 ? 2014" />
NextRun :

As you can see in these examples, there is a lot of information contained in the job definition. The largest and seemingly most complicated part is the configuration, which contains all of the information about the jobs that you created using the Discovery Wizard. For more information about the configuration, see Creating a job.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation