Don’t feel bad, I filed a bug about AV policies not being RBAC’d waaaay back in 
the RTM time frame and got told it would be in a future version.  It hasn’t 
been in any version since, SP1, R2, SP2, or 2016.  I’ve resigned myself to 
having to manage AV policies for everybody that I’ve federated for.  Much like 
IPSec policies in AD I guess.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Robert Spinelli
Sent: Wednesday, June 10, 2015 11:16 AM
To: [email protected]
Subject: RE: [mssms] SCCM 2016 - Feedback?

That is timely, when I get some time, I’ll add a few things.  I don’t have much 
luck though I’ve probably filled at least 10 DCR’s in the past and not one has 
ever been approved.  I know this isn’t a DCR request, but all those DCR 
rejections have taken its toll.. ha.

The main reason I installed SCCM 2016 was too see if they changed/added any of 
the reports for application deployments.  I think I’ve brought it up in the 
past here, but tracking application installs (success, failure, restart, etc.) 
I think is pretty bad in 2012.  It was/is easier in my opinion to get better 
deployment status for legacy packages then applications.

Rob

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Steve Whitcher
Sent: Wednesday, June 10, 2015 11:29 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] SCCM 2016 - Feedback?

This is timely :
http://blogs.technet.com/b/configmgrteam/archive/2015/06/10/tell-us-your-suggestions-for-configuration-manager.aspx


—
Sent from Mailbox<https://www.dropbox.com/mailbox>


On Wed, Jun 10, 2015 at 9:02 AM, Mote, Todd 
<[email protected]<mailto:[email protected]>> wrote:
I don’t know if anyone noticed, but the version numbers between SP2/R2SP1 and 
2016 are exactly the same, 5.0.8239.1000.  So, yea, I can kinda agree with 
Robert, at least at this stage, it seems like a service pack.  Because it 
likely is.  There are some differences, like on the auto client upgrade page, 
and a couple of other places, but by and large seems mostly the same at this 
point.


Todd


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Wednesday, June 10, 2015 8:53 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] SCCM 2016 - Feedback?


I am not aware of any information having been published on that apart from that 
the datacentre product will be brought closer to Intune in terms of release 
cycles


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of John Aubrey
Sent: 10 June 2015 14:26
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] SCCM 2016 - Feedback?


I thought SP2 was for Win10 support and get us by until 2016 version is ready 
to go?  There is another update coming in 2016 as well?  Maybe we need to go 
pound the connect board with some new feature requests?


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of LEROY Mathieu
Sent: Wednesday, June 10, 2015 9:18 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] SCCM 2016 - Feedback?


Keep in mind the that ConfigMgr Vnext RTM will be available later this year for 
and that another release (let’s called it R2) will be available with Windows 
Server Vnext next year ;)
This year release will be focused on MDM enhancements and minimum (yet 
sufficient) support for Windows 10 (ie upgrade etc). Next release will add more 
depth for the Windows 10 Ecosystem ☺


De : [email protected]<mailto:[email protected]> 
[mailto:[email protected]] De la part de Robert Spinelli
Envoyé : mercredi 10 juin 2015 15:07
À : mssms
Objet : [mssms] SCCM 2016 - Feedback?


So I installed SCCM 2016, played around with it and can say I’ve never been so 
underwhelmed by a new product release.  I understand it’s a preview, but I 
can’t see what else they can throw in there that is going to really make this 
feel like  a new product release. There is nothing super new about it, it feels 
like a service pack and that’s it.  It seems to me that since they were 
releasing a new version of System Center they had to also release a new version 
of SCCM, so they just threw something together to say here you go, we have a 
new version.  This sort of confirms to me MS is totally focusing on Intune for 
some reason I still can’t totally figure out.


What do others think?


Rob












Reply via email to