SQL 2008 – Is it supported on System Center Configuration Manager 2007?


 

 

 

 

 

Our live event content this quarter includes System Center Configuration Manager 2007 and this has been a common question: “Is SQL 2008 supported as a site database?”

The Answer

Absolutely!!!!!    SQL Server 2008 is now supported on Configuration Manager 2007 RTM and SP1!

 

What Do I need to do to the Site Server?

In order to upgrade a site-server database to SQL 2008 you must first apply a hotfix.  Which one depends on what version of System Center Configuration Manager 2007 you’re running:

 

What if its a clean install of System Center Configuration Manager 2007 ?

That’s a little more complicated.  If you’re performing a clean install of SCCM using a SQL Server 2008 database, depending on whether is RTM or SP1, you will have to do the following steps:

Clean install of System Center Configuration Manager 2007 RTM:
    • NOT SUPPORTED
      1. First, install SQL Server 2005
      2. Upgrade to SQL Server 2008
      3. Apply hot fix KB955229
Clean install of System Center Configuration Manager 2007 SP1:
    • SUPPORTED
      1. Apply hot fix KB955262
Comments (8)

  1. SCOM 2007 – SQL Server 2005 Standard or Enterprise Edition with Service Pack 1 or Service Pack 2

    SCE 2007 – SQL Server 2005 (SP2 required for running on Windows Server 2008)

  2. You might want to check this KB article, http://support.microsoft.com/kb/949104, or place a support call on this.

  3. Sergey Shaykin says:

    What about SCOM and SCE support?

  4. jordah ferguson says:

    I have problems installing sccm 2007…

    here is the snippet of the log file…please advise asap.

    <03-06-2009 14:54:07> File hash check failed for F:ENGLISHSYSTEMCENTERCONFIGURATIONMANAGER2007SMSSETUPClientx64WindowsUpdateAgent30-x64.exe

    <03-06-2009 14:54:07> Checking alternate path: C:sccmsp0WindowsUpdateAgent30-x64.exe

    <03-06-2009 14:54:07> Verifying hash for file ‘C:sccmsp0WindowsUpdateAgent30-x64.exe’

    <03-06-2009 14:54:10> File hash check failed for C:sccmsp0WindowsUpdateAgent30-x64.exe

    <03-06-2009 14:54:10> Failed to find valid source for required external file

    <03-06-2009 14:54:10> Unable to find valid source for required file ‘WindowsUpdateAgent30-x64.exe’. Aborting setup.

    <03-06-2009 14:54:10> Setup has encountered fatal errors while performing file operations.

  5. jordah ferguson says:

    I have downloaded that file about 5 times and still get the same error. It seems the hash checks fail all the time.

    also, i have an x86 system, dnt really know why i need this file. anyway, is there any one who has actually passed this part. if so how?

    i have tried installing sccm 2007 sp1, i reach the same place…

    i have searched the net to no avail….please help me as im running out of time

  6. jordah ferguson says:

    Hi everyone,

      i have successfully installed sccm 2007 and its server roles. i have 1 computer connected on my domain but i cannot find it. its is already joined on my domain and shows up in the active directory users and computers console.

    when i go to discover it using all the discovery methods i fail. it only shows the site server. is it me or is there a fix. my boss doesn’t recomment network discovery bt i still tried it but to no avail.

    shd i just force it with computer associations or what?

  7. jordah ferguson says:

    HI everyone,

     I posted yersterday, but it hasn’t shown up yet.

    i was asking about discovery on sccm. i have enabled all the discovery methods but i cannot see a client on my collections list. i have extended my ad schema but to no avail. i really dnt kno what im doing wrong….please shade some light

  8. jordah ferguson says:

    i solved this problem by going to tools tree node just under system rights, and started the configMgr services. It opened a console inwhich i queried and started the discovery services.

    it worked like a charm…

    now, im having issues with client push installation. i have a snippet of the ccm.log file and want to know what im doing wrong

    ======>Begin Processing request: "CGFWZADB", machine name: "STN1" SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

    —> Trying the ‘best-shot’ account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

    —> Attempting to connect to administrative share ‘\STN1admin$’ using account ‘jordahadministrator’ SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

    —> The ‘best-shot’ account has now succeeded 1 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

    —> Connected to administrative share on machine STN1 using account ‘jordahadministrator’ SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

    —> Attempting to make IPC connection to share <\STN1IPC$> SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

    —> Searching for SMSClientInstall.* under ‘\STN1admin$’ SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:23 AM 6532 (0x1984)

    Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:25 AM 4820 (0x12D4)

    Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:25 AM 4820 (0x12D4)

    Waiting for change in directory "C:Program FilesMicrosoft Configuration Managerinboxesccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:25 AM 4820 (0x12D4)

    CCR count in queue "Retry" is 3. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:37 AM 4672 (0x1240)

    Sleeping for 634 seconds… SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:37 AM 4672 (0x1240)

    —> System OS version string "5.2.3790" converted to 5.20 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:50 AM 6532 (0x1984)

    —> Service Pack version from machine "STN1" is 2 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:47:50 AM 6532 (0x1984)

    CWmi::Connect(): ConnectServer(Namespace) failed. – 0x8004100e SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:01 AM 6532 (0x1984)

    —> Unable to connect to WMI (r) on remote machine "STN1", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:01 AM 6532 (0x1984)

    —> Creating VerifyingCopying exsistance of destination directory \STN1admin$system32ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:01 AM 6532 (0x1984)

    —> Copying client files to \STN1admin$system32ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:02 AM 6532 (0x1984)

    —> Updated service "ccmsetup" on machine "STN1". SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:02 AM 6532 (0x1984)

    —> ERROR: Unable to start service "ccmsetup" on machine "STN1", error = 1053. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

    —> Failed to install CCM Client Bootstrap component on client (1053) SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

    —> Deleting SMS Client Install Lock File ‘\STN1admin$SMSClientInstall.JFS’ SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

    Retry request id for "CGFWZADB" set to "STN1" SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

    Stored request "STN1", machine name "STN1", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

    <======End request: "STN1", machine name: "STN1". SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:48:34 AM 6532 (0x1984)

    Waking up for site control file directory change notification SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Default MP: JORDAH-SRV SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    SSL State: 0 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Certificate Store: SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Select First Certificate: 0 SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Checking configuration information for server: JORDAH-SRV. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Checking configuration information for server: JORDAH-SRV. SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Fallback Status Point: jordah-srv.jordah.net SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Install on DC: True SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:22 AM 4672 (0x1240)

    Sleeping for 1200 seconds… SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:55:24 AM 4672 (0x1240)

    Thread has been inactive too long. Closing thread SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:56:15 AM 6436 (0x1924)

    — This thread is terminating due to inactivity SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:56:15 AM 6436 (0x1924)

    —– Terminated CCR processing thread. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 3/17/2009 8:56:15 AM 6436 (0x1924)