Chatee ahora con Soporte
Chat con el soporte

Security Explorer 9.8.1 - 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

Repairing inheritance

You may need to repair the inheritance on folders and files because some or all subfolders and files are not inheriting permissions correctly from their parent. Incorrect inheritance can include missing permissions, such as a subfolder missing an inherited permission from the parent, and unwanted extra permissions, such as a subfolder containing an extra inherited permission that is not present on the parent.

 
* 
IMPORTANT: Repairing inheritance changes the permissions on the selected folders, subfolders, and files. Review the selected folders to verify that important permissions are not removed during the process.
NOTE: The Repair Inheritance function is available only in the NTFS Security module.
TIP: You also can use the Repair Security advanced task to repair multiple folders.
To repair inheritance
1
Open the NTFS Security module.
2
In the Navigation pane, select a folder, and select Security | Repair Inheritance.
-OR-
Click on the Tool Bar.
3
Click Yes. See Completing a process.

Creating test folders and files

To help you evaluate or troubleshoot issues, you can create a test folder that contains files and permissions.

To create test folders and files
1
Open the NTFS Security module.
2
Select Help | Create Test Folders and Files.
3
In the Starting Folder box, type the path to where you want to place the test folder, or browse to designate a location.
4
Click Create Evaluation Folders and Files. A message box appears asking if you want to apply a standard set of permissions to the folders and files.
5
To apply permissions, click Yes.
The securityexplorer.try folder appears in the location you designated. If you chose to apply permissions, those display in the Permissions pane.

Using log files

By default, there is one log file written to the Security Explorer installation directory. To get more log information, run Security Explorer.exe with /d key to write two log files to the installation directory.

C:\Program Files\Quest\Security Explorer\SecurityExplorer.exe /d

For the Exchange Security module, the ExchangeAccess log files contain Exchange module log data.

Because Security Explorer is digitally signed, you may see event log entries when starting Security Explorer if the Update Root Certificates component is turned on and the computer cannot connect to the Windows® Update server on the Internet. The Update Root Certificates component automatically updates trusted root-certificate authorities from the Microsoft Update server at regular intervals.

To resolve this behavior, connect to the Internet, or turn off the Update Root Certificates component.

To turn off the Update Root Certificates component
1
In Control Panel, double-click Add/Remove Programs.
2
Click Add/Remove Windows Components.
3
Clear the Update Root Certificates check box, and continue with the Windows Components Wizard.

SharePoint web service removal fails

If you find that you are unable to remove the SharePoint® Web Service and try the manual process, the manual process may fail because a timer job is still in process.

To delete the timer job and remove the SharePoint web service
1
On one of the servers in the SharePoint farm. run the command stsadm.exe –o enumsolutions.
To view the command
a
Open the SharePoint Security module.
b
Select SharePoint | Manage SharePoint Farms and Sites.
c
Click Manual Web Service Deployment/Removal.
d
Click Manual Web Service Removal.
e
Click Verify Command to open the SharePoint Web Service Commands page where you can copy and paste the command.
2
Examine the output.
•
If the output does not show a solution name SLWebServices_1.00.0009.wsp (or similar), then the web service is uninstalled and no further action is required.
•
If the output does show a solution name SLWebServices_1.00.0009.wsp (or similar) then the web service is still installed. The Deployed flag will probably display FALSE.
3
Try to remove the solution manually by running two commands in sequence.
a
Execute the stsadm.exe –o retractsolution –name SLWebServices_1.00.0009.wsp command. You may need to wait a few moments before running the second command to allow the retraction to finish.
b
Execute the stsadm.exe -o deletesolution -name SLWebServices_1.00.0009.wsp command.
To view the commands
a
Select SharePoint | Manage SharePoint Farms and Sites.
b
Click Manual Web Service Deployment/Removal.
c
Click Manual Web Service Removal.
d
Click Removal Commands to open the SharePoint Web Service Commands page where you can copy and paste the commands.
4
Examine the output.
•
If these commands succeed, the web service is uninstalled and no further action is required. You can confirm the uninstall by running the stsadm.exe –o enumsolutions command again.
•
If this command does not succeed, the output will mention that a retraction is already in process. This is the timer job that you need to remove.
5
To remove the timer job, browse to the central administration console and delete the timer job (Central Administration | Operations | Timer Job Definitions).
6
After the timer job is removed, retry the retractsolution and deletesolution commands in step 2. This time the commands should succeed.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación