Back to Blog
![]() AD-integrated authentication (Windows Authentication) is not supported.ģ. Only SQL Server authentication is supported for this operation by the Statistics Portal Server. To connect to the SQL configuration database, the SQL login must have at least the db_datareader role on the database. The account must be delegated Full Control rights in the project to connect to ADAM.Ģ. These accounts must have the following rights:ġ. When configuring the Statistics Portal, two accounts must be specified to connect to ADAM and SQL. Statistics Portal Accounts - Is used to retrieve statistical information from the ADAM project partition and the SQL configuration database. The Statistics Collection Agent service account can be changed on the Server page of the Statistics Collection Agent Properties dialog box. If SQL Authentication is used, the Statistics Collection Agent will use the SQL authentication credentials. ![]() If Windows Authentication is used while selecting the database for Migration Manager, the Statistics Collection Agent service account should have access to the SQL server.Ĥ. The account requires Log on as a Service rights on the server where the agent is installed.ģ. The account must be a member of the local Administrators group on the server where the agent is installed.Ģ. The Statistics Collection Agent account must have the following rights:ġ. Statistics Collection Agent - This account is used to start/run the Statistics Collection Agent service where the agent is installed. Migration Statistics Accounts and their minimal rights: NEW - Please see the attached (Below) PDF regarding the absolute Minimal Permissions required for Migration Manager for Exchange. NEW - Please see the attached (Below) PDF regarding the absolute Minimal Permissions required for Migration Manager for AD.Įxchange Data Migration accounts and minimal rights: The account's password must not expire or be changed during the migration.ĭirectory Synchronization & AD Migration accounts and minimal rights: This account must be considered to be the service account and must not be changed during the migration.Ĥ. This account can be any user account that is a member of the Domain Users group.ģ. The auxiliary account is an internal account that does not require any rights to either the source or the target domain and does not require any rights in Exchange. This account will then have the appropriate permissions to create/own and modify databases on a SQL server.Īuxiliary Account - This account is used by QMM to write to the ADAM partition.Ģ. The account requires the Database Creators role on the SQL server on which the SQL configuration database is created. SQL Configuration Database Account - This account manages the Exchange migration project information that is stored within the SQL Configuration database.ġ. These delegated users will only have rights within the ADAM project partition however, they will not have rights to manage the ADAM instance. The user who creates the project is automatically granted Full Control rights in the project and can later delegate rights within the project to other users. The account must be specified in the Open Project Wizard to connect to ADAM and create a new migration project (which also creates a new ADAM partition.) This is only done the first time Migration Manager is started.ģ. This account is granted Full Control rights over the ADAM instance when installed.Ģ. ![]() If there are cluster servers in the source or target Exchange Organizations, the Migration Manager account must be a member of the local Administrators group on each cluster node and have Full Control rights over the cluster.ĪDAM Administrative Account - The account specified when the ADAM instance is installed.ġ. Must be a member of the local Administrators group on the server.Ģ. Migration Manager Account - The account used to log on to the console machine.ġ. Migration Manager Console accounts and minimal rights: Storage Performance and Utilization Management. ![]()
0 Comments
Read More
Leave a Reply. |