It’s supported for 1602.

J

From: <[email protected]<mailto:[email protected]>> 
on behalf of Justin VanDyke-Restifo 
<[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Friday, May 13, 2016 at 8:29 AM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [mssms] Best upgrade path ?


Same boat.

Initially single Primary Site Server on WS 2008 R2 with ConfigMgr 2012 R2 CU3. 
We upgraded to 1511 with in place but want to do 2008r2 to 2012r2 now. Is that 
upgrade supported? I thought I read that it is now.




[photo]
Justin VanDyke-Restifo
Network Architecture Shepherd, Voorheesville CSD
518-765-3313 x318<tel:518-765-3313%20x318>| 
[email protected]<mailto:[email protected]>| 
www.voorheesville.org<http://www.voorheesville.org>| 432 New Salem Rd 
Voorheesville, NY 12186
[https://s3.amazonaws.com/images.wisestamp.com/icons_32/linkedin.png]<http://www.linkedin.com/pub/justin-vandyke-restifo/27/74a/3b4>
 [https://s3.amazonaws.com/images.wisestamp.com/icons_32/googleplus.png] 
<http://plus.google.com/u/0/102151622008698026219/>

"Welcome to the Redundancy Department. Here is where you will find redundant 
people is what you will find here at the Redundancy Department."
[http://ws-promos.appspot.com/ga/pixel.png?yes__count=1&e=5732568548769792]
Get a signature like this: Click 
here!<http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=&u=495651665646902>

On Fri, May 13, 2016 at 9:03 AM, Marcum, John 
<[email protected]<mailto:[email protected]>> wrote:
Personally I am in the middle of a side0by-side migration from 1602 to 1602 
just because my old primary site is on 2008R2.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Freddy Grande
Sent: Thursday, May 12, 2016 7:52 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Best upgrade path ?


We were on a similar boat;

Initially single Primary Site Server on WS 2008 R2 with ConfigMgr 2012 R2 CU3

1.       Upgraded in place to ConfigMgr 1511

a.       Our plan was to upgrade that to 1602 but for some reason no matter 
what we did it never showed up on the console

2.       Built new WS 2012 R2 with ConfigMgr 1511 > upgraded to 1602

3.       Migrated pretty much everything from old server to new server (1511 to 
1602 migration)

4.       Had issues with DPs and we still seem to be having some weird cryptic 
issues

a.       Application Deployments with following errors: “CI Version Info timed 
out” or “CI documents download timed out”

b.       Site server deploys client to itself but it never reports to the 
actual site

c.       Errors showing in Site Status for Application Catalog web service 
point and Application Catalog website point but no relevant errors in logs



If I could do it again I would bring up a new server without migrating anything 
and configuring it from scratch. We are small enough that we can actually do 
this but didn’t expect these many issues from a migration.



You should note as well you can’t “install 1602” from scratch. You must install 
1511 first and upgrade to it.



Regards,

Freddy

-----Original Message-----
From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Richard Bjerregaard
Sent: Friday, 13 May 2016 6:49 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] Best upgrade path ?



Hi,



So 1 vote for in-place upgrade of OS followed by in-place upgrade of SCCM



Would anyone



1) Build a new server with W2K12R2, install SCCM R2 CU3, restore DB and Data

   from backup of old server, in-place upgrade SCCM to 1602.

2) Build a new server with W2K12R2, install SCCM 1602, manuel

   "rebuilt" configuration. Perhaps restore selected data from

   backup.

3) Build a new server with W2K12R2, install SCCM 1602, start from

   scratch with a new configuration, applications and TS.



How will my clients reacts to all this?



rg

Richard



12. maj 2016, 20:24:07, you wrote:



> I'm never a fan of in-place upgrading an OS, especially on a server.

> Having said that I'd do an R revision in-place then upgrade CM in-place.









> -----Original Message-----

> From: [email protected]<mailto:[email protected]>

> [mailto:[email protected]] On Behalf Of Richard

> Bjerregaard

> Sent: Wednesday, May 11, 2016 5:10 PM

> To: [email protected]<mailto:[email protected]>

> Subject: [mssms] Best upgrade path ?



> Hi everyone



>   Looking for some guidance, high level steps.



>   Have

>   SCCM 2012 R2 CU3 running on Windows Server 2012 RTM

>   4.500 clients, all windows 7, ~200 applications.

>   Just 1 server. Physical.



>   How can I get(upgrade) to SCCM 1602 on Windows Server 2012 R2 ?

>   I can properly wait until Server 2016 is released, if that makes a

>   difference.



>   Preparing for Windows 10.



> rg

> Richard











> ________________________________



> 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.
















NOTICE: This email is confidential. If you are not the nominated recipient, 
please immediately delete this email, destroy all copies and inform the sender. 
Australian Maritime Systems Ltd. (AMS) prohibits the unauthorised copying or 
distribution of this email. This email does not necessarily express the views 
of AMS. AMS does not warrant nor guarantee that this email communication is 
free from errors, virus, interception or interference.
________________________________

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.




Reply via email to