If the scheduled command is configured with the encoded password instead of the plain text one, keep in mind even if this is the correctly encoded password, the command will not run because the gateway will assume it is the plain text version and encode it again.
It is a common misunderstanding that you have to specify a password under the probe advanced tab.
You can provide the password in plain text as an argument in the scheduled command. You can refer to the xml example attached wherein a scheduled command calls a script on the netprobe.
Based on the example given, you can see that the password "hello" is set as argument 2 in the scheduled command. Then Argument 1 is the actual command to be run which is "c:\tmpSapphireMain.exe" based on sample command xml.
Also remember that the password is always provided as the last argument so if the actual command already had more than one argument itself, then the password to be sent would need to be set as target argument number that was one greater than this number of arguments.
Before sending the command to be executed in the netprobe, crypt is called with this plain text password and the salt for that specific netprobe.
The salt is the first two letters of the encoded password that has been set for the netprobe (the netprobe sends its "salt" so that the gateway knows what to use).
The final encoded result of crypt is sent across the network.
On the netprobe side the encoded password coming from the network is compared against the encoded password that has been set on the netprobe side.
There are two main ways to set the password on the netprobe side.
1) Via the GSE in the advanced tab of the netprobe
2) Via setting the ENCODED_PASSWORD environment variable, which overrides whatever has been set in the