Automatic Deployment binding to wrong NIC/IP

Discussion created by RobPol on Jan 23, 2013
Latest reply on Jun 27, 2013 by Reba Gaines

I am using USM/ADE to deploy the robot to discovered windows machines. They are discovered on the correct management subnet and ADE deploys the robot. The new robots show in my hub but the robot chooses to binds to the wrong IP. Not much use.


Communication Breakdown, It's always the same, I'm having a nervous breakdown, Drive me insane! -- Led Zepplin


After connecting to the robot and editing robot.cfg for the correct IP, bouncing the service, all is good.


Is there a way to tell ADE which IP to use other than building XML files? Building XMLs kinda breaks the ease of discovery, deploy, profit.