I *think* there are other things like this. I don’t think it has to anything to do with updates for Edge, I think it’s a carrot to get folks not to choose LTSB although it could be a combination of these also.
As for ConfigMgr, that’s what the release later this year is mostly about based on my [limited] knowledge; don’t know when they’ll publically show it off or reveal any info though. Some of it may be in TP2 already but don’t know. J From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Monday, August 3, 2015 10:38 AM To: [email protected] Subject: [mssms] RE: Quick Poll Looking on VLSC this morning, the LTSB doesn’t get the Edge browser. It makes sense, because Edge gets updates released immediately, but we were really hoping to use Edge vs. Chrome when we roll Win10. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Underwood, Bob Sent: Monday, August 03, 2015 11:34 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Quick Poll For us it’ll definitely be LTSB for our manufacturing and other highly regulated systems, and probably LTSB for most of the rest of the environment as well… with perhaps a well-defined list of early-adopter types who could be on the CBB. It kind of depends on how the controls within SCCM shake out, and how we’re able to make things available. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Monday, August 03, 2015 9:18 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Quick Poll For us stability far outweighs having new features. We must maintain stability and security above all else. We also cannot roll out new features without training. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, July 31, 2015 12:48 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Quick Poll So the question is then, do you expect to retest everything every time a new servicing release is put? Everything being hardware, software, etc. or just assume nothing is going to break? (I’m not trying to push you one way or another at all, just trying to see what folks are thinking around this). J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dave Knoll Sent: Friday, July 31, 2015 12:23 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Quick Poll Our company is in Manufacturing. I don’t think our users would tolerate no new features for 10 years. After all, they’ll have the new features on their home PC’s and will want them at work. We’ll be going current branch unless we run into a use case where we must go LTSB. Also, there will be different .ISO’s for CB and LTSB. That adds to the deployment fun and makes it tougher to undo a bad decision. Dave From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Friday, July 31, 2015 9: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. ________________________________ This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com ________________________________ [CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
