"Run as Another User" password limitation

I've noticed when setting up a external job (.exe) that the "Run as Another User" has a limit of 10 characters. Is there a way of changing this? The accounts I use have 14+ characters for the password.

Thanks in advance for any help

Yes, it is currently a limitation. But there exists a simple script based workaround. Create a JAL script job executing RunAsUser command or RunAsUserAndWait command. These commands support passwords of any length.

Ok, I can do that but does it send the job encrypted or in clear text across the network? This is a job that i'm running on a agent and we have strict security procedures.

The job definition is sent in a binary format as binary stream.

On the other hand, if you want, you can simply keep the job definition on the remote system and just trigger that job run using RemoteJobEnable or using another job to kickof that job RunRemoteJob and tell it to execute the job (local to the remote) with passwords. In the first case the remote job can be setup with all day schedule and run every minute automatically disabling itself after each run. There are lots of options, but I am not really sure which would be best for you as I don't know what kind of processing are trying to automate.

Thanks for the info, I didn't even think of that as an option. Great tool, having fun learning it and I appreaciate the info you've given me.