SAPIEN Technologies

Hi, another finding related to this issue: I created a package and when I tried to execute it I received an "access denied" error. I copied the file into the same directory and the copy worked. I compared the security permissions of the files and recognized that the package created by Powe...

Hi, I want to package a script as Windows exe. My sample code: $script:ExitCode = 2 $global:ExitCode = 3 Packaged with "V3 Host (Command line) x64" : PS C:\Test> .\TestExit.exe;$?;$LASTEXITCODE False 3 Packaged with "V3 Host (Windows) x64" : PS C:\Test> .\TestExit.exe;$?;$LASTEXI...

Hi Sam, I work on a similar script: Some of our field staff use an application which needs regular updates. The update process needs to be elevated for correct execution. The staff has simple user account with no admin permission. So I need a program that can be elevated without knowing the credenti...

Hi Alexander, it doesn't matter what mode - it's all the same. But a fortunate coincidence brouhgt me forward. Let me explain: Today I worked at my company on my project and I thougt that it could be a good idea to convert my psf file into a project. I created a new form project and placed the proje...

Additiononal Info: A local account is used. This happens with my privat installation with Windows 7 Pro x64 and also with my installation at work (4.1.57) on Windows 7 Enterprise x64. I can't use alternate credentials to start a process in any way: no packaging with impersonation no packaging with R...

My environment: Windows 7 x64 PowerShell Studio 4.1.61 I tried to use the runas and impersonate features of the packager and recognized that the do not work in my sample. I then made a simple test case with the credential object: $username = "Test" $secstr = ConvertTo-SecureString -String ...