v4.13.0

Author: jdhitsolutions

Authoring-FAQ.md

@@ -59,4 +59,4 @@ Normally, when you run `Wipe-Lab` that should handle everything for you. But if
 
 Another option is to use the `-UseLocalTimeZone` parameter when running `Setup-Lab` or `Unattend-Lab`. This will configure all virtual machines in the lab configuration to use the same time zone as the local host.
 
-### last updated 2020-04-23 18:21:49Z UTC
+### last updated 2020-04-23 18:21:49Z UTC

Configurations/PowerShellLab/VMValidate.test.ps1

@@ -15,7 +15,7 @@ $prefix = $Labdata.NonNodeData.Lability.EnvironmentPrefix
 #turn off progress bars
 $prep = {
     $ProgressPreference = "SilentlyContinue"
-    $errorActionPreference = 'silentlyContinue'
+    $errorActionPreference = 'SilentlyContinue'
 }
 #define an array to hold all of the PSSessions
 $all = @()
@@ -113,11 +113,11 @@ Describe DOM1 {
 
             $admins = Invoke-Command { Get-ADGroupMember "Domain Admins"-ErrorAction SilentlyContinue } -session $dc
             It "[DOM1] ArtD is a member of Domain Admins" {
-                $admins.name -contains 'artd'
+                $admins.name -contains 'artd' | Should Be True
             }
 
             It "[DOM1] AprilS is a member of Domain Admins" {
-                $admins.name -contains 'aprils'
+                $admins.name -contains 'aprils' | Should Be True
             }
         } #if users
 
@@ -292,7 +292,7 @@ Describe SRV3 {
     Catch {
         It "[SRV3] Should allow a PSSession but got error: $($_.exception.message)" {
             $false | Should Be $True
-        }   
+        }
     }
 }
 

Detailed-Setup-Instructions.md

@@ -223,4 +223,4 @@ Wait about 5 minutes and then test again.
 
 If encounter problems getting any of this to work, you are welcome to post an Issue. If you get the module installed, please include the results of `Get-PSAutolabSetting`. If your problem is meeting one of the requirements, we will do our best to help. Although if your computer is locked down or otherwise controlled by corporate policies there may not be much that we can do.
 
-last updated 2020-06-10 13:54:56Z UTC
+last updated 2020-06-10 13:54:56Z UTC

PSAutoLab.psd1

@@ -4,8 +4,7 @@
 
 > **If you are running Pester v5.x you need to be running at least version 4.11.0 of this module.**
 
