Kaseya Community

Kaseya VSA Roadmap - July 2015 Recording and Q&A

  • VSA Roadmap presented by Prakash Khot, CTO



    sticky
    [edited by: Brande Schweitzer at 4:14 PM (GMT -7) on Jul 21, 2015]
  • FAQ on Kaseya® VSA™ Roadmap

    ·         How will the deprecation of NPAPI in September 2015 affect Kaseya Live Connect™?

    ·         Since Service Desk will be replacing the Ticketing feature, will there be an automatic process for exporting tickets to the system?

    ·         Will there be additional costs associated with moving to Service Desk?

    ·         How will add-on modules be supported in future Kaseya VSA releases?  

    ·         What is the Certified Technology Alliance Partner (TAP) Program?

    ·         Are TAP modules fully supported?

    ·         Who are the TAP partners?

    ·         What if I would like to suggest a new technology company as part of the TAP program?

    ·         Will my existing add-on investment be protected?  

    ·         How will TAP licensing work?

    ·         When will I need to make the transition for the add-on modules?

    ·         How will the conversion / upgrade work?

    ·         What happens if an OEM Partner does not join TAP?

    ·         When will Kaseya support Microsoft Windows 10?

    ·         Why are the Kaseya VSA releases numbered R9.1, R9.8 and R12? What happened to R10 and R11?

     
    Kaseya Live Connect
     
    Q: How will the deprecation of NPAPI in September 2015 affect Kaseya Live Connect™?
     
    A: A number of the functions in Kaseya Live Connect require NPAPI plugin support.  These components include File Manager, Task Manager, Registry Editor, Event Viewer, VPN, and Command Shell.  Kaseya has been working on a replacement for Live Connect, code-named Hydra, that will provide similar functionality on a state-of-the-art architecture which is no longer dependent on third-party applications.  Hydra will begin its beta test in the fourth quarter of 2015 and will be released as part of Kaseya VSA R12 in January 2016.
     
    Some customers have expressed concern regarding the gap between September 2015 and Hydra’s release date.  The Microsoft® Internet Explorer®, Firefox® and Apple® Safari® browsers have not announced when they will remove support for NPAPI.  Consequently, we anticipate that Live Connect should continue to work properly for the majority of customers using these browsers during this intermediate time period.  
     
    However, Google has announced that Google Chrome™ version 45, to be released in September 2015, will deprecate plugin support for NPAPI.  Customers who use Live Connect via Chrome may want to temporarily use another browser until the release of Hydra.  Customers who must use Chrome may decide to disable automatic updates and remain at Chrome version 43 until Kaseya VSA R12 is available in January 2016.  Kaseya VSA R9.8 will alert customers if the Chrome automatic update feature is not turned off, but we recommend customers turn off automatic updates well in advance of September 2015.  Instructions for turning off automatic updates are provided through a KnowledgeBase article: https://helpdesk.kaseya.com/entries/71391863-KLC-browser-plug-in-support-with-Google-Chrome. 
     
    Finally, Microsoft has announced that Microsoft Edge® will not support NPAPI but they will continue to ship Microsoft Internet Explorer for some period after Edge is released. Microsoft Edge will only affect customers using Microsoft Windows® 10.
     
    Ticketing and Service Desk
     
    Q: Since Service Desk will be replacing the Ticketing feature, will there be an automatic process for exporting tickets to the system?
     
    A: Yes. There will be a method to export the tickets from Ticketing and import them into Service Desk.  No data will be lost.
     
    Q: Will there be additional costs associated with moving to Service Desk?
     
    A: Our goal is for there to be no additional cost to customers related to this change. We are currently finalizing our new pricing structure, and will have more information soon. 
     
    Add-on Modules and TAP Program
     
    Q: How will add-on modules be supported in future Kaseya VSA releases? 
     
    A:  Kaseya is enhancing the way we deliver and support add-on functionality from our partners.  These changes are driven as part of our larger development investment to deliver a modern, focused, and highly flexible architecture for Kaseya VSA to both on-premise and cloud deployments.
     
    Standardizing partner integrations will result in smoother, more dependable execution of their capabilities (as well as quicker access to new features and patches) within Kaseya VSA, and enable Kaseya to quickly onboard new partners in the future.
     
    OEM Partners
    Kaseya believes that an OEM relationship should imply a deeply integrated and fully supported solution delivered via Kaseya VSA to our customers.  Our OEM relationships should represent the best of what both Kaseya and our OEM partner can deliver in order to create tremendous value for our joint customers.  Kaseya has selected two OEM partners starting in September 2015 Kaseya VSA R9.8 release: Heat (formerly known as Lumension) and Kaspersky Labs.
     
    All Other Partners
    At the same time, Kaseya has many customers using other add-on modules based on solutions from partners such as Acronis, Storagecraft, AVG, Malwarebytes, and others.  These Kaseya partners continue to be extremely important to us.  These partners are eligible to participate in our new Certified Technology Alliance Partner (TAP) program to offer integrations with Kaseya.
     
    Q: What is the Certified Technology Alliance Partner (TAP) Program?
    The TAP program is structured partner program that, among other advantages, allows partners to utilize our new RESTful APIs to build plug-and-play apps/modules that function as though they were native to Kaseya VSA.  Kaseya provides new SDKs that create this extensibility on the new Kaseya architecture.  TAP modules will go through streamlined testing to ensure security and integration compliance before the application is launched.  Customers can trust that TAP modules will work seamlessly and that upgrade processes will be straightforward.   The TAP partner will now be able to provide upgrades without dependency on the Kaseya VSA release schedule.  Therefore, customers can have faster access to new partner features and patch releases with less logistical friction.  Learn more about TAP
     
    Q: Are TAP modules fully supported?
    Kaseya will still be the central Support point of contact for TAP modules.  However, we will have improved capabilities to escalate issues directly to the partner if necessary.  Partners will also have immediate and improved visibility to issues within their module and the ability to release patches to address these issues.  Consequently, customers should see improved issue resolution.
     
     
    Q: Who are the TAP partners?
    The TAP program is currently in alpha.  We have approached each of the current add-on product partners, as well as some exciting new potential partners, for participation in TAP.  We will be able to announce the specific partner details later this summer on the community.  We anticipate having partnerships in all the below categories:
     
    Backup & Disaster Recovery*
    PSA Integration
    Advanced Network Management
    Additional Endpoint Security
    Additional Software and Patch Distribution​
     
    *Please note, Kaseya Online Backup (KOB) will be part of CORE Kaseya VSA.
     
    Q: What if I would like to suggest a new technology company as part of the TAP program?
     
    Kaseya wants to use the TAP program to create a rich VSA experience for you.  We encourage you to nominate other partners for the TAP program in the Kaseya Community:  http://community.kaseya.com/xsp/f/127/t/20919
    In a few months, Kaseya will be launching a TAP partner portal that will provide all the details and steps for new companies to become partners. 
     
    Q: Will my existing add-on investment be protected? 
     
    A:   Kaseya expects the TAP partners to honor your current investment. 
     
    Q: How will TAP licensing work?
     
    A:  The invoice for the TAP licenses will come from the partner beginning with Kaseya VSA R12.  In parallel, Kaseya is working to deliver new e-Commerce capability in the same release.  This capability will allow a simple way for customers to manage licenses and add new licenses, including TAP partner licenses.
     
    Q: When will I need to make the transition for the add-on modules?
     
    A: TAP will be released as part of Kaseya VSA R12 in January 2016.  Per typical release, Kaseya VSA Cloud customers should expect to be upgraded to Kaseya VSA R12 in the March 2016 timeframe.  Kaseya will continue to support the last two VSA versions, including Kaseya VSA R9.1 and Kaseya VSA R9.8. On-premise customers can schedule their upgrade when they are ready.  
     
    Q: How will the conversion / upgrade work?
     
    A: Kaseya is deeply committed our customers’ success. We are working closely with each TAP partner to make upgrade paths clear and simple. Our goal is for this to be an easy transition. We are finalizing details of this process specific to each TAP partner and will share it with the community as soon as possible so you are able to plan.
     
    Q: What happens if an OEM Partner does not join TAP?
     
    A: The TAP program is being received positively by all existing partners.  Should an existing OEM solution elect to not participate, our goal will be to provide you with several viable alternatives.
     
     
    Other
     
    Q: When will Kaseya support Microsoft Windows 10?
     
    A: Kaseya VSA R9.1 currently has beta support of Windows 10.  This means that a Kaseya VSA R9.1 audit will report computers that are using Windows 10 and customers can set up a view based on Windows 10.  We have also been reaching out to our OEM partners.  We have confirmed that Acronis works on Windows 10.  We have contacted our security partners and should be getting their versions that support Windows 10 in the next 60 days.  We will roll these versions into our release cycle, and will update this FAQ as appropriate.
     
     
    Q: Why are the Kaseya VSA releases numbered R9.1, R9.8 and R12? What happened to R10 and R11?
     
    A: The old licensing system only supported a one-digit release number.  The new licensing system doesn’t have that limitation. Internally, we have been incrementing releases so that R9.1 corresponds to R10, and R9.8 to R11.  Since we will have transitioned to the new licensing system by January 2016, we can officially name that release Kaseya VSA R12.
     
     
    ###
     
    More questions will be posted as new information becomes available.
     
     
     


    edit
    [edited by: Brande Schweitzer at 4:18 PM (GMT -7) on Jul 21, 2015]
  • Thank you, thank you, THANK YOU . Now THIS is the level of communication we have been expecting from Kaseya. Well done!!

    The above FAQ presents the current state of play very nicely, and I am very pleased with the news I'm hearing and reading about. This is the level of detail we have been craving for, so i'm extremely pleased to see you stepping up to the plate and being active here on the forums.

    Once again, well done and keep up the good work :)

  • Since your planning a redo of Backup and Recovery does that mean your going to phase out KDB?

  • ,

    File and directory backup will be included as part of the core solution (see the roadmap recording at about the 4:30 mark).  Additional information about backup options begins at the 14:35 mark.  

  • ,

    You are very welcome.  We are appreciate the constructive discussions and creative ideas of our community members and we're listening.  Please do keep the conversations rolling in, and thank you for helping to keep our community vibrant.

  • I very much agree with 's sentiment.  Thank you very much for putting this information together!

  • I just stumbled on this article and I have to agree with . It's EXTREMELY refreshing to see this level of communication coming from Kaseya. If this continues I'm sure many of us will feel much more comfortable with Kaseya in the future.

  • , ,

    Thank you.  We're working hard to make improvements.  I know we have more work to do and improvements to make in our communication, but hearing from you all that we're on the right track is very much appreciated.

  • Ditto, Eric and Craig!!!

    I think this is wonderful and I am hopeful Brande can maintain this level of communication!

  • I imagine this information may be updated as time goes by, would you be able to post replies into this thread whenever you make updates to the FAQ? This way any of us who are subscribed to the thread will see you have posted a new reply in the thread and maybe have an idea of what changes to look for in the main post.

  • What updates can we expect for Kaseya Remote Control?

  • ,

    Current planned updates for the next release of the product are available in the Roadmap recording in this thread.   No specific updates to KRC were included in this roadmap, but we are regularly reviewing and evaluating what enhancements can be made to our products, including KRC.  A patch is currently being worked on to address concerns with clipboard data remaining available after a session is terminated, as posted in the thread here:  community.kaseya.com/.../97783.aspx

    Any other feature and function updates to modules, including KRC, will be announced through future roadmap updates.  Specific requests for updates to any module can be submitted for consideration by adding a feature request or voting on existing feature requests here:  kaseya.zendesk.com/.../20135356-Feature-Requests