Yes you can, I did it in 2013:  
https://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_UpgradeInfrastructure

Upgrade of the Site Server Operating System<javascript:void(0)>
________________________________
Configuration Manager supports an in-place upgrade of the operating system of 
the site server in the following situations:
·         In-place upgrade to a higher Windows Server service pack as long as 
the resulting service pack level remains supported by Configuration Manager.
·         In-place upgrade from Windows Server 2012to Windows Server 2012 R2.
Configuration Manager does not support the following Windows Server upgrade 
scenarios.
·         Any version of Windows Server 2008 to any version of Windows Server 
2008 R2 or later.
·         Any version of Windows Server 2008 to any version of Windows Server 
2012 or later.
·         Any version of Windows Server 2008 R2 to any version of Windows 
Server 2012 or later.
When a direct operating system upgrade is not supported, perform one of the 
following procedures after you have installed the new operating system:
·         Install System Center 2012 Configuration Manager with the service 
pack level that you want, and configure the site according to your requirements.
·         Install System Center 2012 Configuration Manager with the service 
pack level that you want and perform a site recovery. This scenario requires 
you to have a site backup that was created by using the Backup Site Server 
maintenance task on the original Configuration Manager site, and that you use 
the same installation settings for the new System Center 2012 Configuration 
Manager site.


From: [email protected] [mailto:[email protected]] On 
Behalf Of Marcum, John
Sent: Thursday, December 10, 2015 1:07 PM
To: [email protected]
Subject: RE: [mssms] RE: Migrating server OS

I’m positive. It’s never been supported. You can change the SQL version but 
that’s all.

This is why I’m so pissed off that CM12 to v.Next side-by-side is not an 
option. My CM12 is on Server 2008 R2. To get to vNext on a modern OS I have to 
in-place upgrade my CM12 then do a side by side. Oddly enough though CM07 to 
vNext side-by-side does work. SMH

________________________________
        John Marcum
            MCITP, MCTS, MCSA
              Desktop Architect
   Bradley Arant Boult Cummings LLP
________________________________

  [H_Logo]

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Krueger, Jeff
Sent: Thursday, December 10, 2015 12:57 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] RE: Migrating server OS

You sure?  We’re going to have to look at upgrading the server OS on our 
primary from 2008R2 to 2012R2.  Was hoping to be able to build the new server 
with same name off line and then do a site restore to it.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Marcum, John
Sent: Thursday, December 10, 2015 1:31 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] RE: Migrating server OS

Requires same version OS too.

________________________________
        John Marcum
            MCITP, MCTS, MCSA
              Desktop Architect
   Bradley Arant Boult Cummings LLP
________________________________

  [H_Logo]

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Gailfus, Nick
Sent: Thursday, December 10, 2015 12:29 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] RE: Migrating server OS

Migration is the only way. Restoring a backup requires the server name and site 
code to be the same.


Nick Gailfus
Computer Technician
p. 602.953.2933  f. 602.953.0831
[email protected]<mailto:[email protected]>| 
www.leonagroup.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.leonagroup.com_&d=CwMGaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=HZJy857HKacSVMzp2_RNHvm7f0j7g1PN9_lWzdvV9H8&s=dlNiH0fayuS_Dawkl9TGXa8JzeuJVsxoiWsnbdJYdV8&e=>

[Image removed by sender.]

On Thu, Dec 10, 2015 at 10:18 AM, Marcum, John 
<[email protected]<mailto:[email protected]>> wrote:
Do a side-by-side migration.

________________________________
        John Marcum
            MCITP, MCTS, MCSA
              Desktop Architect
   Bradley Arant Boult Cummings LLP
________________________________

  [H_Logo]

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Heaton, Joseph@Wildlife
Sent: Thursday, December 10, 2015 10:44 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Migrating server OS

If I have SCCM 2012 R2 SP1, with SQL 2012 SP2, on Server 2008R2, and I want to 
migrate to a box with Server 2012 R2, is this the best way?


1)      Build new Server 2012 R2 server.

2)      Install new SCCM 2012 R2 SP1 hierarchy, new site code, etc.

3)      Backup original hierarchy

4)      Restore original hierarchy to new server

Will the backup/restore process reset the site code, etc on the new server to 
the original code?

Thanks,

Joe Heaton
Information Technology Operations Branch
Data and Technology Division
CA Department of Fish and Wildlife
1700 9th Street, 3rd Floor
Sacramento, CA  95811
Desk:  (916) 323-1284<tel:%28916%29%20323-1284>

Every Californian should conserve water.  Find out how at:
[SaveOurWater_Logo]<https://urldefense.proofpoint.com/v2/url?u=http-3A__saveourwater.com_&d=CwMGaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=HZJy857HKacSVMzp2_RNHvm7f0j7g1PN9_lWzdvV9H8&s=7j0CHVy2Qxw70ltzK4DEmVK9ZcQOrN3cWzBs9wJC5YU&e=>
SaveOurWater.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__saveourwater.com_&d=CwMGaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=HZJy857HKacSVMzp2_RNHvm7f0j7g1PN9_lWzdvV9H8&s=7j0CHVy2Qxw70ltzK4DEmVK9ZcQOrN3cWzBs9wJC5YU&e=>
 · 
Drought.CA.gov<https://urldefense.proofpoint.com/v2/url?u=http-3A__drought.ca.gov_&d=CwMGaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=HZJy857HKacSVMzp2_RNHvm7f0j7g1PN9_lWzdvV9H8&s=Ck7rW61qDmnGrDlmELHqxW40dW3SqCHTwy5CczG1muM&e=>


________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.





________________________________

CONFIDENTIALITY NOTICE: This email contains information from the sender that 
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected 
from disclosure. This email is intended for use only by the person or entity to 
whom it is addressed. If you are not the intended recipient, any use, 
disclosure, copying, distribution, printing, or any action taken in reliance on 
the contents of this email, is strictly prohibited. If you received this email 
in error, please contact the sending party by reply email, delete the email 
from your computer system and shred any paper copies.

Note to Patients: There are a number of risks you should consider before using 
e-mail to communicate with us. See our Privacy & Security page on 
www.henryford.com<http://www.henryford.com> for more detailed information as 
well as information concerning MyChart, our new patient portal. If you do not 
believe that our policy gives you the privacy and security protection you need, 
do not send e-mail or Internet communications to us.



Reply via email to