I experience this same result (hanging) if instead of the script, I just try something like this: Enter-PSSession -ComputerName Server2 If I reboot that remote system, it continues until it reaches another remote system experiencing this problem. Once the script reaches the first server experiencing this problem, it hangs indefinitely (again, I've waited for over 60 minutes). The script block is very small/simple (only a couple of 'Get-WBJob' commands). Invoke-Command -Session $rsession -ScriptBlock
WINDOWS POWERSHELL STARTUP WINDOWS
This is causing a problem with our "morning checks" script that tries to check the last Windows Server backup on multiple servers in a foreach loop using "New-PSSession" like this: $rsession = New-PSSession -ComputerName $Server -ErrorAction Stop It has happened on both Windows Server 20, but I do not remember seeing it happen on any of our 2012 R2 servers. I'd guess at least half of our servers, so at least 40 servers or so. More than 15, but I'm not sure exactly how many.
A reboot might be an acceptable fix if it weren't on servers, and the issue never came back, however it eventually returns after a while (perhaps several weeks later). I've tried starting PowerShell everyway I know how, but no matter what I try, the only fix I've found so far is to reboot the system.
NET, or McAfee that is causing it, but I just don't know. My suspicion is that it's not actually a PowerShell problem, but something else such as. All it does is show the blue shell window with the typical PowerShell startup output of: Windows PowerShellĬopyright (C) Microsoft Corporation.
I've waited for over 60 minutes, but it never fully starts. What would be causing "PowerShell.exe" to hang upon opening on multiple systems?
0 kommentar(er)
