SAPIEN Technologies

To help you better we need some information from you. *** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. *** Product, version and build: PowerShell Studio ...

Working perfectly with v5.4.143
Thankyou!

Couldn't find any code changes. Also: The script Runs (Ctrl+F5) without any errors. The script Debugs (F5) without any errors if there are no breakpoints set. I've still got a lot of code to add to this script & some of it is going to be easier if I can step through it. Can you point me towards ...

Oops! That seems to have broken it. I'm stepping through (F11) from an early break-point. Then: ERROR: Ambiguous match found. Process-ToolOrder.ps1 (90, 2): ERROR: At Line: 90 char: 2 ERROR: + $command.Connection = $dbConn1 ERROR: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ERROR: + CategoryInfo : OperationSto...

To help you better we need some information from you. *** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. *** Product, version and build: PowerShell Studio ...

Ah - just checked a bunch of MS scripts and they are signed with a Microsoft cert.
Maybe I need to figure out why aren't being trusted by my PC.

Hi, Sorry - what I meant was that it's all the scripts from external sources that seem to need signing, e.g. scripts from NuGet, scripts that came with Microsoft Exchange management tools etc. I guess I should write a script to hunt them all down & sign them. All of the scripts & executables...

Hi, Sorry for the delay (big Exchange migration happening). In fact it was while trying to figure out what was up with the new Exchange Management Shell, that I realized it was the execution policy that was causing all of my problems. It was set (via group policy for the domain) to AllSigned. I gues...

Product, version and build: PowerShell Studio 2017 v5.4.139 64bit Operating system: Windows 7 SP1 64bit PowerShell Version: 5.1.14409.1005 Whenever my scripts get analyzed in PowerShell Studio I get a message, in the debug panel, similar to the following: >> Analyzing Script (Fix-BadShortcuts.ps1) ....

Excellent advice.
Thank you very much for your time!

This phone book project has proved so popular here that I think it's definately worth me spending the time to get it right.