Converse agora com nosso suporte
Chat com o suporte

MessageStats 7.8 - Deployment Guide

MessageStats Architecture Overview Planning for Deployment Deployment Recommendations and Solutions

2. Enable delegation from the Reports Server to the Database Server.

The AD account used by the Web Reports application pool in IIS must be enabled for delegation to the MSSQLSvc SPN of the MessageStats database SQL server.  MessageStats creates the Web Reports application pool to "run as" NetworkService.  Consequently, you must enable the report server's AD account for delegation to the MSSQLSvc SPN.

2
Select the Delegation tab.
3
Select Trust this computer for delegation to any service to enable delegation from the server AD account to any SPN.
Select Trust this computer for delegation to specified services only to add the MSSQLSvc SPN the list of specified services.
a
Click Add.
b
5
Click OK to save.

Once you have completed steps 1 and 2, you must either wait for Active Directory replication or you can manually force replication between all the domain controllers.

3. Specify Windows authentication in the QMSReports.udl file.

Now you must edit QMSReports.udl file located in MessageStats installation folder and ensure that Windows NT integrated security is used to log onto the MesssageStats database.

2
Double-click the QMSReports.udl file.
3
Select the Connection tab.
4
Ensure that Windows NT authentication is selected.

4. Enable IIS Settings and Restart IIS.

For MessageStats report servers that are hosted by Windows 2012 and later, you must ensure specific IIS settings are enabled under Authentication and that the applicationHost.config file is updated. For all Windows server versions, you must reset IIS by performing an iisreset.

1
In the Internet Information Services (IIS) Manager, select Sites | Default Web Site | MessageStats Reports.

Perform an iisreset on the MessageStats reports server to ensure that IIS uses the updated delegation and QMSReport.UDL settings.

Deploying MessageStats Across Forests

MessageStats can be used in cross-forest scenarios to gather information from an Exchange organization that resides in a different forest by using an alternate account from the external forest and establishing a trust relationship.

The following steps must be completed to use MessageStats to gather information from an Exchange organization in an external forest.

In the following scenario, Domain A has MessageStats installed. Domain B holds the alternate account you want to use to connect to the second organization.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação