DX Unified Infrastructure Management

Hi,

We need to install Nimsoft robot on around 100 windows and unix hosts. How to have a Nimsoft robot automated installation with embedded IPs of primary and secondary hubs so that once robot starts up, it will automatically point to both the hubs ?

I know in case of unix, minimal can be configured to pass IP of the hub in command line but I need to know the exact command.

Assuming this works, in order to have Nimsoft robots configured on all hosts, we just need to ask domain administrator (in case of windows) to push / install / deploy our Nimsoft robot setup on all windows hosts and with out configuration, whenever Nimbus Controller service starts, it will automatically connect to both primary and secondary hubs.

Thanks & Regards,

Amit Saxena

On Windows at least you can first place a robot.cfg file with the secondary hub information, and then run the installation. This can be done silently with a .iss file supplying the input (including primary hub ip).

I am not quite sure if the same can be done on unix, though.

Regards, Koert

Hi Koert,

Thanks for the information. Could you please describe the same in a bit detail ?

Thanks once again.

Regards,

Amit Saxena

You can also try the methods partially described in this post.

http://forum.nimsoft.com/t5/General-Development/VB-NET-Silently-install-Windows-based-robots/td-p/7037

Some more detail for my previous post:

Placing a robot.cfg file with the secondary hub information:

For example create a file like this:

C:\Program Files\Nimsoft\robot\robot.cfg:

 <controller>
   secondary_domain = TestDomain
   secondary_hub = hub2
   secondary_hubrobotname = server2
   secondary_hubip = 192.168.0.102
   secondary_hubport = 48001
</controller>

Then to run the installation silently, the command line may look like this:

C:\temp\robot.exe /s /a /s /sms /f1"c:\temp\robot.iss" /f2"c:\temp\robot.log"

The first /s and /a options are for the wrapper executable which contains the setup.exe and other necessary installation files (/s = silent, /a = take the following as arguments for the setup command).

The /s /sms /f1"c:\temp\robot.iss" /f2"c:\temp\robot.log" are input to the setup exe (/s = silent install, /sms = wait for installation completion - makes it easier to script the installation, /f1 = specifies the input file for the responses to the setup dialogs, /f2 = specifies a log file for the installation).

The .iss file is created beforehand by running an installation recording on a typical machine with a command like this:

C:\temp\robot.exe /s /a /r /f1"c:\temp\robot.iss"

Note that the dialog sequence in earlier robot installations varied a bit depending on nimsoft components found on the network during installation. This is cleaned up in the latest versions.

Regards, Koert