CA UIM Robot Deployment Issue

[Omair_Hasan]

When i try to deploy robot to machine ,  iam unable to select machine from list ..

 

Screen shot attached..

 

Looking for your valuable comments..

 

Thanks

[Anon Anon]

Before you can select a server the collumn credentials must be filled in by running the discovery with credentials.

[Omair_Hasan]

Thanks for comment,

But actually i already discover the machine and i want to deploy robot, i gave the credential when i discover the machine , Screen shots check please

[Anon Anon]

In your second screen shot I can only see the column credentials that is empty!

[Omair_Hasan]

Please now check another scrn shot , i add the target machine credentials..

[Anon Anon]

This extra screen shot is the wmi credential that you give for the discovery.  But the result must be that the Deploy screen has a credential filled in, else you cannot select it.

This could mean that you need an extra credential(s) in the discovery setup

[Omair_Hasan]

Which credentials , can u explain me in detail , if you have any document about how to deploy robot ?...

[Anon Anon]

Once your discovery is done, you must see that credential indicator in the inventory screen (last column); this indicator confirms that the discovery found a corresponding credential in the discovery parameters:

[Omair_Hasan]

[Anon Anon]

This means that you have to give additional or another windows user when performing the discovery (if possible a domain administrator).  Only when the credential sign is found in the Inventory screen it can be selected for deployment.

[Omair_Hasan]

Sory i again add an other machine but , there is any selecting option available,  How to achieve it 

[Phani Devulapalli]

If you are trying to deploy a robot on to NOMAN-PC, looks like that device is not properly discovered as the credentials which you have given during the discovery could be incorrect.  

 

When you are running the discovery , once you get to scopes , make sure you have chosen the correct credentials (look at the check mark under WMI for example) to be used from the credentials windows for that PC you are trying to discover . If the credentials chosen are incorrect, it may not get discovered correctly . Once the discovery is complete (when you see OS and other info) you should be able to deploy the robot from USM

 

[zimou13]

Hi this is the sol:

Your third-party deployment tool must perform the following actions.

Note: If you are not using root access, use either sudo <command> or su -c "<command>". You can also use su to get the root shell, then execute the command.

1. Copy the appropriate installer to /opt on the target system. The Linux installers are:
   • SUSE, SLES, or RHEL:
     nimsoft-robot.rpm
     nimsoft-robot-x64.rpm
   • Debian:
     nimsoft-robot+debian_amd64.deb
     nimsoft-robot+debian_i386.deb
   • Ubuntu:
     nimsoft-robot+ubuntu_amd64.deb
     nimsoft-robot+ubuntu_i386.deb
2. Copy the nms-robot-vars.cfg answer file to /opt.
3. Execute the appropriate command.
   • RedHat, SUSE, or CentOS:To install in /opt/nimsoft, execute:

       rpm -ivh nimsoft-robot.<arch>.rpm

     where <arch> is the architecture of the target system (i386 or amd64).

     To specify the installation directory, execute:

       rpm -ivh nimsoft-robot.<arch>.rpm --prefix=<directory>

     where <directory> is the full path/name of the installation directory.

     The rpm flags function as follows:

     -i installs the software package.

     -v displays a simple status line to show what is being installed (verbose mode).

     -h displays fifty hash marks (#) to show the status as the install proceeds; when all fifty have displayed, installation is complete.

   • Debian or Ubuntu:

       (sudo or root user) dpkg -i nimsoft-robot+<OS>_<arch>.deb 

     where <OS> is debian or ubuntu and <arch> is the architecture of the target system (i386 or amd64).

4. After the installer exits, execute the following to configure the robot:

     cd /opt/nimsoft/install   (sudo, su -c, or root user) bash RobotConfigurer.sh

5. Execute the following to start the robot:
   • RedHat, SUSE, or CentOS:

       /etc/init.d/nimbus start

   • Debian:

       /etc/init.d/nimbus start

   • Ubuntu:

       (sudo, su -c, or root user) initctl start nimbus

Installation is complete.

___________________________

ShowBox VidMate Mobdro