Otto Kucera Posted April 26 Posted April 26 We try to get the client based launcher working. I enabled logging in the PSLauncher.ps1 script. The browser runs the PSlauncher and that the powershell script. PSLauchner.ps1 [...] #----------------------------------------------------------------------------------------------- #Define global variable for logging #----------------------------------------------------------------------------------------------- [string]$LogFile = "c:\temp\PSLauncher.log" [string]$Global:LogDetail = "" [bool]$LoggingEnabled = $true #Logging example $Global:LogDetail += (Get-Date -Format "yyyy-MM-dd hh:mm:ss").ToString() + ' Add custom logging data here.' + "`n" [...] PSLauchner.log 2024-04-26 07:40:32 Add custom logging data here. 2024-04-26 07:56:38 Add custom logging data here. 2024-04-26 07:56:57 Add custom logging data here. 2024-04-26 07:57:39 Add custom logging data here. 2024-04-26 07:57:42 Add custom logging data here. It seams the every stops their. Nothing happens ... We checked the virus scanner, etc. Does someone have an idea why putty, mstsc doesn't get started. Thanks, Otto
Otto Kucera Posted April 29 Author Posted April 29 It seams that we have a collision with our security policy's. [...] add-type @" using System.Net; using System.Security.Cryptography.X509Certificates; public class TrustAllCertsPolicy : ICertificatePolicy { public bool CheckValidationResult( ServicePoint srvPoint, X509Certificate certificate, WebRequest request, int certificateProblem) { return true; } } "@ [System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy [...] I removed this section signed the script with our PKI. But now the script doesn't get executed. How can I sign the script with passwordstate? Thanks. Otto
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now