How to Setup a K2000 RSA on an ESX Server

Greetings everyone, Recently I've been working on getting our Remote Site Appliances set up for our offices and after creating this guide I thought I would share it with the good folks at ITNinja. While this isn't a generic guide for every situation on setting up a RSA on an ESX, it's my hope that people in similar situations to myself will find this guide helpful. Follow the steps below to create a KACE Remote Site Appliance on an ESX server. This allows you to manage computer inventory, deploy software and image computers even across the world.

    1. Make sure you have the latest RSA OVF files. At the time of writing it’s 3.4.62457. You can find the location to download the latest OVF HERE.
    2. Copy the OVF file and vmdk files over to the site you’re planning on to deploy the RSA to.
      1. I.e. if you’re deploying to a geographically remote site , copy the OVF files to the file server prior to trying to deploy the template.
    3. Open up vSphere and log into the ESX server you want to deploy it on and choose File -> Deploy OVF Template. When it asks for the source paste the location and file name of the OVF file that you copied over in Step 2.
      1. i.e. \\UKSERVER\Software\K2000 RSA 3.4\k2000_extender_3.4.62457.ovf
    4. Click Next on the OVF Template Details page. Then name the RSA along this naming scheme: SITEVMRSA and click next.
      1. i.e. UKVMRSA, INVMRSA, KOVMRSA, etc.
    5. Select the datastore you’ll use then click next.
      1. You’ll want to double check with the system admin or IT manager to make sure you’re good to carve out 250GB+ for this RSA.
    6. Choose Thin Provision and click Next. Click Next on Network Mapping as well.
    7. Don’t check “Power on After Deployment” and click finish. It will now build the RSA server. This may take around 15-20 Minutes
    8. Select the RSA server in vSphere and choose Edit Virtual Machine Settings. Then change the Network Adapter’s Network Label if needed. Click OK to close. And power on the RSA.
    9. Open the console and when prompted for the username enter konfig and when prompted for the password enter konfig. (These are the default credentials for the RSA)
    10. When asked for a language make sure English is highlighted and hit enter. (Unless English isn't your language of course)
    11. When prompted for the network setup follow this guide:
      2. Domain Name: Your Domain
      3. IP Address, Default Gateway, Subnet Mask
      4. Leave Network Speed as Auto-negotiate
      5. Primary DNS: IP address of local DC (i.e. KOVMDC01 = 172.X.X.X)
      6. Secondary DNS: HQ DNS server: 172.X.X.X
    12. Tab down to the bottom and hit save.
    13. Pull up your browser and type in rsaserver/login (i.e. kovmrsa/login or invmrsa/login) (Don't forget you need a DNS entry to hit it like this, otherwise you'll need to use the IP address in step 11.3.)
    14. Accept the End User Agreement.
    15. Login with username admin password admin. (These are the default credentials)
    16. Click the Alert that leads you to Registration and Licensing. Click Edit. Enter Company Name, Organization Name is set to the name of the site (i.e. Zeeco India, Zeeco Asia), and put in the KACE Administrator’s email address. Send Crash reports to KACE.
    17. Click Add License Key. Input the License you received for your K2000 then Save.
    18. Log back in and click the alert to change the time settings. Select the Time zone closest to the location of the site.
    19. Then go to Settings & Maintenance -> Kace Linking and enable KACE Linking. The default options are fine.
    20. Go to Control Panel -> Managed Linked Appliances -> Choose Action -> Add New Linked Appliance. Input k2000name.domainfor the host name and paste in the Linking Key from the K2000.
      1. For the Linking Key you’ll need to log in to the K2000 go to Settings & Maintenance -> KACE Linking and copy the linking key.
    21. Log in to the K2000 and go to Settings & Maintenance -> Managed Linked Appliances -> Choose Action -> Add New Linked Appliance. Input rsaserver.domainand paste the linking key from the RSA Server.
      1. For the Linking Key you’ll need to log in to the RSA and go to Settings & Maintenance -> KACE Linking and copy the linking key.
    22. When linking the remote site to the main K2000 use rsaserver.domain this is due to KACE needing to do a reverse lookup so without the domain it doesn’t recognize it.
    23. In the K2000 go to Deployments -> Remote Sites -> Choose Action -> Add New Remote Site Appliance -> Select the remote site you just linked. In steps 20 and 21. Then click Next.
    24. Input Site Remote Site K2000 in the notes, set the update scheduling to go through every day at 12 PM. Then checkmark the installations and boot environments you want to bring over. Click Save and Sync.
    25. Go to the DHCP server for that location and under IPv4 server options set Option 66 to the IP address of the RSA server and then set Option 67 to kbox2000.0
    26. At this point the server will sync and you’ll be ready to use your Remote Site Appliance!


So there you have it! I hope this will help others in a similar situation. If anyone has any questions or suggestions please don't hesitate to comment and let me know!


  • Your title says K1000 when your title should say K2000. - darkhawktman 11 years ago
    • Haha I can't believe I did that. Thanks, I've changed it. - samzeeco 11 years ago
  • hi can u tell me whats '100 Continue' means?
    is that a firewall problem?

    can you tell me the ports i have to open for the rsa?

    sorry for my english! - blackbyte 11 years ago
  • I didn't happen to run into that error myself. Where are you seeing it? In the VM console on the RSA? When you try to navigate to the RSA Website? - samzeeco 11 years ago
  • I had to use the IP of the rsa to link to the 2000 and i didn't need my dell key but other that that this was extremely helpful! - Matthew.edler 8 years ago
  • Thanks samzeeco! - andr3w 7 years ago
This post is locked
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