So shortly after starting my current roll, my first task was automation of patching. I decided to accomplish this with System Center Configuration Manager. My work gave me a single server and a SQL cluster we used for several other applications. I did the obvious thing and tried to utilize the SQL cluster for the SCCM SQL requirement. For my first attempt at installing on the SQL cluster, I let SCCM create it’s own databases (DB’s). It successfully connected, created the base DB’s but failed when trying to determine the drive locations of the DB. I thought this odd but shrugged it off. I attempted again but this time manually created the DB’s. Still failed. After spending days researching, opening tickets with Microsoft Support, etc, I finally found this Technet post: Technet post. It turns out our deployment of SQL was using clustered shared volumes and SCCM won’t work with them. So, if you hopefully find this when Googling SCCM, SQL Cluster, Cluster Shared Volumes, etc, then hopefully I will save you the headache of attempting to install SQL on a cluster. Just build/use a standalone SQL server or a different cluster.