KACE Product Support Question

K2000 - Building an RSA

12/30/2015 2186 views
How can I get the RSA's web page to open?
...is there a conversion command for ESX 5.5? Is there a different option for the 5.5. version?

Our RSA is a vm on ESX 5.5
The OVF file was deployed in VCenter by going to File > Deploy OVF template and all appeared to be well.
After configuring networking in the RSA's console, I'm not yet able to open a web page to it and pinging fails. Our network team confirms the RSA's network config is correct and says it should work.

The only thing I've found in the instructions that differs from what we've done is in the steps noted below regarding converting the OVF. I'm not sure if that's required with our current version of ESX 5.5. Or if the command is different than the options shown below.

SOURCE: https://support.software.dell.com/k2000-systems-deployment-appliance/kb/111359 

On the ESX box, convert all the files using VMWare Converter. Use either the following command using the VMWare Converter:

ESX Sever V2.5 and VMWare Converter V3.0.3

vmkfstools -i k2000_remote.vmdk -d thick k2000_remote_site.vmdk

ESX Server V3.5 VMWare comverter V3.0.3:

vmkfstools -i k2000_remote.vmdk k2000_remote_site.vmdk

This process may take around 1 - 2 hours to finish converting.

0 Comments   [ + ] Show comments


All Answers


The K2000 does contain the RSA OVF file which matches the version of software running on the appliance. Updating the K2000 appliance to the latest version (not sure what version you are running, current release is 3.7.120251) the matching RSA OVF revision would be 3.7.113042.

The RSA will have a disk setting to 250GB, this can be updated to larger by creating a virtual disk of desired size on the same cluster as the RSA and setting the RSA to use off-board storage. The appliance itself started at 250GB, then at 12G system I believe the updated that to a 500GB drive. The latest 13G systems have a 1.2TB drive configuration.

Hope that helps with the drive size.

Answered 12/30/2015 by: TheAustinDave
Brown Belt

I don't believe the versions match as you note. One would think they should, but at least in our case, that's not what we saw. I did use your link from your other post and was able to download a current RSA. I'll deploy that one today.

Below is a moot point now that I have the download noted above, but here's the info in case anyone else runs into it....
Our K2000 is Version: 3.7.116629 and was at this version for at least a month or two before I downloaded the OVF from our K2000. We update our K2000 about 4-6 weeks after upgrades are available in most cases. Especially with large updates.

Note the version of our RSA's about window and the prompt for the 3.3 upgrade. If a fairly current K2000 is meant to contain a fairly current RSA, we did not see this.

Answered 12/31/2015 by: murbot
10th Degree Black Belt


After upgrading the OVF file, the RSA was able to be deployed and configured. I checked with Kace prior to downloading the OVF from our K2000 (which is current), but they told me the only way to get the RSA was by downloading through my existing K2000. Which gave me the old OVF. Now after buliding it, I'm prompted to upgrade, but when i click the prompted upgrade link, it takes me to a generic Kace web page and I don't see a download.

Also, this OVF was only 250GB while I was told all they offer now is a 500GB RSA ovf. Someone at "DELL" Kace needs to get their info straight before passing it along. Kace was so much better before Dell improved things.

Answered 12/30/2015 by: murbot
10th Degree Black 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


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