Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Removing the SharePoint web service manually

 
* 
IMPORTANT: If you ran the automatic removal process and it failed, when you run the manual process there may be a timer job running that will prevent the manual process from completing successfully. If this scenario occurs, you need to delete the timer job and retry the manual process. See SharePoint web service removal fails.
To remove the SharePoint® web service manually
1
From the Manage SharePoint Farms and Sites box (see Managing SharePoint farms or sites), click Manual Web Service Deployment/Removal, and click Manual Web Service Removal.
2
Check that the two required SharePoint services are running on all of the web front end servers in your farm or site.
•
For SharePoint 2010, SharePoint 2010 Administration and SharePoint 2010 Timer must be running.
•
For SharePoint 2013, SharePoint 2016, and SharePoint 2019, SharePoint Administration and SharePoint Timer Service must be running
3
On the target web server where you copied the file in step two, open a command prompt, and execute two STSADM.exe commands: execute the retractsolution command, and execute the deletesolution command.
 
* 
NOTE: To run STSADM.exe commands, you must be logged in as a member of the local administrators group and must have sufficient rights to the various SharePoint databases.
NOTE: Click Removal Commands to open the SharePoint Web Service Commands page where you can copy and paste the commands. Be sure to select the correct version of SharePoint.
NOTE: Click More Information for a command that lists all of the SharePoint web service solutions present on your farm or site. See step three.
4
To verify that the removal process succeeded, you can run one more STSADM.exe command: enumsolutions. The output of the command indicates if the web service has been removed.
 
* 
NOTE: Click Verify Command to open the SharePoint Web Service Commands page where you can copy and paste the command.

 

Working with Access Explorer

To ensure network resources are secured in a manner that meets your business needs, you must be able to easily identify who has access to those resources and manage that access appropriately. With Access Explorer, you can quickly see who has access to specific resources (files, folders, and shares) and the explicit permissions associated with those resources. At any point in the exploration of an account, you can run reports on the available information.

* 
NOTE: The User Centric Security Management features provided by Security Explorer® appear as an Access Explorer node in the navigation tree on the Browse tab if the Access Explorer feature is installed and the license is enabled for Access Explorer. If installed, the Access Explorer menu options are present regardless of whether the license is enabled for Access Explorer.

Topics:

•
Access Explorer components
•
Setting up Access Explorer
•
Updating Access Explorer configuration
•
Collecting Access Explorer data
•
Viewing Access Explorer objects
•
Searching Access Explorer servers
•
Using the Access Explorer permission wizard
•
Setting options for Access Explorer

Access Explorer components

This section defines all of the components that comprise an Access Explorer deployment.

•
Managed domain
•
Registered forest
•
Managed computer
•
Access Explorer agent
•
Scopes
•
Database
•
Service accounts

Managed domain

To ensure that the Access Explorer service can install agents successfully, the Security Explorer® server needs domain user credentials with sufficient access. Access Explorer uses the concept of a managed domain, which is an association of service accounts (user credentials) to Active Directory® domains. When a new service account is added in the configuration, it is automatically granted the required Log On as a Service local user right on the Security Explorer server. This managed domain service account is used to install the agents. Local agents run as Local System and remote agents run as the service account specified during their installation.

 
* 
NOTE: Only domains that have a trust relationship with the Access Explorer service domain can be managed.
 

Once a domain is managed, the application creates a Service Connection Point (SCP) in the domain that provides server location information so that all agents and clients know where to connect.

For more information, see Adding managed domains.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation