Pour les professionnels de l’informatique >
Forums - Accueil
>
Configuration Manager General
>
Prerequisite failure
Prerequisite failure
- Hello,
When I run the prereq and specify the remote SQL 2005, it fails with,
"<06-25-2009 18:07:22> <<<CategoryDesc: Checking access permissions...>>>
<06-25-2009 18:07:22> Rule Name: SQL Server sysadmin rights
<06-25-2009 18:07:22> Result: Passed
<06-25-2009 18:07:22> Rule Name: Site server computer account administrative rights
<06-25-2009 18:07:30> Result: Error
<06-25-2009 18:07:30> Configuration Manager Setup requires that site server computer possess administrative rights on the SQL Server and management point computers."
The server that's to be SCCM 2007 is a member of the local admins group on the remote SQL 2005 server and I'm running the prereq as a domain admin.
I can access the admin share on the remote SQL 2005 from to be SCCM 2007 server just fine.
It seems to be complaining about the site server computer account though.- Modifiésccmstud mardi 30 juin 2009 01:10
Réponses
- Sorry guys...,
It was a DNS issue.
Thanks for all your help!- Marqué comme réponseYvette OMeallyMSFT, Propriétairemardi 7 juillet 2009 20:26
Toutes les réponses
This is a complete guess but after you add the computer account to local admins should tbe SQL box be rebooted before the permissions work?
John Marcum, Systems Management Consultant - www.TrueSec.com- Hello,
With what kind of authentication is the SQL Server installed. I believe it should me in Windows Authentication mode to make it work. If in SQL authentication mode this might happen as then even the local admin group has no permissions.
Robert - see this:
http://technet.microsoft.com/en-us/library/bb693554.aspx
and this
http://technet.microsoft.com/en-us/library/bb680310.aspx
John Marcum, Systems Management Consultant - www.TrueSec.com - I still get the same error during the prereq installation check. I select "Primary" and enter the netbios name of the remote SQL server and for the management point, I enter in the name of the SCCM server.
I checked the SPN of the SQL and the article but I haven't found anything odd.
Our remote SQL 2005 (default instance) is running a mixed mode and the SQL server service is started using System account.
The SCCM server is a member of the local administrators group on the remote SQL server and the SCCM server itself.
I'm running the prereq under a domain admin account so it has admin rights on the remote SQL server.
Any other suggestions? - What about the firewall on the ConfigMgr site server?
http://myitforum.com/cs2/blogs/jsandys/archive/2008/11/15/configmgr-prerequisite-checker.aspx
Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys - And you met this requirement?
If the user account running Configuration Manager Setup does not have administrative rights on the remote SQL Server, you must assign the sysadmin SQL Server role to the user account in the SQL Server 2005 Management Studio console on the remote SQL Server computer.
John Marcum, Systems Management Consultant - www.TrueSec.com - The firewall isn't on on the remote SQL or the SCCM server.
The account running the configuration manager setup is a domain admin account and is a member of a builtin administrators group on the remote SQL server which in turn is a member of the sysadmin SQL server group.
I even added the domain admin to the sysadmin SQL server group maually but still get the same error.
When running the prereq installation check, I selected "primary" as this is the only SCCM and entered the netbios name of the remote SQL server and for the management point, I entered in the name of the SCCM server.
Is this correct? When I select the "secondary", the prereq completes successfully. - I know you mentioned this is the initial post, but can you please double-check the permissions of the ConfigMgr server itself on the SQL server? Is the server's AD account a member of the local admins group on the SQL Server and a sysadmin in SQL itself?
Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys - I would call PSS at this point.
John Marcum, Systems Management Consultant - www.TrueSec.com - Sorry guys...,
It was a DNS issue.
Thanks for all your help!- Marqué comme réponseYvette OMeallyMSFT, Propriétairemardi 7 juillet 2009 20:26
