waithidden { pathname of file ((it as string) of value "Path" of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell" of native registry) } -ExecutionPolicy Bypass -File "C:\*****\***.ps1"
This is likely more a problem with the powershell script than with bigfix. The script may not run correctly in the environment of the LocalSystem account.
Common issues we’ve seen here before include
there’s no user interface to the service account. If you’vre trying to popup a window, we won’t see it.
the LocalSystem account is not the same as a logged-on-user account. If you are dealing with the HKEY_CURRENT_USER registry path, Desktop folder, Documents folder, or something along those lines, get ready for complexity.
I don’t have enough information to try to guesswhat your powershell script is attempting.
waithidden { pathname of file ((it as string) of value “Path” of key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell” of native registry) } -ExecutionPolicy Bypass -File “c:\IBM\bdsv5.ps1”
One script c:\IBM\bdsv4.ps1 (it has code to invoke sqlcmd to run query for databases per instance of sql server and it creates a single file with all of this information)
As the fist script needs to run with a specific domain user account I created another ps script c:\IBM\sqlquery.ps1 to run the first script with that credentials: