SCCM Setup Check Fails - Steve Thompson |
Wednesday, February 13, 2008 3:12 PM
|
Have you rebooted the server running SQL Server, since you added the site
server computer account to local admins?
Steve |
 |
SCCM Setup Check Fails - Steve Gould |
Wednesday, February 13, 2008 3:50 PM
|
I wish it were that easy. Yes, both the sccm site server and SQL server have
been rebooted. I have read others post the same issue, but have not seen any
fixes. |
 |
SCCM Setup Check Fails - Steve Thompson |
Thursday, February 14, 2008 7:45 AM
|
Does SQL Server have the default security set? IOW, does the local
administrators group have sysadmin permissions on SQL Server? |
 |
SCCM Setup Check Fails - Steve Gould |
Thursday, February 14, 2008 11:30 AM
|
Yes, the local administrators group has sysadmin permissions. |
 |
Resolved - Steve Gould |
Thursday, February 14, 2008 12:48 PM
|
I got so frustrated with this project that I went back to basics. I am
working with existing servers in a test forest. I found issues with DNS,
WINS, and lots of IP settings on the servers. After correcting the issues I
am now able to run the checks. I think it was DNS related.
Steve |
 |
Resolution Part 2 - Steve Gould |
Thursday, February 14, 2008 6:06 PM
|
My previous discovery didn't make enough difference. I was still unable to
install because the SMS Provider would fail.
My external SQL server runs under a domain service account. SPN's must be
set. The online references say to use the following:
setspn -A MSSQLSvc/<SQL Server computer name>:1433 <Domain\Account>.
setspn -A MSSQLSvc/<SQL Server computer name.domainname>:1433
These were incorrect. "MSSQLSvc" needs to be your actual SQL Server service
name. In my case "MSSQLSERVER". As soon as I altered the SPN's (using
ADSIEdit) I was able to complete the installation on the first server. |
 |