1 of 1 people found this helpful
Shankar, instead of standard ACL configuration, you can implement Automation Principal (user Guide for more info). Basically with Automation Principals, you can set the job to run as any local or domain user, rather than running as BladeLogicRSCD user impersonating the permissions of the mapped user. Automation Principal is configured in the RBAC, ALCs do not need to be pushed.
Another option is to throw psexec into your mix and use it to execute your scripts as a domain user. using this method you may be exposing the username/password in clear text, so just a warning there..