We recently installed a Kace RSA running on VMWare vSphere.

We were able to link to our main KBox 2000 with no issues.

We were using the driver feed workaround, and ran the driver feed syncronizer to sync those driver between the KBox 2000 and the RSA.

We have a scripted Windows 7 image that works fine on the Kbox, but not when deploying from the RSA.

PXE boot works fine - we choose our default KBE.

It loads the KBE iso. It starts running the scripts.

Maps drives to the RSA, then gets to the mshta y:rpc_upload_inventory.hta and hangs.

We see the white screen that says "Logging into server..." and eventually it times out. (During the Launching Deployment client.) and says "An error occured while contacting the server.".

Any ideas?


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Any thoughts or suggestions on this? Has anyone run across anything similar?


Answered 01/25/2012 by: dmontgomery
Senior Yellow Belt

  • Were you able to resolve this? I am getting the same error, but only on my x86 KBE.
  • Our issue was tied to the way the RSA's push out and communicate back to the primary server. In order to push out anything from a Kace RSA, the client must do an "inventory upload" not to the RSA, but to the "home" Kace server. I'm sure this is done for licensing reasons, but it does restrict the functionality of the RSA's a bit. We work in very remote areas, and it's not always feasible for us to get Internet/VPN access set up first, but it's what we're currently working with.
Please log in to comment
Can you access the main K2000 server from that network ?

It's uploading the inventory to that as far as I understand, so that could be the problem I guess.

I haven't heard about the problem before though
Answered 01/27/2012 by: rmeyer
Second Degree Blue Belt

Please log in to comment
That's what Kace support may be indicating as well.

We are trying to have a portable Kace RSA that we can take to a remote site and use to deploy our systems before connectivity is established via VPN back to our main office. So in testing we have been getting everything in sync between the K2000 and RSA, turning on the DHCP, and removing from our network and doing isolated testing for just the RSA and the desired client.

It seems like Kace might not be able to do what we're looking for in this instance. :/

Answered 01/27/2012 by: dmontgomery
Senior Yellow Belt

Please log in to comment
Often this either not enough memory on the computer, or a nic driver conflict (same nic in kbe multiple times).
Answered 01/29/2012 by: cserrins
Red Belt

Please log in to comment

I have run into a very similar issue to this. Specifically with the Dell e6420. With the e6420, it was a matter of updating the BIOS as it had some issues with the A06 bios booting PXE. 

Best bet, check and see if there are known issues, and try upgrading the BIOS.

Answered 10/29/2013 by: Finire
White Belt

Please log in to comment