dimwit

Just so anyone getting the \boot\bcd error knows, this error can happen if you're working with real physical devices which at some point in their lifespan were Ghosted (or imaged using some similar imaging method) and as a result have the same GUID as other devices in the SCCM All Systems collection. A way around the issue is to power off a machine(s) having the problem(i.e. the machines with identical GUIDs), (make note of its GUID & MAC address before you do), delete the machine(s) from SCCM's All Systems collection, then manually re-add each device (which is why I suggest knowing its MAC address). And specifically if you're getting this error following anyweb's tutorial here on Build and Capture, you'll want to assign the device back to the build and capture collection once you done the aforementioned delete/manual re-add. Credit goes to http://adventuresinosd.blogspot.com/2011_03_01_archive.html (scroll down on that page)

I am having the exact same errors on trying to install SCCM that BewilderedAtTheMoment mentions in comment #11 on this thread. From reading his/her comments, I don't see mention of a solution. Did he/she correspond privately with you and do you happen to know a solution for the errors encountered in comment #11? I've read your subsequent questions/responses and all of my answers to those questions would be the same. All of my settings look right, but the prerequisites check throws the "SQL Server service running account", "Required SQL Server Collation" and "SQL server sysadmin rights" errors.

Thank you for the clarification. To make the walkthrough clearer for folks like me, might you want to show actually linking the GPO to the SCCM server? You're so good about giving detailed steps elsewhere...this how-to has been a godsend!

Apologies, I'm probably just missing something, but in Step 6 here and in an earlier walkthrough of installing SCCM, you describe making inbound rules for SQL traffic using a new Group Policy built on the domain controller. But to which computer(s) should this policy be applied/linked? The SQL/SCCM server? Or the AD server? And if it is the AD server, can you give a little explanation as to why the SQL ports need to be open on that machine? Thank you.