I am testing the image capture/build via RSA. I am able to boot a system to the KBE, and everything seems to go as normal while it initializes, but after that I am presented with the deployment client which has an error:

What could be going wrong here? Is there any specific error logged anywhere?

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


Is the Ip address at the bottom of the screen the K2000 server? Do you have enough licenses?
I have seen this issue occur with network drivers, please make sure you have the latest Windows 7 drivers in KBE for you machine.

Answered 09/08/2011 by: cserrins
Red Belt

Please log in to comment

I am getting the same screen and the IP on the bottom of the screen for me is the RSA IP.  Does the Network that the RSA is on still need access to the K2200 box?

Answered 02/20/2013 by: jander32
White Belt

  • Yes, the RSA must be able to make contact with the K2000 to check licensing.
    • This seems to defeat the whole purpose of having RSA's. What if the physical appliance goes down in, let's say, HURRIANCE SANDY!
  • I would agree as this would have be very useful out in the field to reimage a system on the spot.
  • Lets call this an enhancement request..
Please log in to comment

Encountered this error, the cause of this Error not able to contact K2 was due to a WAN optimization appliance setup in between the K2 and RSA at remote sites. No doubt the RSA do get files from the K2 but during deployment of KBE it will stuck with this message. 

Answered 11/27/2013 by: Aaron Cool
Red Belt

Please log in to comment