thanks for the reply Swapnil it pointed me to the right direction (after writing an NSH script). However, I would like to give this BL job to help desk and do not want them access to the depot package but only on the job. how can you have an insertable field for the user and password on the job?

You can use Local properties in your BLPackage to expose inputs that can be overridden/filled in at Job execution time. That would for example allow you to specify which user you want to update.

The limitation IMO is that you cannot use properties in the password field of the user object, which means you would still need to either hard-code the password in the package or allow your operator to edit the package, which brings you back at the initial situation.

You could possibly use a script instead or if you want to stick to the BLPackage, to write an external command in the package.

A last option would be to use the live browse of the server and right click on the user you want to update.

Olivier, That is exactly what I encountered. I did wrote a one line script with a simple

"echo username:password | chpassword" and have custom fields $$username$$ and $$password$$ however it is failing. i ran the script on a box: test_ch_passwd.nsh <username> <password> and works. i am still scratching my head.

I don't think you can use the built-in user object in conjunction with an encrypted property (any property in fact) for the password. That means you need to hard-code the password into the package as opposed to make it available to update at deploy time.