Kaseya Community

Introducing Kaseya’s New Software Management Module

  • Centralized, automated patch management and software deployment are some of the most important arrows in the quiver of any IT pro, whether you’re managing your company’s machines or you’re an MSP providing services for dozens or hundreds of customers.

    Join us to explore Kaseya’s new Software Management module, which supports both OS patching and 3rd-party software distribution, for VSA. We’ll cover:

    • Cross platform patching and deployment for Windows and Mac
    • Vulnerability Assessments
    • Completely revamped and simplified profile-based configuration
    • Peer-to-peer patch and software distribution
    • And so much more!

    Webinar Details:

    Wednesday, May 17th at 11AM ET/ 5PM CEST or 6PM ET/ 3PM PT

    REGISTER NOW



    sticky
    [edited by: Brande Schweitzer at 9:49 PM (GMT -7) on May 15, 2017]
  • Is there a recording of the webinar? I got pulled away and ended up missing most of the one this morning, and am unable to attend the other times.

  • A recording will be made available within a few business days.

  • Are we going to be notified via email when it's available? I registered but missed the webinar entirely.

    Thanks,

  • Is the recording available yet?

  • found it

    community.kaseya.com/.../86631.aspx

  • I have been playing around with different Software Management (SM) scenarios.

    Does SM support deploying software within a 3rd Party Software Profile if it does not yet exists on a machine.

    If so, how to point to the "always latest" software version of apps and are we gonna be able to access the whole list of supported apps when doing so?

    The KSDU module have that feature and it really eliminates the need for scripting initial application deployments.

    /Ronny



    spellcheck
    [edited by: Ronny Tunfjord at 2:53 AM (GMT -7) on May 23, 2017]
  • We would need to create a lot of scripts to take care of our 3rd party software installs :(

  • Hi It's a patch management software not a software deployment module, so you cannot deploy software with.

    So, this module does not replace KSDU (even with ninite) at all it's complementary for me.

  • Are you sure it doesn't support SW Deployment? The original post states "Kaseya’s new Software Management module, which supports both OS patching and 3rd-party software distribution,"

    Also, the way third party software like java, flash, notepad++, VLC... is patched is generally by redeploying the newer version, not by applying an incremental bug fix.

    I thought this did combine KSDU and Patch Management into one location.

  • Software management includes OS patching for Macs and PCs, 3rd party deployment of software, and 3rd party software update.  OS patching is included with no additional cost.  3rd party deployment and update is licensed separately.

  • What is the ETA for General release of this module?

  • I was told the end of June.

  • So does this mean the relationship with Ninite is over, or will this still use Ninite and I can use the licenced version of Ninite I already have?

  • Hi all,

    I copy Q&A session during the webinar. This will reply most of the questions about new Kaseya module:

    Domanda audience

    D: Will that eliminate the need for Ninite?

    R: The Software Management module does not leverage or require Ninite.

    Domanda audience

    D: Linux support ETA?

    R: Its on our roadmap.  Should be addressed in the next year.

    Domanda audience

    D: so Ninite will no longer be available?

    R: There are no plans to retire Software Deployment so Ninite support will continue to be available

    Domanda audience

    D: Is this a free module or an extra chargable?

    R: OS patching is included.  3rd party patching is licensed.  Tracy will discuss this during the presentation.

    Domanda audience

    D: Hello, will there be a way to also move over existing policies, or will that have to be configured again from the ground up as part of the process?

    R: We are providing some migration tools.  However, the set-up is different so there will be a need to plan the conversion.

    Domanda audience

    D: Are you able to do custom app?

    R: This is not available in the first release.  It is still available in Software Deployment.

    Domanda audience

    D: Can you approve, review and reject on macOS or is it just for Windows?

    R: MAC support is available in Software Management

    Domanda audience

    D: Hello! What version of Kaseya has this capability?

    R: It will be available as an installable module in 9.4.  Tracy will discuss specific VSA patch version for 9.4 availability.  It will be included in 9.5 without requiring additional install.

    Domanda audience

    D: Will there be patching for Linux machines?

    R: Linux support is on our roadmap.

    Domanda audience

    D: What is the performance impact to end users if you patch them when they are logged on?

    R: You can create blackout periods so patching will not occur during those periods.

    Domanda audience

    D: Is this available for VSA cloud, on-prem or both?

    R: both

    Domanda audience

    D: Is it Windows 10 updates supported?

    R: yes

    Domanda audience

    D: how does the 'fabric' mechanism work, is it subnet aware, or does it operate on the basis of the 'connection gateway'?

    R: It works with subnets

    Domanda audience

    D: How do profiles differ from Kaseya policies when it comes to deploying patches? If we already have custom policies in place by client, why would we change to a profile setup instead or in addition to?

    R: Profiles in Software Managmenet are similar to Patch Policies in Patch Managmenet.  SW Managment Profiles also are used to control scans and deployment.  Each has its own type.  These are not the same as Policy Management Policies, but there are new Policy Management objects available to control the assignment of Software Management profiles from within Policy Management Policies.

    Domanda audience

    D: Dumb question - When you say "3rd party patching", what exactly are you referring to?

    R: Vendors other than the OS vendor

    Domanda audience

    D: Do you have an ETA on the roadmap for Linux support?

    R: We will be adding this in the next year.

    Domanda audience

    D: Is this replacing KSDU?

    R: The functionality of KSDU will eventually be all available in Software Management other than Ninite support.  KSDU will continue to exist to support Ninite.

    Domanda audience

    D: What about for SaaS customers?

    R: SaaS customers will have access to it through the Controlled Release process.

    Domanda audience

    D: What restrictions are there when you are using the controlled release vs with the fully integrated version in 9.5

    R: There are no restrictions.  We are just rolling this new module out slowly so we can provide great support.

    Domanda audience

    D: Does that mean cloud customers have to wait until 9.5?

    R: No it will be available in 9.4.

    Domanda audience

    D: Will this completely replace the built in patch process, and if you install this, can you still use built in patch process?

    R: You can still use the Patch Management module, but we recommend using one or the other on a per-machine basis.  Software Management provides increaded capabilities over Patch Management, but Patch Managment module will remain available.

    Domanda audience

    D: Will this completely replace the built in patch process, and if you install this, can you still use built in patch process?

    R: There are no plans to retire the current Patch Management at this time.  We anticipate customers will be moving to Software Management as they see the new features.

    Domanda audience

    D: What is the benefits the new module is offering over ninite?

    R: Software Management patches 3rd party applications in addition to deploying them.

    Domanda audience

    D: When will the software deployment module be retired?

    R: There are no plans at this time

    Domanda audience

    D: Will this show third party vulnerabilties regardless if that module is purchased for updating via Kaseya?

    R: The vulnerbility will be reported even if the 3rd party patching isn't purchased.  The purchase is to actually deploy patches.  This can be turned off.

    Domanda audience

    D: Does this work for all 3rd party patches or is it currently limited to specific software?

    R: There is a list of 3rd party software that we will be patching

    Domanda audience

    D: What about denying specific 3rd party patches?  Such as denying Java 8, but making sure Java 7 is fully patched?

    R: You can use override profiles to 'lock' software at a specific version.

    Domanda audience

    D: I saw the pricing said starting at $0.50/user; does that mean it goes up for more features or it goes down if you purchase XX licenses?

    R: Its .50 / endpoint / month

    Domanda audience

    D: What happens if you set a black out time and the patching begins prior to the blackout window, but it hasn't completed before the blackout window starts?

    R: The cycle will stop at the end of the current patch.  We recommend you set the blackout window to be 30 minutes before your actually time

    Domanda audience

    D: when setting up the scan and analysis is that done by machine group or individual endpoints? or is that controlled through a policy?

    R: You create the profiles and then assign to machines.  You can control profile assignment via policy management to apply to an entire org or group.

    Domanda audience

    D: Is the title list will be auto update?

    R: yes, as new titles are available

    Domanda audience

    D: are we purchasing just for the endpoints we want to enable, or for all endpoints?

    R: OS patching is included.  For 3rd party patching, you purchase the number of licenses you want and then enable the 3rd party deployments on a per-machine basis.  

    Domanda audience

    D: Will there still be improvements/changes made to the Patch Management module, or is that just remaining in-place as-is for now, and focus will be on the Software Deployment module? Will both remain fully supported?

    R: We are not planning to enhance Patch Management.  We will be supporting it for the foreseeable future.

    Domanda audience

    D: what about the ability to approve patches by product rather than classifications?

    R: This is possible using the advanced override

    Domanda audience

    D: Can this do a fresh install of a 3rd party program?  Or is it only managing updates?  For example, can I push Notepad++ with this, or will this only manage the updates for already existing installs.

    R: Yes, deployments are available

    Domanda audience

    D: Can the patch deploy schedule be distributed automaticly so that not all agents are patched at the same time without having to manually set each agent to a seperate time?

    R: Its done by profile.

    Domanda audience

    D: Will the price for 3rd party patching be a one-time purchase, or subscription?  Also, what will the actual cost be?

    R: Licensing for 3rd party patching will start at 50 cents per endpoint per month.

    Domanda audience

    D: when setting up the scan and analysis is that done by machine group or individual endpoints? or is that controlled through a policy?

    R: all of the above

    Domanda audience

    D: will the Software Management module tied into the Policy Management module?

    R: yes