/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Connecting Two KACE K1000s

05/05/2016 636 views
Is there a way to connect two K1000s on one domain and have them share information? Currently I am setting up a virtual K1000 running 6.3 as I have several helpdesk queues with JQuery customization that can't be upgraded to 6.4.  I have a new appliance running 6.4 that will handle patching, etc.  I'd like for a ticket in the IT Helpdesk queue on the 6.3 server to show up on the 6.4 server inventory information where you can see previous tickets worked on that workstation.  

My original plan was to have the IT helpdesk queue on the 6.4 server and a rule would pass the tickets submitted on the 6.3 server (the helpdesk ticketing site for all queues) to the 6.4 server via an email.  The issue with this is the tickets when created on the 6.4 server will have a different ticket number than the one issued by the 6.3 server.

We have 26 different queues with customization and so we can't afford to go to 6.4 and loose those features at this time which is why we are considering this. 
1 Comment   [ + ] Show comment

Comments

  • Each KBOX is it's own separate world. With SSO they can join a domain now but in general, they don't share information between each other.

All Answers

0
There is basically no way to do this except for the email method you describe.  

Keep in mind that you can't keep the same ticket number even if you were changing queues on the same K1000.
Answered 05/05/2016 by: jknox
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