But only original versions…..no custom images…..so you get all the “garbage” 
back after every upgrade…

No fun if you have custom images with all the languages in it (which also need 
to be upgraded with every release)…

 

Unless that has been changed recently…

 

From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On 
Behalf Of Niall Brady
Sent: Friday, January 29, 2016 6:02 PM
To: ms...@lists.myitforum.com
Subject: Re: [mssms] SCCM 2012 R2 SP1 CU2 - Windows 10 TH2

 

think of it this way, windows 10 comes out in a new flavor every 6 or so 
months, so far there was the RTM release in 1507, then there was threshold 2 in 
1511, no doubt redstone will release at some date and be known as 16xx (dont 
know what month hence xx),

you need to be ConfigMgr Current Branch 1511 (or whatever version it will be at 
by then) in order to do windows 10 servicing on windows 10 

windows 10 servicing is the ability to 'offer' and deploy patches to 
collections of windows 10 computers, much like you download and upgrade from 
windows 10 1507 to windows 10 1511

there is a large 'upgrade' file involved

you can do this automatically on a preset basis in Current Branch by defining 
servicing plans or you can upgrade these computers when you want by deploying 
the updates to them using normal SUP,

lastly you can also use the Upgrade Task sequence to upgrade these computers in 
addition to upgrading other editions of windows such as windows 7 or windows 8 
to windows 10

 

On Fri, Jan 29, 2016 at 5:46 PM, Marcum, John <jmar...@babc.com 
<mailto:jmar...@babc.com> > wrote:

Like update to a new “branch”

 


  _____  


        John Marcum

            MCITP, MCTS, MCSA
              Desktop Architect

   Bradley Arant Boult Cummings LLP


  _____  


    

  

 

From: listsadmin@lists.myitforum.com <mailto:listsadmin@lists.myitforum.com>  
[mailto:listsadmin@lists.myitforum.com <mailto:listsadmin@lists.myitforum.com> 
] On Behalf Of Robert Spinelli
Sent: Friday, January 29, 2016 10:43 AM
To: ms...@lists.myitforum.com <mailto:ms...@lists.myitforum.com> 
Subject: RE: [mssms] SCCM 2012 R2 SP1 CU2 - Windows 10 TH2

 

To clarify since I work with Henry Wilson and he is insane..

 

When you say servicing you’re talking about Win10 branches or saying servicing 
it as you won’t be able to do HW inventory / SW inventory.. etc.  

 

From: listsadmin@lists.myitforum.com <mailto:listsadmin@lists.myitforum.com>  
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Friday, January 29, 2016 11:34 AM
To: ms...@lists.myitforum.com <mailto:ms...@lists.myitforum.com> 
Subject: RE: [mssms] SCCM 2012 R2 SP1 CU2 - Windows 10 TH2

 

That’s good to know.  

 

When you say service it, what would be an example of “servicing’ it.

 

From: listsadmin@lists.myitforum.com <mailto:listsadmin@lists.myitforum.com>  
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Niall Brady
Sent: Friday, January 29, 2016 11:29 AM
To: ms...@lists.myitforum.com <mailto:ms...@lists.myitforum.com> 
Subject: Re: [mssms] SCCM 2012 R2 SP1 CU2 - Windows 10 TH2

 

yes you can deploy it but if you want to service it or any release of windows 
10 going forward you need to move to SCCM 1511.

 

On Fri, Jan 29, 2016 at 5:13 PM, Robert Spinelli <rspinell...@outlook.com 
<mailto:rspinell...@outlook.com> > wrote:

I’ve read bunch of blogs, but guess my brain isn’t working since its Friday, 
since it’s still not clear to me.

*         https://www.systemcenterdudes.com/sccm-2012-windows-10-th2-1511/

*         
http://blogs.technet.com/b/configmgrteam/archive/2015/10/27/system-center-configmgr-support-for-win-10-and-intune.aspx

 

Am I able to deploy Windows 10 Threshold 2 with SCCM 2012 R2  SP1 CU2 or do I 
need to go to SCCM 1511?  

 

Thanks 

 

Rob

 

 

 

 

 

  _____  


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