This has to be done in 2 steps:
pu -u administrator -p controller probe_verify
pu -u administrator -p controller probe_activate
Open a command window and change directory to the 'bin' folder to run the command.
C:\Program Files (x86)\Nimsoft\bin>pu -u administrator -p <password for UIM administrator> controller probe_verify hdb
C:\Program Files (x86)\Nimsoft\bin>pu -u administrator -p <password for UIM administrator> controller probe_activate hdb
Note: the above is used when the pu tool is making the change at the local system. If it is to update at a remote robot the full UIM path must be used, and it is case sensitive. This can be found in the IM console by selecting the target robot and it will be shown as the Address for controller. Example:
Be sure the user (if not administrator) has the correct ACL's:
You need to enable 'Basic Management' in the user's ACL
This is how validation works:
When a probe is distributed to a robot, the controller creates a magic_key which is a combination of the robotname and the checksum of the probe's binary (stored in the controller.cfg).
When the robot starts up, the controller will validate this magic_key for the probes that shall be started.
To correct any Validation Errors, you have to validate the probe manually:
(Select the probe and choose rt-click->Security->Validate->Yes).
...or via pu command if necessary.
keywords: probe utility re-validate revalidate command security verify probe_verify Error validation validate
Please Update This Required Field