v5.1.0

Author: jdhitsolutions

Configurations/PowerShellLab/Instructions.md

@@ -38,87 +38,87 @@ You could use this configuration that calls for a simple domain environment.
 
 To run the full lab setup, which includes Setup-Lab, Run-Lab, Enable-Internet, and Validate-Lab. You should run all commands from the directory with the MOF and psd1 files.
 
-```powershell
+```shell
 PS> Unattend-Lab
 ```
 
 To run the commands individually to setup the lab environment:
 
 Run the following for initial setup:
 
-```powershell
+```shell
 PS> Setup-Lab
 ```
 
 To start the Lab, and apply configurations the first time:
 
-```powershell
+```shell
 PS> Run-Lab
 ```
 
 To enable Internet access for the VMs, run:
 
-```powershell
+```shell
 PS> Enable-Internet
 ```
 
 To validate when configurations have converged:
 
-```powershell
+```shell
 PS> Validate-Lab
 ```
 
 Or you can run the Pester test directly
 
-```powershell
+```shell
 PS> Invoke-Pester vmvalidate.test.ps1
 ```
 
 ## To Stop and snapshot the lab
 
 To stop the lab VMs:
 
-```powershell
+```shell
 PS> Shutdown-lab
 ```
 
 To checkpoint the VMs:
 
-```powershell
+```shell
 PS> Snapshot-Lab
 ```
 
 To quickly rebuild the labs from the checkpoint, run:
 
-```powershell
+```shell
 PS> Refresh-Lab
 ```
 
 ## To Patch a lab
 
 If you want to make sure the virtual machines have the latest updates from Microsoft, you can run this command:
 
-```powershell
+```shell
 PS> Update-Lab
 ```
 
 Because this may take some time to run, you can also run it as a background job.
 
-```powershell
+```shell
 PS> Update-Lab -AsJob
 ```
 
 ## To remove a lab
 
 To destroy the lab to build again run:
 
-```powershell
+```shell
 PS> Wipe-Lab
 ```
 
 You will be prompted for each virtual machine. Or you can force the removal and suppress the prompts:
 
-```powershell
+```shell
 PS> Wipe-Lab -force
 ```
 

Configurations/PowerShellLab/PostSetup/README.md

@@ -4,29 +4,29 @@ The PowerShell scripts in this directory can be run after the lab setup is compl
 
 Usage of these scripts is completely optional and are provided for your convenience. You may elect to manually accomplish these tasks from the PostSetup folder. For any installations to the Windows 10 client, you should launch an interactive session first to the virtual machine with the credential you intend to use to force a profile creation.
 
-```powershell
+```shell
 vmconnect localhost Win10
 ```
 
 ## Install-SysInternals.ps1
 
 Use this script to download the SysInternals suite from Microsoft. All of the files will be stored in a new folder, `C:\Sysinternals`. It is assumed you will only need to run this for the client virtual machine.
 
-```powerShell
+```shell
 .\Install-SysInternals -VMName win10 -credential company\administrator
 ```
 
 If you already have an existing PSSession to the virtual machine you can use that instead:
 
-```powershell
+```shell
 .\Install-SysInternals -session $sess
 ```
 
 ## Download-Git.ps1
 
 This script will download the current Windows version of the git setup file. The file will be saved to the root of C:\. You will need to manually setup and configure git in the virtual machine.
 
-```powershell
+```shell
 .\Download-Git -VMName win10 -Credential company\artd
 ```
 
@@ -36,7 +36,7 @@ If you already have an existing PSSession to the virtual machine you can use tha
 
 This script will download and install the current version of Visual Studio Code. The file will be saved to the root of C:\. It is assumed you will run this for the client virtual machine.
 
-```powershell
+```shell
 .\Install-VSCode -VMName win10 -credential company\aprils
 ```
 
@@ -47,7 +47,7 @@ Once installed, you can logon as and finish configuration such as installing the
 
 If you want to restart all of the virtual machines, use a command like this:
 
