locked
SCCM 2012 SP1 and SQL 2008 R2 - let's make this as difficult as possible RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Have a multi-instance SQL 2008 R2 installation running on Windows 2008 R2.  I downloaded the SCCM 2012 with SP1 installation media from my Technet repository.  After initial run of SCCM pre-req checker, I was notified that I needed SQL 2008 R2 with SP1 and CU6 or *HIGHER*.  SQL 2008 R2 SP1 with CU6 is supposed to be version 10.50.2811.0 (per this article --> http://support.microsoft.com/kb/2679367 ).  Seeing that SP2 for SQL 2008 R2 is available (including 4 or 5 CU packages already), and believing that a pre-req checker would accept a *HIGHER* than required version, I downloaded and installed SP2, bringing my current SQL installations to version 10.50.4000.0.  Installation attempt with this version refused by the SCCM 2012 SP1 installation bits.  Downloaded the SQL 2008 R2 SP2 CU1 installer from the following article --> http://support.microsoft.com/kb/2720425 .  Attempted install, reports as failed, however my running version of SQL 2008 R2 SP2 now shows 10.50.4260.  Reference the following article ... http://support.microsoft.com/kb/2777963/en-us .  Umm, OK.  Rolled-up CU4, rebooted, all services started, now at 10.50.4276:

    SO ... what is *actually* required (SQL VERSION by NUMBER) to run and install the SCCM 2012 SP1 bits?  If there is a *maximum* supported version, is that documented anywhere?  Is SP2 for SQL 2008 R2 not actually inclusive of the updates from SP1 and all subsequent CU packages?  I'd really like to get this software deployed in my lab so I can work on learning it, but so far I've only been reminded of the labyrinth of pre-installation patching required for these products.


    • Edited by Levi Spears Monday, March 18, 2013 4:54 AM Missing content in original post
    Monday, March 18, 2013 4:50 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    At the end of this, moved to a dedicated Windows 2012 Server running a dedicated instance of SQL 2008 R2 SP2 and SCCM 2012 SP1.  Installation completed, system up and running, now clients cannot be installed (aside from the local site server).  Will post issues there in the appropriate forum.  @Jason - Thanks for the feedback on the installation process.
    • Proposed as answer by Garth JonesMVP Thursday, February 5, 2015 11:07 PM
    • Marked as answer by Garth JonesMVP Tuesday, October 27, 2015 5:00 PM
    Monday, March 25, 2013 4:02 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    What permissions do you have on the instance? You need to be a local administrator and sysadm. Also verify that the site server is local administrator on the SQL server. I have seen all kinds of strange errors if you or the site server do not have the correct permissions. 

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    Monday, March 18, 2013 5:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    My logon account is a local admin for the hosting server and sysadmin on the SQL Server.  Installer is run as administrator.  I see NT AUTHORITY\SYSTEM (SQL instance is running on the same host where I'm attempting to install SCCM) in the sysadmin role for the SQL instance / server.  As the SCCM system and SQL server are the same, I'd assume that I do not need to add the local system to the local administrators group.

    Monday, March 18, 2013 12:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Have you assigned a static port to your SQL Server named instance?
    Monday, March 18, 2013 1:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    SQL 2008 R2 SP 2 with no CU is supported and works.

    Some of your statements above are unclear though. Specifically, first you said "My logon account is a local admin for the hosting server and sysadmin on the SQL Server", then "Installer is run as administrator". Are you running the installer using your account and simply elevating it or are you running the installer using an account other than your own?

    Also, you mentioned this is a multi instance SQL Server. Why are you trying to install ConfigMgr on that same, multi-instanced server? That's not typically done even in a lab environment. During setup though, are you specifying the correct instance? Is that instance using a dynamic port? Have you reviewed the pre req checker log at the root of the C drive to make sure it is checking the correct instance. 

    Jason | http://blog.configmgrftw.com

    Monday, March 18, 2013 1:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    @Jason - thanks for the response:

    1) Static port 1434 assigned using SQL Configuration Manager, assigned to a single IP, following documented procedure (verified with netstat -an -p tcp -b).  Verified named instance listening on static port 1433 with same methods.

    2) I am logged onto the SQL 2008 server under a domain admin account that is therefore a member of the server local Administrators group.  Local Administrators group has the sysadmin role on the SQL server.  Running the SCCM installer using the "Run as Administrator" to elevate and avoid UAC issues.

    3) Multiple instances on SQL - the SQL server is running a named instance on a static port for Virtual Center (HOSTNAME\VC), the SCCM instance is intended for the default instance that is installed.  My other SQL Server system in the environment is a multi-instance host as well, running a mix of database services including Sharepoint.  I will review the pre-req log to ensure that the installer is talking to the appropriate instance.  I would expect that if the installation bits were finding the wrong instance, there would be an error indicating lack of support for named instances instead of a versioning error.

    4) My statement regarding the SQL 2008 R2 SP2 with no CU compatibility was based on the SCCM installation SQL checker failing with the above compatibility error at SQL 2008 R2 SP1 (expected), SP2, and SP2 CU4.

    Tuesday, March 19, 2013 2:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just to be clear, you are actually running the ConfigMgr setup on the same system hosting the DB for Virtual Center on which you've also spun up another SQL instance? Are you truly planning on making this your site server?

    1) Using 1434 for a SQL instance is generally not recommended because the SQL Browser listens on UDP 1434. I'm not sure if there would be an issue or not, but it's nothing I would ever do. Also, typically, default instances listen on 1433.

    2) Local Admins are not by default sysadmins in SQL Server so unless you explicitly added this, this is not true.

    3) ConfigMgr supports multiple instances no problem, but based on #1, I think you're throwing spitballs at it. Definitely check the log for more info. This still begs the question, why are you installing on system hosting a DB for a different application? Unless you have an explicit license of SQL Server, this violates the licensing for SQL Server for System Center.

    4) Without proper permissions, the pre-req checker can't actually check some of the pre-reqs so throws erros for things it simply can't check. Although, I still think it may be trying to connect to a different instance.

    Jason | http://blog.configmgrftw.com

    Tuesday, March 19, 2013 3:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, SCCM install being run on the same system - this is my TechNet lab environment in my home network, not for production use or for any customers or other users.

    1) Will review port utilization and probably adjust that - did not see a port in use (may have SQL browser disabled on the system, will verify)

    2) Realize that the local admins are not default sysadmins in SQL 2008 installations - this was selected during the SQL instance installation (for both the original named and subsequent default instances) at the point where I am allowed to define security groups or users other than the sa account as SQL sysadmins.  Explicitly added the local Administrators group, which contains the Domain Admins group for my environment.

    3) To the licensing question - again, am leveraging my Technet Professional subscription licenses for lab / training / pre-certification purposes, am the only user in the environment for all installed software.

    Based on the fact that I can log in and fully administer both SQL instances (configuration, database provisioning, security, backup / management plans, etc) with the account I am attempting installation of SCCM under, I do not think there are any permissions issues at hand.

    Thanks again for the feedback, I'm going to check logs this evening and will post further response.

    Tuesday, March 19, 2013 4:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    At the end of this, moved to a dedicated Windows 2012 Server running a dedicated instance of SQL 2008 R2 SP2 and SCCM 2012 SP1.  Installation completed, system up and running, now clients cannot be installed (aside from the local site server).  Will post issues there in the appropriate forum.  @Jason - Thanks for the feedback on the installation process.
    • Proposed as answer by Garth JonesMVP Thursday, February 5, 2015 11:07 PM
    • Marked as answer by Garth JonesMVP Tuesday, October 27, 2015 5:00 PM
    Monday, March 25, 2013 4:02 PM