Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Support the windows server OS being upgraded on Site Servers (in place), w/o backup & recovery or migration.

Older version of windows server are falling out of support, or are deprecated for ConfigMgr current branch. i.e. Windows Server 2008 and 2008 R2. Support an easy way of upgrading those operating systems to newer versions of windows server.

77 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Admindjam (Product Director, or Executive, System Center Configuration Manager) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

9 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Caroline commented  ·   ·  Flag as inappropriate

    Definitely agree with what has been said below:

    Windows Server 2008 R2 -> Windows Server 2012 R2
    Windows Server 2012 R2 -> Windows Server 2016

  • Cristopher commented  ·   ·  Flag as inappropriate

    2008R2 --> 2012R2 and/or 2008R2 --> 2016 upgrade support get my voice. We are currently looking at how to get our environment up to 1511 with full Win10 OSD and patching support and an in-place upgrade would make that 1000 times easier.

  • dgr commented  ·   ·  Flag as inappropriate

    x1000

    I commented here: http://blogs.technet.com/b/configmgrteam/archive/2015/12/08/system-center-configuration-manager-ga.aspx#pi168308=3 on 12/16.

    We went production with 2012 in spring/summer of 2012. Server 2012 wasn't RTM yet so we had NO CHOICE but to use Server 2008 R2 on our primary.

    Now I find I will be forced to perform a side-by-side "upgrade" (there's little that is "upgrade" about it) in late 2016. This is a nightmare for a medium-sized, global company such as ours. Its like we are being penalized for being an early adopter.

    Please please please...give us a REAL upgrade path to move forward from 2008 R2. Side-by-side only works for lab environments, very small companies, or wherever nobody cares about SLAs or service uptime.

    Even a site restore from a backup makes me super nervous. The few times I have had to use that over the years supporting different clients a site reset caused more issues than it solved 50% of the time.

  • Sri Bala commented  ·   ·  Flag as inappropriate

    I would agree with Steve

    Windows Server 2008 R2 -> Windows Server 2012 R2
    Windows Server 2012 R2 -> Windows Server 2016

  • Steve Thompson commented  ·   ·  Flag as inappropriate

    I'd say these two:
    Windows Server 2008 R2 -> Windows Server 2012 R2
    Windows Server 2012 R2 -> Windows Server 2016

Feedback and Knowledge Base