none
sccm2010升级 RRS feed

  • 问题

  • 请问现有的环境中sccm2010升级至2012或以上怎么升级呢?升级的流程是怎样的?能否详细描述下呢?
    2019年2月18日 9:06

全部回复

  • 您好,

    没有 SCCM 2010。SCCM的命名规则如下:

    SMS -> SCCM 2007 -> SCCM 2012.....。请先确认当前的版本。

    https://www.systemcenterdudes.com/sccm-2012-version-numbers/

    上面的链接包含安装和升级文档,例如:

    SCCM 2012 R2 5.00.7958.1000 7958 N/A N/A Installation guide
    SCCM 2012 R2 - CU1 5.00.7958.1203 7958 N/A KB2938441 N/A
    SCCM 2012 R2 - CU2 5.00.7958.1303 7958 N/A KB2970177 Upgrade guide
    SCCM 2012 R2 - CU3 5.00.7958.1401 7958 N/A KB2994331 Upgrade guide
    SCCM 2012 R2 - CU4 5.00.7958.1501 7958 N/A KB3026739 Upgrade guide
    SCCM 2012 R2 - CU5 5.00.7958.1604 7958 N/A KB3054451 Upgrade guide


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    2019年2月18日 9:25
    版主
  • 是的,打错了,环境中是sccm2007,近期有项目需要升级到sccm2012的版本,又相关的实施文章可以参考不?具体是怎么升级的?需要注意的点有哪些?
    • 已编辑 MSTEO 2019年2月19日 1:47
    2019年2月19日 1:41
  • SCCM 2007 不可以直接升级到SCCM 2012. 可以把当前的数据,迁移到SCCM 2012上面。

    [Step-by-Step] Migrating SCCM 2007 to SCCM 2012

    https://win1337ist.wordpress.com/2012/12/31/step-by-step-migrating-sccm-2007-to-sccm-2012/

    Migrating Hierarchies in System Center 2012 Configuration Manager

    https://docs.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/gg682006(v%3dtechnet.10)

    SCCM ConfigMgr 2007 to SCCM 2012 Migration Reference Guide

    https://www.anoopcnair.com/sccm-configmgr-2007-to-2012-migration-reference-guide/

    SCCM 2012 在2017年已经不支持了。而且不支持最新的系统,比如Windows 10,Window server 2016

    https://support.microsoft.com/en-in/lifecycle/search?alpha=System%20Center%20Configuration%20Manager

    建议直接升级到 System Center Configuration Manager (Current Branch)

    Prerequisites for migration in System Center Configuration Manager

    https://docs.microsoft.com/en-us/sccm/core/migration/prerequisites-for-migration


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    2019年2月19日 6:03
    版主
  • System Center Configuration Manager (Current Branch)版本是哪个版本?sccm2007可以直接跨版本升级的吗

    我看了迁移文档,在现有的域环境中部署一套sccm2012,然后将sccm2007的配置迁移过去,是这样的吧?

    另外以下疑问:

    1.升级成功之后,客户端的agent不需要重新更新安装吧?2.自定义过的报表也可以迁移过去吗?


    • 已编辑 MSTEO 2019年2月20日 2:21
    2019年2月20日 2:12
  •  >>System Center Configuration Manager (Current Branch)版本是哪个版本?

    你看最上面那个关于版本的链接,SCCM 从 2012 R2 SP1 以后,使用跟Windows 10 同样的命名规则,用发布的年+月份,比如1511,1602。最新的是1810,就是18年10月发布的。

    >>sccm2007可以直接跨版本升级的吗?

    不可以,从2007到2012发生了很大变化,比如控制台的底层技术,层次结构的调整。只能迁移。
    >>我看了迁移文档,在现有的域环境中部署一套sccm2012,然后将sccm2007的配置迁移过去,是这样的吧?

    对。

    >>1.升级成功之后,客户端的agent不需要重新更新安装吧?

    需要重新指向新的站点,开启客户端自动安装就可以。

    >>2.自定义过的报表也可以迁移过去吗?

    SCCM 自带的工具,不支持迁移。

    找到一个三方工具,供你参考:

    Migrating Reports
    SCCM 2007 classic reports can't be migrated using the Microsoft Migration utility, but there's a helpful utility named ReportSync. You first need to migrate your SCCM 2007 reports into SSRS, then ReportSync can migrate those reports to SCCM 2012 and update their data source. Kent Agerlund's great blog post "Migrate reports from SCCM 2007 to SCCM 2012 SP1" contains step-by-step instructions as well as a link to the free ReportSync utility.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    2019年2月20日 2:47
    版主
  • 请问开启客户端自动安装在哪里设置的呢?迁移完之后重新指定新的站点,也就是说在现有的域环境中配置sccm2012的时候,输入的站点的名字不能与sccm2007的相同,对吗?

    另外,如果域环境是属于多站点的模式,sccm的架构采用多节点的模式管理可以吗,多节点管理是怎么的呢?比如主站点在广州,其余站点都承载分发点吗?,也就是说将sccm角色分开部署,能否分开部署的呢?能否说明下sccm的相关角色呢?




    • 已编辑 MSTEO 2019年2月20日 9:21
    2019年2月20日 6:58
  • https://enterinit.com/guide-configure-sccm-automatic-client-push-installation/

    建议使用主站点+分发点模式,除非超过10万台客户端。

    SCCM就是分布式系统,可以分开部署。

    Note:

    Central Administration Site

    • A central administration site can support up to 25 child primary sites
    • When you use SQL Server Enterprise or Datacenter for the site database at the central administration site, the shared database and hierarchy supports up to 400,000 clients
    • In most cases a CAS is not required. You only need a CAS if:
      • you REQUIRE more than one Primary Site
      • you have over 100,000 clients

    Primary Site
    • A stand-alone primary site always supports up to 100,000 clients
    • Each primary site management point can support up to 25,000 computer clients. To support 100,000 clients you must have at least four management points. Each primary site can support up to 10 management points
    • Each primary site can support up to 250 secondary sites

    Primary Site Server (local or remote SQL)
     
    • Microsoft support both scenarios and do not care where SQL is installed. However most ConfigMgr consultants will tell you to install SQL locally. You have more control and your solution will be less problematic.
    • Also the ConfigMgr Primary Site Server computer account must be local administrator and Sysadmin for the SQL instance. This is a hard sell for most DBAs in a shared SQL environment.
     
    Secondary Site
    • The number of secondary sites per primary site is based on continuously connected and reliable wide area network (WAN) connections. For locations that have fewer than 500 clients, consider a distribution point instead of a secondary site
    • Each secondary site supports a single management point that must be installed on the secondary site server.
    • Maximum number of clients in 5,000

    Distribution Point
    • Individually, each primary site supports up to 250 distribution points and each distribution point can support up to 4,000 clients.
    • Individually, each secondary site supports up to 250 distribution points and each distribution point can support up to the same number of clients as supported by the hardware configuration of the secondary site server, up to no more than 4,000 clients.
    • Each primary site supports a combined total of up to 5,000 distribution points. This total includes all the distribution points at the primary site and all distribution points that belong to the primary site’s child secondary sites.
    • Each distribution point supports a combined total of up to 10,000 packages and applications.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2019年2月21日 8:20
    版主