Depending on the level of security applied in your environment, you might not be able to complete the setup program or run Analysis Center. If your environment is FIPS-encryption-enabled or just highly secured, try the following security configurations:
To run the setup program, use the domain account that will be used as the Reporting Center service account.
When launching the installation package, use the Run as Administrator command.
Instead of running the setup program using Remote Desktop Protocol (RDP), use console session 0 mode.
If necessary, temporarily disable the FIPS encryption policy setting during installation only.
Add the Reporting Center service account to the local security policy settings for Impersonation and delegation.
Add the following user rights to the Reporting Center service account:
Enable computer and user accounts to be trusted for delegation
Impersonate a client after authentication
Configure the SQL Server service account to use the Reporting Center service account.
If necessary, temporarily disable UAC for the Reporting Center service account during installation.
Verify the IIS_IUSRS group permissions on the Reporting Center, IIS, and ASP.NET directories.
Verify the Components Services (dcomcnfg) MSDTC security configurations, and enable them for network access.
Enable the SQL Server Browser Service on servers where Reporting Center components will be hosted.
Where the Windows Firewall is enabled, add explicit exceptions for IIS, SQL, Analysis Services, MSDTC, and Integration Services, where appropriate.
Where the Windows Firewall is enabled, add explicit exceptions for the NetIQ Reporting Console (NRConsole.exe) after Reporting Center has been installed successfully.