locked
Migrate from SCCM 2007 to SCCM 2012 RRS feed

  • Question

  • Dears,

    I am upgrading a single primary installed SCCM 2007 R3 to SCCM 2012 RTM

    SCCM 2012 will be installed on New Server (as primary server only), Database is hosted on CLustered SQL 2008 R2 (Which is hosting the SCCM 2007 Database)

    All Prerequirsites are Passed

    Everything is smoth, but Here is my big doubt:

    1- The Option: Upgrade an  eixsiting configuration manager 2012 installation cannot be selected in SCCM 2012 installation wizard, Is this wrong? or its just coz i do not have any SCCM 2012?

    2- In SCCM installation wizard > DataBase Information > Should I provide the Name of SCCM 2007 Database? or I have to give a new name?

    3- Do Prerequest Checker Notify if SQL CU is missed?

    • Edited by Jean M Thursday, April 19, 2012 6:14 AM
    Thursday, April 19, 2012 6:05 AM

Answers

  • That tab is just used for accepting the EULA, so you can safely check them.

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Jean M Monday, April 23, 2012 12:00 PM
    Thursday, April 19, 2012 7:45 AM
  • 2. It should be different Instance and different DB name as per your site code.


    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.


    • Edited by Anoop C NairMVP Thursday, April 19, 2012 6:36 AM
    • Marked as answer by Jean M Monday, April 23, 2012 11:59 AM
    Thursday, April 19, 2012 6:36 AM
  • #1: CM07 cannot be upgraded to CM12. It has to be a side-by-side migration.
    #2: No. You have to create a new database (see also #1)
    #3: See http://technet.microsoft.com/en-us/library/gg682077.aspx for the supported SQL versions/editions plus SP/CU levels.


    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Jean M Monday, April 23, 2012 11:59 AM
    Thursday, April 19, 2012 7:07 AM
  • 2. It should be different Instance and different DB name as per your site code.


    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.


    Thank you Anoop, for New Database, its okay, sound is fine.For different Instance! What is the reason? is there any article you gone through mentioned it?


    May be some pointers from the following thread : http://innovation.connect.microsoft.com/configmgrbeta/Thread/View.aspx?ThreadId=6284

    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    • Marked as answer by Jean M Monday, April 23, 2012 11:59 AM
    Thursday, April 19, 2012 7:10 AM
  • ConfigMgr 2012 requires SQL Server named instance to use static port TCP/1433, so you have to configure that from SQL Server Config Manager http://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1


    • Edited by Bechir Gharbi Thursday, April 19, 2012 9:23 AM
    • Marked as answer by Jean M Monday, April 23, 2012 12:00 PM
    Thursday, April 19, 2012 9:21 AM
  • Maybe the best way is to use SQL on SCCM 2012 for all SC products.

    I have some problems when I try to use SQL on other machine. After I put SQL on SCCM server everything is working fine. Now I have also SCOM connected to same machine and works fine (for now :))


    No that's not the best practice even if it is possible to use one SQL machine (and one instance for each) for more than one SC product. In plus, ConfigMgr 2012 can use a remote SQL box.

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1

    • Marked as answer by Jean M Monday, April 23, 2012 12:00 PM
    Saturday, April 21, 2012 8:01 AM
  • CM 2012 should work on a named instance that has a static port other than 1433 assigned to it; this is a (welcome) change from CM 2007.

    Assuming your CM 2007 installation is on port 1433, and the SSB port (as shown in the setup UI) is left at the default of 4022, those will be unavailable as instance ports.  If, for example, port 12345 is not in use, you could theoretically use it for your CM 2012 SQL instance.

    Details here (bottom of "Optional SQL Server Configurations" section, in "SQL Server Ports" block): SQL Server Requirements


    Monday, April 23, 2012 5:49 AM

