none
Multi-Tenancy

    Question

  • Is there an offering that would allow for the replacement of the Kaseya product?  Out of domain remote control, patch management, software distribution etc.

    I have read a bunch of stuff on SCCM SCSM but nothing that I see would replace this offering.

    Wednesday, September 07, 2011 6:19 PM

Answers

  • Hi

    I would say that the combination of the two (SCSM and SCCM) delivers.

    SCCM's Remote Tools supports "out of domain remote control"

    http://technet.microsoft.com/en-us/library/bb693702.aspx

    Of course SCCM takes care of software distribution and patch management as well. By adding SCSM to the implementation will be able to utilize the information from SCCM in a quick and easy way. For instance you'll be able to pick a computer from the CMDB and see a complete view, with data from AD, SCCM and SCOM - depending on which products you choose to implement. In the computer form you'll be able to see the basic information for the computer from AD, installed software and patches from SCCM, IP and related incidents generated by SCOM. You’re even able to define baselines for patches and have incidents spawned based on computers out of compliance.

    The remote tools can be triggered directly from the SCSM console when a computer is selected. This is a custom feature, but it's really simple to add as a custom activity in the console.

    The feature list is waaaay to long, so... Now, what are you missing? :)

     Ooops... missed out on the important thig here... Multi-Tenancy - See next post...


    Patrik Sundqvist Solutions Architect @ Gridpro AB Blog: http://blogs.litware.se
    Wednesday, September 07, 2011 6:48 PM

All replies

  • Hi

    I would say that the combination of the two (SCSM and SCCM) delivers.

    SCCM's Remote Tools supports "out of domain remote control"

    http://technet.microsoft.com/en-us/library/bb693702.aspx

    Of course SCCM takes care of software distribution and patch management as well. By adding SCSM to the implementation will be able to utilize the information from SCCM in a quick and easy way. For instance you'll be able to pick a computer from the CMDB and see a complete view, with data from AD, SCCM and SCOM - depending on which products you choose to implement. In the computer form you'll be able to see the basic information for the computer from AD, installed software and patches from SCCM, IP and related incidents generated by SCOM. You’re even able to define baselines for patches and have incidents spawned based on computers out of compliance.

    The remote tools can be triggered directly from the SCSM console when a computer is selected. This is a custom feature, but it's really simple to add as a custom activity in the console.

    The feature list is waaaay to long, so... Now, what are you missing? :)

     Ooops... missed out on the important thig here... Multi-Tenancy - See next post...


    Patrik Sundqvist Solutions Architect @ Gridpro AB Blog: http://blogs.litware.se
    Wednesday, September 07, 2011 6:48 PM
  • Hi again..

    Regarding Multi-Tenancy SCSM might be a challange. See this post for clarification:

    http://blogs.technet.com/b/servicemanager/archive/2009/12/22/does-service-manager-support-multitenancy-managed-service-providers.aspx


    Patrik Sundqvist Solutions Architect @ Gridpro AB Blog: http://blogs.litware.se
    Wednesday, September 07, 2011 6:50 PM
  • Thank you for your information.  I did find this post from 2009 but I was hoping for more updated information for the 2012 product set.  There just happens to be better "Help Desk" tools out there.  We will look deeper and see what we can find.

     

    Thanks again

    Wednesday, September 07, 2011 9:01 PM
  • I´m stugeling with the same topic myself, we need to evaluate if SCCM is capable of multi tenancy, meaning to serve few customers in the same workspace. In nordic countires we have lot of small customer enviroments and one admin supplies a few customers, not just one. We want to discontinue the way of jumping from one enviroment to another and creating same generic software packages to every customer separatly. Our main consern is, how the remote tools would work, are they relying on active directory rights? If we build a primary site server on our enviroment, and child server on customers enviroment, will it also require domain trusts? What will happen, if some customers has same IP-pools and subnets?

    ConfigMgr 2012 does not provide any new features to this subjects, as far I as know, only old network protocols are gone.

    Thursday, November 17, 2011 7:43 AM
  • @Yannara

    This is exactly my concern aswell, as i'm considering system center 2012 as management platform in our hosting environment. Unfortunate I can't see a design where multi tennancy is possible. It's not an option to do domain trusts, so management / discovery would have to be done in other ways.

    The questions is how? :-)

     

    Wednesday, January 04, 2012 10:04 PM
  • I´ve seen server 8 hyper-v presentation which provides support on tcp/ip level for a customers who have same IP pool. This is a feature because of a private cloud technology. So I rise this issue again. I asked MVPs about this, and they claimed that there is official documentation on multi tenancy planning, but still Microsoft does not officially support this feature. It would be nice to take a look at that documentation.

    Still if SCCM would support multi tenancy on a tcp/ip level, the question of security and access rights pops up. I can´t figure it, how multiple network access accounts could be used in multi-customer enviroment. Or should we start to use native mode to serve client computers of different customers via http protocol?

    Monday, March 12, 2012 6:34 AM