Warehouse SQL Server Authentication Account. Instead, create your own account and your own Run As Account and make the Run As Account a member of the Run As Profile, Data Warehouse SQL Server Authentication Account when configuring SQL Server Authentication. The following outlines the relationship of the various account credentials, Run As Accounts, and Run As Profiles for both Windows Integrated Authentication and SQL Server Authentication. Default: Windows Integrated Authentication Run As Profile: Data Warehouse Account Run As Account: Data Warehouse Action Account Credentials: Data Writer Account (specified during setup) Run As Profile: Data Warehouse SQL Server Authentication Account Run As Account: Data Warehouse SQL Server Authentication Account Credentials: Special account created by Operations Manager (do not change) Optional: SQL Server Authentication Run As Profile: Data Warehouse SQL Server Authentication Account Run As Account: A Run As Account you create. Credentials: An account you create. The System Center Data Access Service and Reporting Data Warehouse By default, the System Center Data Access service, which is responsible for reading data from the Reporting data warehouse and making it available in the Report Parameter Area, achieves Windows Integrated Authentication by running as the Data Access Service and Config Service account that was defined during setup of Operations Manager. If the Reporting data warehouse and the management server are separated by a boundary (for example, each resides in different domains with no trust), then Windows Integrated Authentication would not work. To work around this situation, the System Center Data Access service can connect to the Reporting data warehouse using SQL Server Authentication. To do this, create a new Run As Account (of Simple Account type) with the SQL account credential and make it a member of the Run As Profile called Reporting SDK SQL Server Authentication Account with the management server as the target computer. Important By default, the Run As Profile, Reporting SDK SQL Server Authentication Account was assigned a special account through the use of the Run As Account of the same name. Never make any changes to the account that is associated with the Run As Profile, Reporting SDK SQL Server Authentication Account. Instead, create your own account and your own Run As Account, and make the Run As Account a member of the Run As Profile, Reporting SDK SQL Server Authentication Account when configuring SQL Server Authentication.
Warehouse SQL Server Authentication Account. Instead, create your own account and your own Run As Account and make the Run As Account a member of the Run As Profile, Data Warehouse SQL Server Authentication Account when configuring SQL Server Authentication. The following outlines the relationship of the various account credentials, Run As Accounts, and Run As Profiles for both Windows Integrated Authentication and SQL Server Authentication. Default: Windows Integrated Authentication Run As Profile: Data Warehouse Account Run As Account: Data Warehouse Action Account Credentials: Data Writer Account (specified during setup) Run As Profile: Data Warehouse SQL Server Authentication Account Run As Account: Data Warehouse SQL Server Authentication Account Credentials: Special account created by Operations Manager (do not change) Optional: SQL Server Authentication Run As Profile: Data Warehouse SQL Server Authentication Account Run As Account: A Run As Account you create. Credentials: An account you create. The System Center Data Access Service and Reporting Data Warehouse By default, the System Center Data Access service, which is responsible for reading data from the Reporting data warehouse and making it available in the Report Parameter Area, achieves Windows Integrated Authentication by running as the Data Access Service and Config Service account that was defined during setup of Operations Manager. If the Reporting data warehouse and the management server are separated by a boundary (for example, each resides in different domains with no trust), then Windows Integrated Authentication would not work. To work around this situation, the System Center Data Access service can connect to the Reporting data warehouse using SQL Server Authentication. To do this, create a new Run As Account (of Simple Account type) with the SQL account credential and make it a member of the Run As Profile called Reporting SDK SQL Server Authentication Account with the management server as the target computer. Important By default, the Run As Profile, Reporting SDK SQL Server Authentication Account was assigned a special account through the use of the Run As Account of the same name. Never make any changes to the account that is associated with the Run As Profile, Reporting SDK SQL Server Authentication Account. Instead, create your own account and your own Run As Account, and make the Run As Account a member of the Run As Profile, Reporting SDK SQL Server Authentication Account when configuring SQL Server Authentication.
SC2012_OpsMgr_Deployment.docx