Deploy Powershell using Powershell - break the branch you are sitting on. #25651
inoculator
started this conversation in
Enhancements
Replies: 1 comment 3 replies
-
|
Are you deploying the MSI? If so, the Install the MSI package from the command line document may be helpful. Have you tried using this method to deploy it with remoting enabled? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I know, that this feature has been requested a while ago, but the chain drained into the 6 month auto close.
Scenario:
Isolated large IT Environment with no internet access.
Powershell 7 deployed by a remote script from a central script.
PSRemoting is set to 1 (on).
While some previous versions of 7.4 and up had no such issue, 7.5.1 seems to update something in PSRemoting and restarts the WinRM service on purpose.
This breaks the install/update process, that is launched using "invoke-command -computer $remoteComputer" and corrupts the update itself.
Is there any way to keep all Powershell processes running during update and just flag the system to "reboot required" on success?
On a Linux system I do not have such issues and in worse case a "screen" session to unlink main process from subprocess. But Windows does not have such a terminal oriented engine -neither does PWSH of course.
To summarize: some sort of argument "/WinRMNoRestart" o.s. would maybe help.
any thoughts?
br
Carsten
Beta Was this translation helpful? Give feedback.
All reactions