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

MessageStats 7.8 - Administrator Guide

What is MessageStats? MessageStats Information Sources Using the Console Interface Creating a Connection to Exchange Creating Gathering Tasks Default Gatherings Extending Gathering Tasks Configuring Audits Setting MessageStats Server Properties Setting Configuration Properties Setting Exchange Organization Properties Setting Exchange Server Properties Setting Task Execution Server Properties Setting Task Default Properties Compressing Tracking Log Files Using the MessageStats Reports Console Database Management Appendix A:Microsoft ASP.NET Configuration Issues Appendix B: Gathering Task Dependencies Appendix C:Troubleshooting Permission Problems

MessageStats Reports Features

The following features are included in MessageStats Reports:

Using the console, you can perform the following tasks:

Setting Security for Reports

MessageStats Reports includes a flexible solution for report security which allows you to assign certain permissions to users, and enable different views of the reporting tree depending on user needs and security requirements.

MessageStats Reports supports two types of security:

Role-based Security

Role-based security provides an initial layer of security for your reports. Three local security groups, each with specific permissions, are created when MessageStats Reports is installed:

All three security groups have access to the report site and to all reports. The roles (Administrator, Author, User) provide different permissions that can restrict the ways reports can be manipulated.

The default membership to these security groups places administrators in the Web Report Administrator role, and all others in both the Web Report Authors and Web Report Users roles.

To customize the memberships, you can add or remove users from the default groups. Administrators can specify which users belong to which roles by modifying their membership in these local groups. The role-based security scheme is easier to manage than the file-system permissions security scheme, as the changes to these security groups immediately affect all reports.

Accessing the site

Exporting reports

Saving report settings in My Reports folder

Saving report settings in any folder

 

 

Creating Custom Reports

 

Saving Custom Reports in My Reports folder

 

Saving Custom Reports in any folder

 

 

Creating new folders in My Reports folder

Creating new folders in any folder

 

 

Copy folders or report within My Reports folder

Copy folders or reports to and within My Reports folder

 

Copy folders or reports to and within any folder

 

 

Move folders or reports within My Reports folder

Move folders or reports from any folder to My Reports folder

 

 

Move folder to and within any folder

 

 

Rename folders or reports in My Reports folder

Rename folders or report in any folder

 

 

Delete folders or reports in My Reports folder

Delete folders or reports in any folder

 

 

Edit folder descriptions in My Reports folder

Edit folder descriptions in any folder

 

 

Enable subscriptions for reports in My Reports folder

Enable subscriptions for reports in any folder

Set Filter Defaults

File-System Based Security

In addition to the Web Report security roles, you can enable an additional level of security using a file permissions-based scheme. At a minimum, the role-based security scheme allows all roles to view all reports.

Alternately, a permission-based scheme can restrict the reports to be available to some users. Explicit permissions are applied on a per-group or per-user basis, and assigned to individual files, folders, and reports. You can configure the settings so that different groups, such as executive management, the help desk, and Exchange administrators can see different report nodes and reports.

System administrators can create more sophisticated security schemes by modifying the file permissions for reports and folders in the file system on the web server. By default, report files and folders reside in the following location:

By restricting the reports that are available to all users, you can protect sensitive data from users that do not require that information. Users connecting through a web browser can only see report files and folders for which they have read access permissions, and folders for which they have list permissions in the file system.

Permission-based security provides more detailed control than role-based security, but it requires some action on an administrator’s part. MessageStats does not provide the functionality to manipulate the permissions on files and folders. Use native Microsoft tools to create the appropriate Windows NT File System (NTFS) security changes.

Refer to Microsoft Windows native tools procedures for detailed information about implementing NTFS security scenarios. For information about determining an appropriate security scheme for your implementation, contact Quest Support.

Restricting access to standard report folders

Using native Microsoft Windows tools, remove the Web Reports Administrators, Authors, and Users roles from the folder you want to restrict.

Create new security groups and add the appropriate members to those groups.

Add your newly-created security groups and their access rights to the report folder you want to restrict.

Restricting access to newly-created report folders

Using native Microsoft Windows tools, remove the Web Reports Administrators, Authors, and Users roles from the folder you want to restrict.

Create new security groups and add the appropriate members to those groups.

Add your newly-created security groups and their access rights to the report folder you want to restrict.

Restricting access to individual standard reports

Using native Microsoft Windows tools, remove the Web Reports Administrators, Authors, and Users roles from the report you want to restrict.

Create new security groups and add the appropriate members to those groups.

Add your newly-created security groups and their access rights to the report you want to restrict.

Restricting access to individual Custom Reports

Using native Microsoft Windows tools, remove the Web Reports Administrators, Authors, and Users roles from the report you want to restrict.

Create new security groups and add the appropriate members to those groups.

Add your newly-created security groups and their access rights to the report you want to restrict.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation