Ask a questionAsk a question
 

Answerno more releases of SCCM ?

Answers

  • Sunday, September 13, 2009 4:52 PMWallyMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    The product, like *any* product, is not without its shortcomings, issues, whatever you want to call them. Some of the things you highlight here are things we had no choice in for the current version of the product - we had to live with them. Some things are the best we can do with them at the time, but technology moves on.

    We *are not* done with Configuration Manager. As stated above, we already announce the R3 version of Configuration Manager 2007, which requires our SP2 release (in release candidate testing right now). R3 will have new features that you can read about, but is not a release designed to change a lot of how things are done today (yes a few things like delta AD discoveries, fast collection evaluations, etc, but it is not to redesign or 'fix' any shortcomings like you feel the product has).

    And we have a very large team working on Configuration Manager vNext, which is a completely new version of the product with a common interface that other System Center products have, and many new and updated features.

    So, I'll state that this post (and the original one above) does nothing to help anyone that uses these forums for getting answers on the product. Please ask constructive questions and if you have thoughts on how to improve the product, you should do as everyone is suggested, and that is to submit feedback (suggestions or bugs) via the Feedback option on the System Center Configuration Manager site on http://connect.microsoft.com.

    If there can be appropriate discussion on this thread now, I'll leave it. If the thread is going to not generate any useful discussion, I'll go ahead and delete it.


    Wally Mead

All Replies

  • Saturday, September 12, 2009 6:33 AMUmansson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi

    Microsoft just announced the release of SCCM R3 early next year. This is the first product to release a R3. Besides from that the beta for SCCM 2010 is  too expected in the beginning of 2010.

    So Microsoft does believe in the product and the investments in System Center are growing as I see it.
    Regards Ulf Mansson MCT, MCSE www.lumagate.com
  • Saturday, September 12, 2009 10:19 AM-Hari- Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Good to here that Ulf
  • Saturday, September 12, 2009 8:55 PMGarth JonesMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Can I ask why you are asking this question? MS is putting lots of effort in ConfigMgr, so I'm curious why your are asking this question.


    http://www.enhansoft.com/
  • Sunday, September 13, 2009 6:20 AMIlia Chipitsine Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Can I ask why you are asking this question? MS is putting lots of effort in ConfigMgr, so I'm curious why your are asking this question.


    http://www.enhansoft.com/
    because of informational vacuum around Configuration Manager.

    We are using SCCM2007 and I see a lot of things to do better, for instance

    1) COM security model (which is used for SCCM Console and Remote Tools) is very bad. It gives you no clue if something goes wrong, just "access denied"

    2) Remote Tools security model is too simple for real life application - user is being notified in non-localized manner and user account name (not real name) is given for approval. Also, approval model is somewhat not flexible at all, we'd like some support staff to allow contact without any approval (in read/write manner), the not-so-qualified-support-staff we'd like to allow contact in read-inly model with approval.

    and many-many-many other things I can share with developers if they realy want to do the product better.

    contrary, I'm getting answers "this is by design" and there'is only new thing in R3 is "power savind reports", looks like "somewhar just has to be done before Platform-2010 thing", no real improvement is seen there (and there ARE things which could be done much better!)

    so, that'all just because of informational vacuum around SCCM itself (and "this is by design" instead of "yes, it could be done better and we'll do it better")
  • Sunday, September 13, 2009 4:52 PMWallyMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    The product, like *any* product, is not without its shortcomings, issues, whatever you want to call them. Some of the things you highlight here are things we had no choice in for the current version of the product - we had to live with them. Some things are the best we can do with them at the time, but technology moves on.

    We *are not* done with Configuration Manager. As stated above, we already announce the R3 version of Configuration Manager 2007, which requires our SP2 release (in release candidate testing right now). R3 will have new features that you can read about, but is not a release designed to change a lot of how things are done today (yes a few things like delta AD discoveries, fast collection evaluations, etc, but it is not to redesign or 'fix' any shortcomings like you feel the product has).

    And we have a very large team working on Configuration Manager vNext, which is a completely new version of the product with a common interface that other System Center products have, and many new and updated features.

    So, I'll state that this post (and the original one above) does nothing to help anyone that uses these forums for getting answers on the product. Please ask constructive questions and if you have thoughts on how to improve the product, you should do as everyone is suggested, and that is to submit feedback (suggestions or bugs) via the Feedback option on the System Center Configuration Manager site on http://connect.microsoft.com.

    If there can be appropriate discussion on this thread now, I'll leave it. If the thread is going to not generate any useful discussion, I'll go ahead and delete it.


    Wally Mead