All replies

  • 2. It should be different Instance and different DB name as per your site code.


    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.


    • Edited by Anoop C NairMVP Thursday, April 19, 2012 6:36 AM
    • Marked as answer by Jean M Monday, April 23, 2012 11:59 AM
    Thursday, April 19, 2012 6:36 AM
  • 2. It should be different Instance and different DB name as per your site code.


    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.


    Thank you Anoop, for New Database, its okay, sound is fine.For different Instance! What is the reason? is there any article you gone through mentioned it?

    Thursday, April 19, 2012 6:59 AM
  • #1: CM07 cannot be upgraded to CM12. It has to be a side-by-side migration.
    #2: No. You have to create a new database (see also #1)
    #3: See http://technet.microsoft.com/en-us/library/gg682077.aspx for the supported SQL versions/editions plus SP/CU levels.


    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Jean M Monday, April 23, 2012 11:59 AM
    Thursday, April 19, 2012 7:07 AM
  • 2. It should be different Instance and different DB name as per your site code.


    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.


    Thank you Anoop, for New Database, its okay, sound is fine.For different Instance! What is the reason? is there any article you gone through mentioned it?


    May be some pointers from the following thread : http://innovation.connect.microsoft.com/configmgrbeta/Thread/View.aspx?ThreadId=6284

    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    • Marked as answer by Jean M Monday, April 23, 2012 11:59 AM
    Thursday, April 19, 2012 7:10 AM
  • #1: CM07 cannot be upgraded to CM12. It has to be a side-by-side migration.
    #2: No. You have to create a new database (see also #1)
    #3: See http://technet.microsoft.com/en-us/library/gg682077.aspx for the supported SQL versions/editions plus SP/CU levels.


    Torsten Meringer | http://www.mssccmfaq.de

    Thank you Torsten, This is very useful.

    But Here I want to know onething, in SCCM 2012 RTM installation there are some options in Prerequisite licenses tab:

    Microsoft SQL Server 2008 R2 Exproess, Microsoft SQL Server 2008 Native Client, Micorosft Silverlight 4

    Since am going to use remote SQL Instance, so do i have to select: Microsoft SQL Server 2008 Native Client?

    Thursday, April 19, 2012 7:30 AM
  • That tab is just used for accepting the EULA, so you can safely check them.

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Jean M Monday, April 23, 2012 12:00 PM
    Thursday, April 19, 2012 7:45 AM
  • That tab is just used for accepting the EULA, so you can safely check them.

    Torsten Meringer | http://www.mssccmfaq.de

    I have Got a strange error, I tried to check for solution I could not find, my used account for setup SCCM is SCCMAdmin (Which is Local administrator on SQL Server, and the computer which am using is also local administrator on SQL Server)

    SCCMAdmin have a Privallage on named instance i have created on SQL Server (Instance name: SCCM2012), when I am trying to connect to it it giving the following error:

    ---------------------------

    Configuration Manager

    ---------------------------

    Setup is unable to connect to SQL Server with the connection information provided.  Verify the following:  . The SQL Server and instance names are entered correctly . The specified SQL Server instance is not configured to use dynamic ports . If a firewall is enabled on the SQL Server, inbound rules exist to allow connections to the correct ports . The account used to run Setup has permissions to connect to the specified SQL Server instance

    ---------------------------

    OK  

    ---------------------------

    I am sure that Firewall is off on SQL, and SCCMAdmin is local admin and having SYSADMIN and Server ADmin on SQL.

    as a test I run default instance (it was okay)

    Any suggestion?

    Thursday, April 19, 2012 9:16 AM
  • ConfigMgr 2012 requires SQL Server named instance to use static port TCP/1433, so you have to configure that from SQL Server Config Manager http://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1


    • Edited by Bechir Gharbi Thursday, April 19, 2012 9:23 AM
    • Marked as answer by Jean M Monday, April 23, 2012 12:00 PM
    Thursday, April 19, 2012 9:21 AM
  • ConfigMgr 2012 requires SQL Server named instance to use static port TCP/1433, so you have to configure that from SQL Server Config Manager http://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1


    Thanks alot Mr. Bechir

    Thursday, April 19, 2012 9:57 AM
  • Maybe the best way is to use SQL on SCCM 2012 for all SC products.

    I have some problems when I try to use SQL on other machine. After I put SQL on SCCM server everything is working fine. Now I have also SCOM connected to same machine and works fine (for now :))


    Best regards
    Dubravko Marak
    MCP
    Blog: Windows Server Administration
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, April 21, 2012 7:52 AM
  • Maybe the best way is to use SQL on SCCM 2012 for all SC products.

    I have some problems when I try to use SQL on other machine. After I put SQL on SCCM server everything is working fine. Now I have also SCOM connected to same machine and works fine (for now :))


    No that's not the best practice even if it is possible to use one SQL machine (and one instance for each) for more than one SC product. In plus, ConfigMgr 2012 can use a remote SQL box.

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1

    • Marked as answer by Jean M Monday, April 23, 2012 12:00 PM
    Saturday, April 21, 2012 8:01 AM
  • ConfigMgr 2012 requires SQL Server named instance to use static port TCP/1433, so you have to configure that from SQL Server Config Manager http://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1


    Dear Bechir,

    Today I have noted that my SCCM 2007 Lost the connectivity with SQL Database, I did some diagnostics and I found:

    1- Default SQL Instance was using the Port 1433 in SQL Configuration Manager. (Default instance is holding SCCM 2007 Database).

    2- When I configured Port 1433 for named Instance (named Instance for SCCM2012), the named SQL Service was not able to startup, For these, I modified the Default Instance port number to user 4022.

    3- It seems, that Since I configured Default instance to use 4022, my Configuration Manager 2007 lost connctivity.

    So, Here I have some doubts:

    1- is it better to configure Named instance with port 4022? and return the default instance to port 1433? "This instep to have SCCM 2007 connctivity to SQL Database".

    2- Is it okay to reconfigure SCCM 2012 to use Port Number 4022 using Configuration Manager Setup which located component in Start Menu?

    3- However, I went with Step 2, Default Instance Port is 1433 SCCM 2007 is working fine, BUT unfortunatily SCCM2012 Named Instance is stop working, I check the configuration from SQL Server Configuration Manager, I found that the last field of TCP/IP Properties /IP ADdress Tab (TCP PORT) is returining automaticlly to 1433, then its make the service to stop. "Each time i reconfigure it to use port 4022, then it work for 15 mints then stop again, and rechange the port to 1433.

    Here is snapshot:

    So what might I do?

    Sorry for being asking a long questions.

    Thanks



    • Edited by Jean M Sunday, April 22, 2012 7:15 AM add information
    Sunday, April 22, 2012 5:48 AM
  • Regarding answer from Bechir Gharbi, I know that this is not best practice.

    My first scenario was to install one server jusf or SQL and then install and connect all SC products to this server. But we faced many problems, similar as Jean M.

    Best security practice is to configure SQL not to use default ports.

    At the end I install SQL on SCCM machine (I've tried to install on SCOM machine but I have same problem as Jean M with connection), and my SCCM is working fine now

    Now I have connected second SC product to this SQL without any problem.

    So my suggestion is one from yesterday, try to install SQL on same server as SCCM

    :)


    Best regards
    Dubravko Marak
    MCP
    Blog: Windows Server Administration
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Sunday, April 22, 2012 9:58 AM
  • Regarding answer from Bechir Gharbi, I know that this is not best practice.

    My first scenario was to install one server jusf or SQL and then install and connect all SC products to this server. But we faced many problems, similar as Jean M.

    Best security practice is to configure SQL not to use default ports.

    At the end I install SQL on SCCM machine (I've tried to install on SCOM machine but I have same problem as Jean M with connection), and my SCCM is working fine now

    Now I have connected second SC product to this SQL without any problem.

    So my suggestion is one from yesterday, try to install SQL on same server as SCCM

    :)


    Best regards
    Dubravko Marak
    MCP
    Blog: Windows Server Administration
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Hi Dubravko,

    In My case I have centeral Clustered SQL, holding Several Instance for Serveral Application, It is not possible for me to install SQL server especialy for SCCM.

    For these end, I installed an Instance to support SCCM 2012 Requrirements.

    Currently coz of above mentioned Port Issue, I am not able to complete the migration, I wish Mr. Bechir, will be free soon to provide a suggestion.

    Finally thank you Dubravko for your suggestion

    Sunday, April 22, 2012 10:05 AM
  • Hi Dubravko,

    In My case I have centeral Clustered SQL, holding Several Instance for Serveral Application, It is not possible for me to install SQL server especialy for SCCM.

    For these end, I installed an Instance to support SCCM 2012 Requrirements.

    Currently coz of above mentioned Port Issue, I am not able to complete the migration, I wish Mr. Bechir, will be free soon to provide a suggestion.

    Finally thank you Dubravko for your suggestion

    I had similar situation, and I told you my final (worked solution)

    I have this SQL only for System Center products.

    I wish you good luck, and please when you resolve problem post it here on forum.


    Best regards
    Dubravko Marak
    MCP
    Blog: Windows Server Administration
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Sunday, April 22, 2012 10:08 AM
  • CM 2012 should work on a named instance that has a static port other than 1433 assigned to it; this is a (welcome) change from CM 2007.

    Assuming your CM 2007 installation is on port 1433, and the SSB port (as shown in the setup UI) is left at the default of 4022, those will be unavailable as instance ports.  If, for example, port 12345 is not in use, you could theoretically use it for your CM 2012 SQL instance.

    Details here (bottom of "Optional SQL Server Configurations" section, in "SQL Server Ports" block): SQL Server Requirements


    Monday, April 23, 2012 5:49 AM
  • As most of my friends have already answered the questions, am adding my answer for Q#3 which I think no body has answered specifically.

    Yes, Prerequisites checker notify if SQL CU is missed.

    Regards,
    Atul

    Wednesday, August 22, 2012 8:18 AM