RE: [mssms] CAS/PS Upgrade Question
Thanks Sherry and Jeff, I did found from Microsoft links that direct 1606 is possible. Is OS upgrade recommended now at 8239 level or post upgrading to 1606, the latest ? Sherry: Yes, I do consider all valuable suggestions you made Kind Regards, Vasu Miriyala From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jeff Poling Sent: Wednesday, October 19, 2016 8:17 PM To: Sherry Kissinger; mssms@lists.myitforum.com Subject: RE: [mssms] CAS/PS Upgrade Question Why not use the 1606 baseline build that was released last week? It is in VLSC. And like Sherry said, really evaluate if you need the CAS Jeff Sent from my Windows 10 phone From: Sherry Kissinger<mailto:sherrylkissin...@gmail.com> Sent: Wednesday, October 19, 2016 9:08 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] CAS/PS Upgrade Question We upgraded the OS well before (months if I recall correctly) upgrading to 1511. that was to distinctly separate any issues that *might* have arisen from the "the reason for this issue is 1511 vs. the reason is the os upgrade". Helps in determining/fixing any issues found. My notes indicate that we uninstalled/reinstalled the ADK prior to installing 1511. Side note: 1606 is or will soon be--released in media so that you don't have to do 1511, then 1602, then 1606. If you haven't yet done so--what's your rationale for starting with 1511 and doing 2 upgrades instead of starting with 1606? Another side note--because it has to be said. :) You didn't mention how many clients you support with those 5 primaries. are you SURE you need all 5--or can you, prior to upgrading to Current Branch--move clients around to get rid of one (or 3... the fewer you have, the better off you are for DRS). Or of course... do you need a CAS at ALL ? :) On Tue, Oct 18, 2016 at 11:59 PM, Miriyala, Vasu mailto:vasu.miriy...@capgemini.com>> wrote: Hello, We have CAS and 5 Primaries currently on ConfigMgr 2012 SP2 (Build 8239), with SQL Server 2012, ADK 8.1, MDT 2013 running Server 2008 R2 We plan to upgrade it to latest versions (or close to), here is our plan of action 1) SCCM Upgrade to 1511, then to 1602 2) Step 1) allows us to do in place Upgrade of OS to Server 2012 R2 3) Then SQL Upgrade from 2012 to either 2014/2016 4) ADK 8.1 to 1511 5) MDT 2013 to MDT 2013 Update 2 6) WSUS needs to be un/reinstalled along with SUP roles Appreciate your suggestions in the order or any learnings/lessons if any of you tried this or similar upgrade. Our goal is twofold, 1) ensure all in place upgrades happens, so no parallel infra needs to be built and 2) to ensure Infra runs latest versions in all components as much possible Kind Regards, Vasu Miriyala This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
RE: [mssms] CAS/PS Upgrade Question
Why not use the 1606 baseline build that was released last week? It is in VLSC. And like Sherry said, really evaluate if you need the CAS Jeff Sent from my Windows 10 phone From: Sherry Kissinger<mailto:sherrylkissin...@gmail.com> Sent: Wednesday, October 19, 2016 9:08 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] CAS/PS Upgrade Question We upgraded the OS well before (months if I recall correctly) upgrading to 1511. that was to distinctly separate any issues that *might* have arisen from the "the reason for this issue is 1511 vs. the reason is the os upgrade". Helps in determining/fixing any issues found. My notes indicate that we uninstalled/reinstalled the ADK prior to installing 1511. Side note: 1606 is or will soon be--released in media so that you don't have to do 1511, then 1602, then 1606. If you haven't yet done so--what's your rationale for starting with 1511 and doing 2 upgrades instead of starting with 1606? Another side note--because it has to be said. :) You didn't mention how many clients you support with those 5 primaries. are you SURE you need all 5--or can you, prior to upgrading to Current Branch--move clients around to get rid of one (or 3... the fewer you have, the better off you are for DRS). Or of course... do you need a CAS at ALL ? :) On Tue, Oct 18, 2016 at 11:59 PM, Miriyala, Vasu < vasu.miriy...@capgemini.com> wrote: > Hello, > > > > We have CAS and 5 Primaries currently on ConfigMgr 2012 SP2 (Build 8239), > with SQL Server 2012, ADK 8.1, MDT 2013 running Server 2008 R2 We plan to > upgrade it to latest versions (or close to), here is our plan of action > > > > 1) SCCM Upgrade to 1511, then to 1602 > > 2) Step 1) allows us to do in place Upgrade of OS to Server 2012 R2 > > 3) Then SQL Upgrade from 2012 to either 2014/2016 > > 4) ADK 8.1 to 1511 > > 5) MDT 2013 to MDT 2013 Update 2 > > 6) WSUS needs to be un/reinstalled along with SUP roles > > > > Appreciate your suggestions in the order or any learnings/lessons if any > of you tried this or similar upgrade. Our goal is twofold, 1) ensure all in > place upgrades happens, so no parallel infra needs to be built and 2) to > ensure Infra runs latest versions in all components as much possible > > > > Kind Regards, > > *Vasu Miriyala* > > > > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, you > are not authorized to read, print, retain, copy, disseminate, distribute, > or use this message or any part thereof. If you receive this message in > error, please notify the sender immediately and delete all copies of this > message. > > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
Re: [mssms] CAS/PS Upgrade Question
We upgraded the OS well before (months if I recall correctly) upgrading to 1511. that was to distinctly separate any issues that *might* have arisen from the "the reason for this issue is 1511 vs. the reason is the os upgrade". Helps in determining/fixing any issues found. My notes indicate that we uninstalled/reinstalled the ADK prior to installing 1511. Side note: 1606 is or will soon be--released in media so that you don't have to do 1511, then 1602, then 1606. If you haven't yet done so--what's your rationale for starting with 1511 and doing 2 upgrades instead of starting with 1606? Another side note--because it has to be said. :) You didn't mention how many clients you support with those 5 primaries. are you SURE you need all 5--or can you, prior to upgrading to Current Branch--move clients around to get rid of one (or 3... the fewer you have, the better off you are for DRS). Or of course... do you need a CAS at ALL ? :) On Tue, Oct 18, 2016 at 11:59 PM, Miriyala, Vasu < vasu.miriy...@capgemini.com> wrote: > Hello, > > > > We have CAS and 5 Primaries currently on ConfigMgr 2012 SP2 (Build 8239), > with SQL Server 2012, ADK 8.1, MDT 2013 running Server 2008 R2 We plan to > upgrade it to latest versions (or close to), here is our plan of action > > > > 1) SCCM Upgrade to 1511, then to 1602 > > 2) Step 1) allows us to do in place Upgrade of OS to Server 2012 R2 > > 3) Then SQL Upgrade from 2012 to either 2014/2016 > > 4) ADK 8.1 to 1511 > > 5) MDT 2013 to MDT 2013 Update 2 > > 6) WSUS needs to be un/reinstalled along with SUP roles > > > > Appreciate your suggestions in the order or any learnings/lessons if any > of you tried this or similar upgrade. Our goal is twofold, 1) ensure all in > place upgrades happens, so no parallel infra needs to be built and 2) to > ensure Infra runs latest versions in all components as much possible > > > > Kind Regards, > > *Vasu Miriyala* > > > > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, you > are not authorized to read, print, retain, copy, disseminate, distribute, > or use this message or any part thereof. If you receive this message in > error, please notify the sender immediately and delete all copies of this > message. > > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
[mssms] CAS/PS Upgrade Question
Hello, We have CAS and 5 Primaries currently on ConfigMgr 2012 SP2 (Build 8239), with SQL Server 2012, ADK 8.1, MDT 2013 running Server 2008 R2 We plan to upgrade it to latest versions (or close to), here is our plan of action 1) SCCM Upgrade to 1511, then to 1602 2) Step 1) allows us to do in place Upgrade of OS to Server 2012 R2 3) Then SQL Upgrade from 2012 to either 2014/2016 4) ADK 8.1 to 1511 5) MDT 2013 to MDT 2013 Update 2 6) WSUS needs to be un/reinstalled along with SUP roles Appreciate your suggestions in the order or any learnings/lessons if any of you tried this or similar upgrade. Our goal is twofold, 1) ensure all in place upgrades happens, so no parallel infra needs to be built and 2) to ensure Infra runs latest versions in all components as much possible Kind Regards, Vasu Miriyala This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.