mkilpatric

For those who have been following this topic and never really found the answer (or those who just ran across it while looking for the answer): 1. Ensure that you have created a group in AD for SCCM that includes the machine, and then add it to SQL servers local administrators group. You CAN do this method of security, or a multitude of other steps, you pick. But the answers below are specific to my way, sorry. 2. Add the SQL Server login that will associate with the group name you used. 3. Associate the serveradmin, sysdmin, and public roles (again, if you aren't a DBA, you will just accept these and move on sir.) 4. Run your pre-req checks again (also note, the group you created with the accounts? Ya, add it to your SCCM server as well). And voila, you will pass the machine is not a member error. Now, do this in your lab all day long, but make SURE you are performing the most secure setup possible per the deployment guide, as well as ensuring that all of your SCCM accounts don't have permissions all over the place.