Calling PowerShell Scripts from Tidal

[Dinesh Sankaranarayanan]

Earlier on, I had troubles getting to invoke a PowerShell 2.0 script from Tidal. So I thought of documenting it for future reference to others who may need it.

The following job definition screen from TES 6.1 shows

1. Execution policy needs to be bypassed using the -ExecutionPolicy bypass switch. This is required due to the additional security features in PowerShell

2. Path to the script is provided using -File option

3. Three parameters being passed to the PowerShell script - namely Prefix, FeedFileName and InputFolder

Happy scripting !

[Dave.Carnahan]

Also, if you can RDP into this server, invoke PowerShell and issue the command -

  Set-ExecutionPolicy -ExecutionPolicy RemoteSigned <CR>

A pop-up will appear and you need to answer 'yes' to change the execution policy, then your issue above is resolved.

PowerShell (out of the box) requires you to change the execution policy (or go through what you're describing above).

Do the above one time, and this command changes PowerShell for any further sessions.

Also for remote PowerShell jobs, climb into PowerShell and ask -

   Help About_Remote_Requirements

about the permissions and requirements to perform remote PowerShell jobs....

[Dave.Carnahan]

It's unfortunate that Tidal doesn't permit your PowerShell cmdlets to be recognized in the Job Command Parameter field of a Tidal job (for 64-bit Tidal agent servers).

This makes for much more work at your site by creating the need to distribute, keep track and maintain extra scripting files, instead of centralizing your source code.

 <thumbs down>  

...

8^(