Sometimes in a corporate enviroment someone esle might set up SQL cluster for your SCCM and overlook the collation setting wich must be SQL_Latin1_General_CP1_CI_AS for SCCM. This is a workaround for this case assuming there is currently no database on your SQL instance.

1. Check server General settings and Master database General settings and confirm that collaction is wrong
2. Go to the active cluster node
3. Bring down SQL Server resource (Server and Agent only)
4. Start cmd.exe as Administrator
5. Go to SQL binn folder (you’ll find it from the SQL service start string)
6. Run command:

   sqlservr -m -T4022 -T3659 -s"<instance name>" -q"SQL_Latin1_General_CP1_CI_AS"

There will be a bunch of information messages and it should run for 2-8 minutes. After that it will display notification that it has successfully finished but it won’t exit the application. Wait for another minute, close cmd window, bring the resource up and check collation on the server and Master database.