You can absolutely manage and deploy Windows 10 with ConfigMgr 2012 SP2/R2 SP1, supporting the same functionality that exists for Windows 7 and Windows 8/8.1. New functionality often requires new code, which is case with the new Windows 10 servicing model.
From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: Tuesday, August 4, 2015 3:52 AM To: [email protected] Subject: RE: [mssms] RE: Quick Poll Isn't that a step away from the "No need to upgrade ConfigMgr to a newer version to Deploy & Manage Windows 10" statement that was trumpeted out before? I remember a session someone held at Barcelona covering that... ;-) //A From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: den 4 augusti 2015 12:09 To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: Quick Poll Thank you Aaron. That makes things much clearer. Mike From: <[email protected]<mailto:[email protected]>> on behalf of Aaron Czechowski <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday, August 4, 2015 at 12:43 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: [mssms] RE: Quick Poll I'm working to refine a blog post that will talk some more about this, trying to get it posted soon. This will primarily fit in with the next release of ConfigMgr, so you should be evaluating the Technical Previews, and if you are deploying or planning to deploy Windows 10 you should also have a plan to upgrade to the next version of ConfigMgr. Think of the "rings" like this: Insiders (rapid, bleeding edge), CB (consumer-style, upgrade a couple times a year), CBB (similar to CB but allows business to defer the upgrade, but not indefinitely, only for a few months), and LTSB (very stable, new features on scale of year[s]). Management of CB/CBB and LTSB will integrate with the next version of ConfigMgr, monthly cumulative updates as well as the build-to-build upgrades can be managed via WSUS/ConfigMgr. You can also point devices at WU, where you are delegating control of scheduling to Microsoft (which might work for some customers in some situations). Insiders requires this. Aaron From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Monday, August 3, 2015 7:13 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: Quick Poll Aaron, How does this all fit into SCCM? We manage all of our updating through SCCM. Since we're a hospital we have to be very cautious about deploying anything which would sound like the LTSB. On the other hand having the flexibility of rolling out new features when they fit our needs would be a huge advantage, which sounds like CB or CBB. The new features that would be coming from Microsoft for CB/CBB, would they be available to deploy through WSUS+SCCM or will they be exclusively available through Windows Update? Thanks Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCSE, MCTS, MCITP, MCSA, MS [ Profile<http://www.mycertprofile.com/Profile/5319166625> ] [Blog<http://thesystemsmonkey.wordpress.com/>] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb I will rise when I have fallen. "Unless you try to do something beyond what you have already mastered, you will never grow." -Ralph Waldo Emerson From: <[email protected]<mailto:[email protected]>> on behalf of Aaron Czechowski <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, August 3, 2015 at 6:58 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [mssms] RE: Quick Poll Same media, both are Current Branch. Difference is in the config. It's in Windows Update, Advanced options. "Defer upgrades" is the CB vs CBB setting. (see attached) >From a policy perspective, the CB vs CBB setting is controlled via a new >policy under Computer Configuration > Windows Components > Windows Update, >"Defer Upgrade" Aaron From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Monday, August 3, 2015 10:18 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Quick Poll >From a media perspective how do I know which is CB and which is CB for >Business? From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Monday, August 3, 2015 11:28 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Quick Poll We believe for most organizations you should use a mix: · A small percentage (maybe just your own lab machines) on the Insider branch, to see new features as they are being developed. · A small percentage on the Current Branch, as early adopters. · A significant percentage on the Current Branch for Business, deployed in phases. · Some percentage (dependent on industry) of mission-critical machines on the Long Term Servicing Branch, probably averaging under 20% (could be zero for some firms, higher for others). Maybe that mix works out to <1%, 1%, 80%, and the rest. Thanks, -Michael From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Friday, July 31, 2015 8:35 AM To: SMS List ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>> Subject: [mssms] Quick Poll When you deploy Windows 10 will you deploy current branch or long term servicing? http://jermsmit.com/windows-10-enterprise-2015-ltsb-whats-that/ ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] ________________________________ 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. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
