Thanks Jason, I’ll keep checking then and wait to hear something from MS. I’ve already been in communication with MS about my issues preventing any future upgrades, but unfortunately our situation is extremely nitch, so… Ryan
From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, December 9, 2015 12:18 PM To: [email protected] Subject: RE: [mssms] SCCM v1511 on VLSC? No, nothing has been publically announced about future builds – some inferences can be made but there’s nothing official for sure. Also, just because there will be a release coinciding with Server 2016 doesn’t necessarily mean that release/build will be “for” Server 2016. They will certainly add support for it as they have for all other versions and editions of Windows but as to whether there will be anything special for Windows Server 2016 is TBD. If you have items in mind, get them on uservoice (or connect) ASAP though. J From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Shugart Sent: Wednesday, December 9, 2015 12:30 PM To: [email protected] Subject: RE: [mssms] SCCM v1511 on VLSC? Has MS said yet what kind of support for Server 2016 will be in 2012R2? I’m hoping basic support like Windows 10, as I’m holding off upgrading as long as possible due to custom 3RD party apps. Ryan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David Jones Sent: Wednesday, December 9, 2015 11:17 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] SCCM v1511 on VLSC? thanks Jason. I'm trying to find numbers on how many clients we can manage with the SQL Express. I assume it will still install that if you want it to. The page talking about SQL doesn't give limitations. On Wed, Dec 9, 2015 at 11:49 AM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: No, this never was the case. From now on, ConfigMgr will be builds just like (or at least similar to) Windows 10 that layer on top of each other. At most, they will be in-place upgrades but will be more like CUs typically although there is a built-in servicing now so no matter what it will be a very seamless process to install them. When the features needed to support Server 2016 are available, they will be added to a build that comes down through the built-in servicing feature. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of David Jones Sent: Wednesday, December 9, 2015 10:39 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] SCCM v1511 on VLSC? Earlier in the year, I read something that said the new ConfigMgr was going to be released twice. Once in the fall to support Windows 10 and again in the spring to support Server 10 when it's released as well as Win10. The kicker was that if you installed the first one, you could not upgrade with the second one meaning you had to start over again when the second one came out. I hope I'm not the only one remembering this or it was a bad dream one night. Is that still the case or is this the one and only Configmgr start? On Wed, Dec 9, 2015 at 11:21 AM, Mote, Todd <[email protected]<mailto:[email protected]>> wrote: So I see two entries under system center that say “(current branch)” in VLSC System Center Config Mgr Client Mgmt License (current branch) System Center Endpoint Protection (current branch) But nothing just “System Center Configuration Manager Server (current branch)”. The description of the client mgmt. entry one talks about SQL and VMM, I don’t need all that, I just want the current branch sccm bits. Is there an entry for that, what’s the name of the ISO you all have been downloading? Todd MiTek Holdings, Inc., 2011-2014, All Rights Reserved ________________________________ This communication (including any attachments) contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying, or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it.
