Skip to content

Usage-FAQ.md

Latest commit

 

History

History
145 lines (106 loc) · 6.57 KB

Usage-FAQ.md

File metadata and controls

145 lines (106 loc) · 6.57 KB

Usage FAQ

These are some common questions you might have about this module or errors that you might encounter. If you haven't already done so, you should read the README file. And don't forget the About_PSAutolab file.

I get an error about trying to modify TrustedHosts

The module commands must be able to use PowerShell remoting to configure and test the virtual machines within a configuration. Because there is no Kerberos authentication between the local host and the virtual machines, you need to configure TrustedHosts. If TrustedHosts can't be configured, you will likely encounter errors. You should make sure remoting is enabled on the localhost. Run this command.

Test-WSMan

If you get errors, you may need to enable PowerShell remoting.

Enable-PSRemoting

Ensure that you are running an elevated PowerShell session (Run as Administrator).

NOTE: If your TrustedHosts configuration is managed by Group Policy, it is unlikely you will be able to use this module.

"I get an error about my network connection type being set to Public."

Full error

Set-WSManQuickConfig : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859113" Machine="localhost"><f:Message><f:ProviderFault provider="Config provider" path="%systemroot%\system32\WsmSvc.dll"><f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859113" Machine="tablet"><f:Message>WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again. </f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>
At line:116 char:17
+                 Set-WSManQuickConfig -force
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException
    + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand

Fix

# Find connections with a NetworkCategory set to Public
Get-NetConnectionProfile

# For each connection, change to Private or Domain
Set-NetConnectionProfile -InterfaceIndex 3 -NetworkCategory Private

Enable-Internet fails on New-NetNat

You might get an error like "The parameter is incorrect."

Full Error

New-NetNat : The parameter is incorrect.
At C:\Lability\Configurations\POC-StandAlone-Server-GUI\Enable-Internet.ps1:50 char:9
+         New-NetNat -Name $NatName -InternalIPInterfaceAddressPrefix $ ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidArgument: (MSFT_NetNat:root/StandardCimv2/MSFT_NetNat) [New-NetNat], CimException
+ FullyQualifiedErrorId : Windows System Error 87,New-NetNat

Currently, Hyper-V only supports a single NAT network, you can read more about this here: https://blogs.technet.microsoft.com/virtualization/2016/05/25/windows-nat-winnat-capabilities-and-limitations/. Likely, if you receive the error above, you already have a NAT network created. For example, Docker for Windows creates a DockerNAT virtual switch and NAT network. You can check if this is the case with the Get-NetNat PowerShell cmdlet. If you get back a NAT network object, then you won't be able to create another one for your lab.

The solution is to coordinate a single NAT network so it covers all of your NAT networking needs.

  • That likely means creating a larger NAT subnet that covers the IP ranges of all of your networks.
  • Which also means coordinating IP ranges across apps so they can fall under a single NAT subnet.
  • The NAT subnet cannot overlap with the external network that the host is attached to. If a host is attached to 192.168.0.0/24, you can't use 192.168.0.0/16 as a NAT network.

Here's a visualization from the above limitations article: overlapping prefixes

Refer to this article for help on creating NAT networks: https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/setup_nat_network

List NAT networks, take note of the IP range and subnet

Get-NetNat

Remove an existing NAT network called DockerNAT

Remove-NetNat DockerNAT

Create a NAT network with coordinated subnet

New-NetNat -Name DockerAndLabilityNAT -InternalIPInterfaceAddressPrefix "10.10.0.0/16"

Docker for Windows network settings can be updated from the windows tray icon. Lab network changes require updating both Enable-Internet.ps1 and the Lab.psd1 files.

I want to customize or create my own configuration

The expectation is that one of the included configurations will meet your needs or has been specified by a Pluralsight author. However, are free to modify or create your own configuration. This process assumes you have experience with writing Desired State Configuration (DSC) scripts, including the use of configuration data files (*.psd1) and Pester. Because configurations might be updated in future versions of the PSAutoLab module, you are encouraged to create a new configuration and not edit existing files. Find a configuration that is close to your needs and copy it to a new folder under Autolab\Configurations. Technically, you can put the configuration folder anywhere but it is easier if all of your configurations are in one location.

Once the files have been copied, use your script editor to modify the files. Don't forget to update the pester test. Keep the same file names.

How can I change a VM's timezone?

First, find your desired timezone using one of these techniques:

# Filter all timezones, take the Id property from the desired timezone:
[System.TimeZoneInfo]::GetSystemTimeZones()
[System.TimeZoneInfo]::GetSystemTimeZones().Where({$_.Id -like '*Eastern*'})

# Get your current timezone:
(Get-TimeZone).Id

Next, open the lab's VMConfigurarationData.psd1 in your script editor and change Lability_timeZone per Node.

 @{
            NodeName                = 'Win10Ent'
            IPAddress               = '192.168.3.101'
            Role                    = @('RSAT','RDP')
            Lability_ProcessorCount = 2
            Lability_MinimumMemory  = 2GB
            Lability_Media          = 'WIN10_x64_Enterprise_EN_Eval'
            Lability_BootOrder      = 20
            Lability_timeZone       = 'Central Standard Time' #[System.TimeZoneInfo]::GetSystemTimeZones()
            Lability_Resource       = @()
        }