Document potential issue with PowerShell progress bar

Since PowerShell subprocesses don't inherit the setting for
`$ProgressPreference`, it's probably a good idea to set this variable to
`SilentlyContinue` globally when using the WinSSH communicator.

This commit also fixes a formatting issues with the list of supported
Windows guests.
This commit is contained in:
Jeff Bonhag 2020-03-10 16:13:49 -04:00
parent dbec9ae68c
commit 1e6c98f539
No known key found for this signature in database
GPG Key ID: 32966F3FB5AC1129

View File

@ -178,12 +178,13 @@ can take many seconds.
## Windows Boxes
Supported Windows guest operating systems:
- Windows 7
- Windows 8
- Windows Server 2008
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows 7
- Windows 8
- Windows Server 2008
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
Windows Server 2003 and Windows XP are _not_ supported, but if you are a die
hard XP fan [this](https://stackoverflow.com/a/18593425/18475) may help you.
@ -236,6 +237,26 @@ netsh firewall add portopening TCP 5985 "Port 5985"
winrm set winrm/config/listener?Address=*+Transport=HTTP @{Port="5985"}
```
### Optional WinSSH Configuration
When using the WinSSH communicator, you may run into an issue where a PowerShell
command can't display a progress bar. A typical error message might look like:
```
Win32 internal error "Access is denied" 0x5 occurred while reading the console output buffer.
```
In order to prevent this, we recommend setting `$ProgressPreference = "SilentlyContinue"`
in your box's PowerShell profile:
```
if (!(Test-Path -Path $PROFILE)) {
New-Item -ItemType File -Path $PROFILE -Force
}
Add-Content $PROFILE '$ProgressPreference = "SilentlyContinue"'
```
## Other Software
At this point, you have all the common software you absolutely _need_ for