-```powershell
+```shell
 Get-VM Dom1,Srv*,Win10 | Stop-VM -force -passthru | Start-VM -passthru
 ```
 

Configurations/SingleServer-2022/Instructions.md

@@ -14,86 +14,86 @@ Administrator password is P@ssw0rd.
 
 To run the full lab setup, which includes Setup-Lab, Run-Lab, Enable-Internet, and Validate-Lab. You should run all commands from the directory with the MOF and psd1 files.
 
-```powershell
+```shell
 PS> Unattend-Lab
 ```
 
 To run the commands individually to setup the lab environment:
 
 Run the following for initial setup:
 
-```powershell
+```shell
 PS> Setup-Lab
 ```
 
 To start the Lab, and apply configurations the first time:
 
-```powershell
+```shell
 PS> Run-Lab
 ```
 
 To enable Internet access for the VMs, run:
 
-```powershell
+```shell
 PS> Enable-Internet
 ```
 
 To validate when configurations have converged:
 
-```powershell
+```shell
 PS> Validate-Lab
 ```
 
 Or you can run the Pester test directly
 
-```powershell
+```shell
 PS> Invoke-Pester vmvalidate.test.ps1
 ```
 
 ## To Stop and snapshot the lab
 
 To stop the lab VMs:
 
-```powershell
+```shell
 PS> Shutdown-lab
 ```
 
 To checkpoint the VMs:
 
-```powershell
+```shell
 PS> Snapshot-Lab
 ```
 
 To quickly rebuild the labs from the checkpoint, run:
 
-```powershell
+```shell
 PS> Refresh-Lab
 ```
 
 ## To Patch a lab
 
 If you want to make sure the virtual machines have the latest updates from Microsoft, you can run this command:
 
-```powershell
+```shell
 PS> Update-Lab
 ```
 
 Because this may take some time to run, you can also run it as a background job.
 
-```powershell
+```shell
 PS> Update-Lab -AsJob
 ```
 
 ## To remove a lab
 
 To destroy the lab to build again run:
 
-```powershell
+```shell
 PS> Wipe-Lab
 ```
 
 You will be prompted for each virtual machine. Or you can force the removal and suppress the prompts:
 
-```powershell
+```shell
 PS> Wipe-Lab -force
 ```

Configurations/SingleServer/Instructions.md

@@ -14,86 +14,86 @@ Administrator password is P@ssw0rd.
 
 To run the full lab setup, which includes Setup-Lab, Run-Lab, Enable-Internet, and Validate-Lab. You should run all commands from the directory with the MOF and psd1 files.
 
-```powershell
+```shell
 PS> Unattend-Lab
 ```
 
 To run the commands individually to setup the lab environment:
 
 Run the following for initial setup:
 
-```powershell
+```shell
 PS> Setup-Lab
 ```
 
 To start the Lab, and apply configurations the first time:
 
-```powershell
+```shell
 PS> Run-Lab
 ```
 
 To enable Internet access for the VMs, run:
 
-```powershell
+```shell
 PS> Enable-Internet
 ```
 
 To validate when configurations have converged:
 
-```powershell
+```shell
 PS> Validate-Lab
 ```
 
 Or you can run the Pester test directly
 
-```powershell
+```shell
 PS> Invoke-Pester vmvalidate.test.ps1
 ```
 
 ## To Stop and snapshot the lab
 
 To stop the lab VMs:
 
-```powershell
+```shell
 PS> Shutdown-lab
 ```
 
 To checkpoint the VMs:
 
-```powershell
+```shell
 PS> Snapshot-Lab
 ```
 
 To quickly rebuild the labs from the checkpoint, run:
 
-```powershell
+```shell
 PS> Refresh-Lab
 ```
 
 ## To Patch a lab
 
 If you want to make sure the virtual machines have the latest updates from Microsoft, you can run this command:
 
-```powershell
+```shell
 PS> Update-Lab
 ```
 
 Because this may take some time to run, you can also run it as a background job.
 
-```powershell
+```shell
 PS> Update-Lab -AsJob
 ```
 
 ## To remove a lab
 
 To destroy the lab to build again run:
 
-```powershell
+```shell
 PS> Wipe-Lab
 ```
 
 You will be prompted for each virtual machine. Or you can force the removal and suppress the prompts:
 
-```powershell
+```shell
 PS> Wipe-Lab -force
 ```