systems administrator to ensure the account you log on with at each server has
appropriate permissions. Also, you must be a member of the Administrators
group on the local computer where you are installing a component.
The following permissions are implemented according to the principle of least
privilege, and the table lists permissions required in addition to administrator
access on the computer.
Component | Additional permissions required to install |
Database | Member of the dbcreator role on the SQL Server instance. |
Application Object Server (AOS) | Member of the securityadmin role on the SQL Server instance you want to connect to. |
Enterprise Portal | Member of the SYSADMIN role in Microsoft Dynamics AX and a member of the dbcreator role on the SQL Server instance being used for Microsoft SharePoint Services. |
Enterprise Search | Member of the SYSADMIN role in Microsoft Dynamics AX, a member of the Administrator group in Microsoft SharePoint Services, and a member of the dbcreator role on the SQL Server instance being used for Microsoft SharePoint Services. |
Help Server | Member of the SYSADMIN role in Microsoft Dynamics AX. |
Business Intelligence Components | Member of the SYSADMIN role in Microsoft Dynamics AX and a member of the SQL Serverdb_accessadmin role for the Microsoft Dynamics AX database. |
Client | None |
Office Add-Ins | None |
Debugger | None |
Visual Studio Tools | None |
Trace Parser | None |
AIF Web Services | Member of the SYSADMIN role in Microsoft Dynamics AX. |
.NET Business Connector | None |
Synchronization Proxy | Member of the dbowner database role on the SQL Server database for Microsoft Office Project Server, and a member of the Administrators group on the computer running Project Server. |
Synchronization Service | Member of the Administrators group in Microsoft Dynamics AX. |
Management Utility | None |
Regards,
Hossein Karimi
No comments:
Post a Comment