Search This Blog

Saturday, December 2, 2017

Reccomendations / Best practices when putting SCCM Current Branch database on remote cluster

fdsfdsf

If you decide to put your SCCM DB on a remote SQL cluster instead of locally (which is a best practice) then follow these recommendations


  1. SQL instance and database collation must be SQL_Latin1_General_CP1_CI_AS
  2. No other SCCM site databases are on this SQL instance. SQL instance could be default or named.
  3. The use of dynamic ports on SQL instance is not supported
  4. SQL service user must have registered SQL service SPN
  5. SCCM server account must be local administrator on all SQL cluster nodes
  6. When installing SCCM or moving DB to remote cluster the user account performing the actions should have local administrator rights on SQL server nodes and sysadmin rights on SQL instance. After installation these rights can be removed.
  7. On all shared disks on SQL cluster put no_sms_on_drive.sms file which will disallow creating SCCM files on these disks. SCCM SQL backup service creates files on SQL cluster, so you need to control where these files are installed - they should be on same drive on all cluster nodes, otherwise SCCM backups will fail.
  8. Change Reporting Service DB recovery mode from Full to Simple.
  9. Use SCCM backup task for backup and put it onto share, where other backup solution backs it up.
  10. All SQL requirements from Microsoft are here https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-sql-server-versions

No comments:

Post a Comment