Unable to install .NET Framework 3.5 remotely on Windows Server 2012 or 2016 using WinRM
Opened this issue · 1 comments
Attempting to choco install -y dotnet3.5 when connected to either Windows Server 2012 or 2016 via a remote WinRM session fails with error output similar to the following:
ERROR: Running ["C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NonInteractive -NoProfile -ExecutionPolicy Bypass -InputFormat Text -OutputFormat Text -EncodedCommand IAAgACAAIAAgACAAJABuAG8AUwBsAGUAZQBwACAAPQAgACQAVABy AHUAZQANAAoAIAAgACAAIAAgACAAIwAkAGUAbgB2ADoAQwBoAG8AYwBvAGwAYQB0AGUAeQBFAG4AdgBpAHIAbwBuAG0A ZQBuAHQARABlAGIAdQBnAD0AJwBmAGEAbABzAGUAJwANAAoAIAAgACAAIAAgACAAIwAkAGUAbgB2ADoAQwBoAG8AYwBv AGwAYQB0AGUAeQBFAG4AdgBpAHIAbwBuAG0AZQBuAHQAVgBlAHIAYgBvAHMAZQA9ACcAZgBhAGwAcwBlACcADQAKACAA IAAgACAAIAAgACYAIABpAG0AcABvAHIAdAAtAG0AbwBkAHUAbABlACAALQBuAGEAbQBlACAAJwBDADoAXABQAHIAbwBnAHIA YQBtAEQAYQB0AGEAXABjAGgAbwBjAG8AbABhAHQAZQB5AFwAaABlAGwAcABlAHIAcwBcAGMAaABvAGMAbwBsAGEAdABlAH kASQBuAHMAdABhAGwAbABlAHIALgBwAHMAbQAxACcAIAAtAFYAZQByAGIAbwBzAGUAOgAkAGYAYQBsAHMAZQAgAHwAIAB PAHUAdAAtAE4AdQBsAGwAOwANAAoAIAAgACAAIAAgACAAdAByAHkAewANAAoAIAAgACAAIAAgACAAIAAgACQAcAByAG8AZw ByAGUAcwBzAFAAcgBlAGYAZQByAGUAbgBjAGUAPQAiAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAIgANAAoA IAAgACAAIAAgACAAIAAgAGMAbQBkAC4AZQB4AGUAIAAvAGMAIABEAEkAUwBNACAALwBPAG4AbABpAG4AZQAgAC8ATgBvAF IAZQBzAHQAYQByAHQAIAAvAEUAbgBhAGIAbABlAC0ARgBlAGEAdAB1AHIAZQAgAC8ARgBlAGEAdAB1AHIAZQBOAGEAbQBlAD oATgBlAHQARgB4ADMADQAKACAAIAAgACAAIAAgACAAIABpAGYAKAAhACQAbgBvAFMAbABlAGUAcAApAHsAcwB0AGEAcgB0 AC0AcwBsAGUAZQBwACAANgB9AA0ACgAgACAAIAAgACAAIAB9AA0ACgAgACAAIAAgACAAIABjAGEAdABjAGgAewANAAoAIAA gACAAIAAgACAAIAAgAGkAZgAoACEAJABuAG8AUwBsAGUAZQBwACkAewBzAHQAYQByAHQALQBzAGwAZQBlAHAAIAA4AH0A DQAKACAAIAAgACAAIAAgACAAIAB0AGgAcgBvAHcADQAKACAAIAAgACAAIAAgAH0A] was not successful. Exit code was '1'. See log for possible error messages.
The installation succeeds if logged in locally (via Remote Desktop) and run from a shell prompt.
This bug is particularly problematic for anyone attempting to provision a machine using Packer as it connects to Windows machines via WinRM. I've noted that Chef has worked around this with its "elevated WinRM" feature, but Packer has no such option.