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

Security Explorer 9.9.2 - User Guide

Getting Started with Security Explorer Managing permissions Searching Managing security Managing objects
Managing folders and files Managing shares Managing registry keys Managing services Managing tasks Managing groups and users Managing Favorites Managing Enterprise Scopes Updating licenses Managing network drives
Working with Microsoft SQL Server Working with Microsoft Exchange
Checking minimum requirements Viewing Exchange permissions Granting Exchange permissions Revoking Exchange permissions Cloning Exchange permissions Searching for Exchange server objects and permissions Backing up and restoring Exchange server security Modifying Exchange permissions Managing Exchange group memberships Exporting Exchange security permissions Creating Exchange databases Creating public folder mailboxes Managing Exchange administrators Managing Exchange distribution groups Managing mail contacts Managing mail users Managing mailboxes Managing mailbox folders Managing public folders Using role based access control Setting options for Exchange security
Working with Microsoft SharePoint Working with Access Explorer Working with Microsoft Active Directory Customizing Security Explorer Using the command line Using PowerShell cmdlets Troubleshooting

Changing the agent configuration on a managed computer

At some point you may want to look at specific folders and files on a managed computer. The data roots for the agent can be changed with an Access Explorer cmdlet. Note that the cmdlet overwrites the current data roots selection, so if you are already scanning a folder called Files1, and you want to include a folder called Files2, you cannot just add the new folder with the cmdlet. You need to specify both Files 1 and Files 2 in the cmdlet. Also the ID for the agent is required, which can be found using the Get-AEAgentInstances cmdlet. For more information, see Identifying agents on a managed computer.

In this example, the agent with the ID BW_aaabd11494ed4f19921a91b92ee0979d is set to another location for the data roots selection. Any previous setting will be removed as this cmdlet does not add a new data root location, but replaces the current one. Because the managed host ID is provided, the cmdlet does not need to search all of the deployed agent to see if any match the one provided.

In this example, three separate folders on the C:\ Drive are selected for the data roots settings. You can add any number of folders as long as they are separated by a comma. Note that the data root locations are enclosed in quotation marks. The first two data root locations do not need the quotation marks, but the third one does as it contains spaces. It is a good habit to enclose all items like this in quotation marks whether they need them or not.

In this example, the complete C:\ drive is being set as the data root.

Restarting the agent

There are two cmdlets that allow you to restart a single agent or restart all the agents on a managed computer.

Restarting a single agent

The restart operations for the specified agent instances are performed asynchronously by the management server. This cmdlet will not wait for the service restart operations to complete before returning.

The agent with the ID BW_aaabd11494ed4f19921a91b92ee0979d is restarted. Use the Get-AEAgentInstances cmdlet to obtain the agent Id for the AgentId parameter. This cmdlet does not return any values.

Restart operations for the agent instances associated with the specified managed computer are performed asynchronously by the management server. This cmdlet will not wait for the service restart operations to complete before returning.

The agent on the managed computer with the ID 33bf3e5b-5edf-4b28-9eee-7fff84de2bca is restarted. Use the Get-AEManagedComputers cmdlet to obtain the value for the ManagedComputerId parameter. This cmdlet does not return any values.

Updating an agent

There are times when an agent update may be require or may be available. An update can be performed with a cmdlet.

This example updates the agent specified if there is an agent update available. See the Get-AEAgentInstances cmdlet on how to get the agent Id for the AgentId parameter.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択