1 of 1 people found this helpful
for nsh jobs to pickup the AP, you must configure the nsh client on your appservers to use the nsh proxy. so:
1 - ensure a nsh proxy is running on your appserver(s)
2 - add 'appserver_protocol=ssoproxy' in the secure file on your appserver(s) and restart the appserver service.
Bill, thanks for your response.
I'm just wondering if nexec command execution on a different server than the target server of the NSH job will utilize the AP to execute the command as well?
Target Server: win1
1. get FQDN property from win1 (target)
2. nexec scom1 "D:\apps\stopMonitoring.ps1" "<FQDN>"
Is the script in step 2 also executed using AP on the scom1?
it depends - if the nsh client the script is running from is configured to use the nsh proxy and you have bladelogic creds then yes.
to pickup the AP nsh must connect through a NSH Proxy.