• Replies 2 replies
  • Subscribers 16 subscribers
  • Views 1894 views
  • Users 0 members are here
Options
Related

Desktop Authority Preproduction environment

swapnamali82
over 3 years ago

Does anyone here who still uses Desktop Authority have a way to test new releases in a 192.168.1.254  environment before deploying the client to everyone? 10.0.0.0.1

  • over 3 years ago

    Hello,

    Thank you for your post. Yes, there is a way to have two different versions of KDA (KACE Desktop Authority) running in parallel for testing without touching the production environment. Please see our knowledge article called How to configure a Member Server Scenario, link: https://support.quest.com/kace-desktop-authority/kb/sl4652/. In case you need further assistance with this configuration please do not hesitate to open a service request in our support portal at https://support.quest.com/contact-support and we will be more than glad to help you.

    Kind regards,

    Jorge Corrales.

  • 15 days ago

    Yes, if you're still using Desktop Authority, setting up a preproduction environment is a smart way to test new releases before full deployment. You can mirror your production setup on a separate VLAN or subnet like 192.168.1.254 to safely test configurations, scripts, or client updates without affecting end users. Some even use loopback or internal IPs like 10.0.0.0.1 for isolated testing. Just like how you'd want to check Wendy’s Frosty Canada menu before trying a new flavor, testing in a preproduction setup ensures everything works smoothly before a wide rollout.