-This project serves as a set of "wrapper" commands that utilize the [Lability](https://github.com/VirtualEngine/Lability) module which is a terrific tool for creating a lab environment of Windows based systems. The downside is that it is a difficult module for less experienced PowerShell users. The configurations and control commands for the Hyper-V virtual machines are written in PowerShell using Desired State Configuration (DSC) and deployed via Lability. If you feel sufficiently skilled, you can skip using this project and use the Lability module on your own. Note that the Lability module is not owned or managed by Pluralsight.
-This project and all files are released under an MIT License - meaning you can copy and use as your own, modify, borrow, steal - whatever you want.
+This project serves as a set of "wrapper" commands that utilize the [Lability](https://github.com/VirtualEngine/Lability) module which is a terrific tool for creating a lab environment of Windows based systems. The downside is that it is a difficult module for less experienced PowerShell users. The configurations and control commands for the Hyper-V virtual machines are written in PowerShell using Desired State Configuration (DSC) and deployed via Lability. If you feel sufficiently skilled, you can skip using this project and use the Lability module on your own. Note that the Lability module is not owned or managed by Pluralsight. This project and all files are released under an MIT License - meaning you can copy and use as your own, modify, borrow, steal - whatever you want.
 
 **While this project is under the Pluralsight banner, it is offered AS-IS as a free tool with no official support from Pluralsight.
 Pluralsight makes no guarantees or warranties. This project is intended to be used for educational purposes only.**
@@ -21,7 +20,7 @@ The host computer must have the following:
 * Windows PowerShell 5.1
 * A high-speed internet connection
 * Minimum 16GB of RAM (32GB is recommended)
-* Minimum 100GB free disk space preferably on a fast SSD device
+* Minimum 100GB free disk space preferably on a fast SSD device or equivalent
 * An Intel i5 processor or equivalent. An i7 is recommended for best performance
 * Windows PowerShell Remoting enabled
 * You should be logged in with a local or domain user account. The setup process may not work properly if using an O365 or Microsoft account to logon to Windows.
@@ -60,7 +59,7 @@ PS C:\> Get-Module PSAutolab
 
 ModuleType Version    Name                                ExportedCommands
 ---------- -------    ----                                ----------------
-Script     4.11.0      psautolab                           {Enable-Internet, Get-LabSnapshot,...}
+Script     4.12.0      PSAutolab                           {Enable-Internet, Get-LabSnapshot,...}
 ```
 
 Your version number may differ.
@@ -114,7 +113,7 @@ Current configurations will use these names for the virtual machine and computer
 * S12R2
 * S12R2GUI
 
-> Nano Server images have been removed from configurations. These configurations were using the now deprecated version of Nano. Microsoft has changed direction and none of the existing configurations use this new version.
+> Nano Server images have been removed from configurations. These configurations were using the now deprecated version of Nano. Microsoft has changed direction with regards to Nano Server and none of the existing configurations use this new version.
 
 ### Previous Versions
 
@@ -276,7 +275,7 @@ To quickly rebuild the labs from the checkpoint, run:
 PS C:\Autolab\Configurations\SingleServer\> Refresh-Lab
 ```
 
-Or you can use the Hyper-V cmdlets to create and manage VM snaphots.
+Or you can use the Hyper-V cmdlets to create and manage VM snapshots.
 
 ### To Remove a Lab
 
@@ -501,4 +500,4 @@ These are some of the items that are being considered for future updates:
 
 A complete list of enhancements can be found in [Issues](https://github.com/pluralsight/PS-AutoLab-Env/issues).
 
-Last Updated 2020-06-11 15:35:17Z UTC
+Last Updated 2020-06-16 13:30:03Z UTC

README.md

@@ -1,5 +1,23 @@
 # Change Log for PSAutoLab
 
+## 4.13.0
+
+## Add
+
++ none
+
+## Change
+
++ Added more Verbose messaging to `Invoke-SetupLab`.
++ Modified `Invoke-ValidateLab` to import and use the approved version of the Pester module.
++ Updated validation test for `PowerShellLab` configuration to fix error validating domain admin membership. (Issue # 226)
++ Modified `Invoke-ValidateLab` to remove all versions of Pester and then load the version compatible with this module.
++ Updated `Invoke-SetupLab` to use `(Get-TimeZone).id` when using local time zone. (Issue #227)
+
+## Delete
+
++ None
+
 ## 4.12.0
 
 ## Add

changelog.md

@@ -375,7 +375,11 @@ Function Invoke-SetupLab {
     }
 
     if ($UseLocalTimeZone) {
-        $localtz = [System.TimeZone]::CurrentTimeZone.StandardName
+        #modifying this old code since it doesn't translate properly from some
+        #non-US locations. (Issue #227)
+        # $localtz = [System.TimeZone]::CurrentTimeZone.StandardName
+        $localtz = (Get-TimeZone).ID
+        Write-Verbose "Using local time zone $localtz"
         if ($LabData.allnodes.count -gt 1) {
             if (-Not $NoMessages) {
                 Microsoft.PowerShell.Utility\Write-Host "Overriding configured time zones to use $localtz" -ForegroundColor yellow
@@ -396,7 +400,7 @@ Function Invoke-SetupLab {
 
     $LabData.allnodes | Out-String | Write-Verbose
 
-    # Install DSC Resource modules specified in the .PSD1
+    Write-Verbose "Install DSC Resource modules specified in the .PSD1"
 
     If (-Not $NoMessages) {
         Microsoft.PowerShell.Utility\Write-Host -ForegroundColor Cyan -Object 'Installing required DSCResource modules from PSGallery'
@@ -432,7 +436,7 @@ Function Invoke-SetupLab {
         }
     }
 
-    # Run the config to generate the .mof files
+    Write-Verbose "Run the config to generate the .mof files"
     If (-Not $NoMessages) {
         Microsoft.PowerShell.Utility\Write-Host -ForegroundColor Cyan -Object 'Build the .Mof files from the configs'
     }
@@ -445,8 +449,8 @@ Function Invoke-SetupLab {
     if (-Not $NoMessages) {
         Microsoft.PowerShell.Utility\Write-Host -ForegroundColor Cyan -Object "Building the lab environment for $labname"
     }
-    # Creates the lab environment without making a Hyper-V Snapshot
 
+    # Creates the lab environment without making a Hyper-V Snapshot
     $Password = ConvertTo-SecureString -String "$($labdata.allnodes.labpassword)" -AsPlainText -Force
     $startParams = @{
         ConfigurationData   = $LabData
@@ -463,13 +467,14 @@ Function Invoke-SetupLab {
     Write-Verbose ($startParams | Out-String)
     if ($PSCmdlet.ShouldProcess($labname, "Start-LabConfiguration")) {
         Try {
+            Write-Verbose "Invoking Start-LabConfiguration"
             Start-LabConfiguration @startParams
         }
         Catch {
             Microsoft.PowerShell.Utility\Write-Host "Failed to start lab configuration." -foreground red
             throw $_
         }
-        # Disable secure boot for VM's
+        Write-Verbose "Disable secure boot for VM's"
         $VM = Get-VM ( Get-LabVM -ConfigurationData "$path\*.psd1" ).Name
         Set-VMFirmware -VM $vm -EnableSecureBoot Off -SecureBootTemplate MicrosoftUEFICertificateAuthority
 
@@ -665,15 +670,18 @@ Function Invoke-ValidateLab {
     )
 
     Write-Verbose "Starting $($myinvocation.mycommand)"
-    Write-Verbose "Importing Pester module version $PesterVersion"
 
+    #remove pester v5
+    Get-Module Pester | Remove-Module -force
+    Write-Verbose "Importing Pester module version $PesterVersion"
+    #use the module specific version of Pester
     Import-Module -name Pester -RequiredVersion $PesterVersion -force -Global
     $Path = Convert-Path $path
     Write-Verbose "Using path $path"
 
     If (-Not $NoMessages) {
 
-        $msg = @"
+    $msg = @"
     [$(Get-Date)]
     Starting the VM testing process. This could take some time to
     complete depending on the complexity of the configuration. You can press
@@ -684,11 +692,17 @@ Function Invoke-ValidateLab {
 
         Invoke-Pester .\vmvalidate.test.ps1
 
+    Make sure you are using version $PesterVsion of the Pester module.
+    Remove any other versions first and then re-import
+
+        Get-Module Pester | Remove-Module -force
+        Import-Module -name Pester -RequiredVersion $PesterVersion -force
+
     If only one of the VMs appears to be failing, you might try stopping
     and restarting it with the Hyper-V Manager or the cmdlets:
 
-    Stop-VM <vmname>
-    Start-VM <vmname>
+        Stop-VM <vmname>
+        Start-VM <vmname>
 
     Errors are expected until all tests complete successfully.