We've changed the way we build and package our BizTalk apps using Visual Studio Team Service. We used to build our MSI's, bindings and PowerShell deployment scripts and then zip them all into a single Deploy.ZIP package on our on site build server. Now we leave the MSI's, bindings and PowerShell scripts in the Artifacts folder in the cloud, ready for a Release to deploy them.
So today I've downloaded the artifacts for the first time. Chrome has kindly downloaded Artifacts.ZIP for me ready for use. I've unzipped it and copied the contents to my target server. I've then run my deployment PowerShell script.
Well blow me, PowerShell has noticed my files have been download from the internet and now asks me if I trust each and every script! Worse, even if I say I would like to (R)un Once for each script they no longer work because various PowerShell commands are unavailable.
The workaround is simple.
Download the zip file from the Artifacts location. Then open Properties on the zip file. Check the "Unblock" checkbox and click OK. Now you can unzip as normal.
Behold, the extracted files are no longer being considered a top security risk. The prompt goes away and suddenly you are able to run commandlets again. Life is good, but...
What we do is hard.
No comments:
Post a Comment