You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 15, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: Detailed-Setup-Instructions.md
+21-3Lines changed: 21 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ It is assumed that you have administrator rights to your computer and can makes
11
11
If your computer is controlled by Group Policy, you may encounter problems.
12
12
13
13
> It is *possible* to run this module with nested virtualization inside a Windows 10 Hyper-V virtual machine but it is **not** recommended.
14
-
> Some networking features may not work properly and overall performancel will be reduced.
14
+
> Some networking features may not work properly and overall performance will be reduced.
15
15
16
16
## Pre-Check
17
17
@@ -174,7 +174,7 @@ If Hyper-V is not installed you will see errors.
174
174
Any errors indicate a problem with your setup.
175
175
Please post this information when reporting an issue.
176
176
177
-
### Setup a Configuration
177
+
### Setup a Configuration Unattended
178
178
179
179
In an elevated PowerShell session, **change directory** to the configuration folder that you want to use.
180
180
@@ -205,6 +205,24 @@ This is to be expected until all of the configurations merge.
205
205
You can press `Ctrl+C` to break out of the testing.
206
206
The virtual machines will continue to prepare themselves.
207
207
208
+
### Manual Configuration Setup
209
+
210
+
If you encounter errors running an unattended setup, it may have helpful to step through the process manually to identify where exactly and error is occuring. Make sure you are in an elevated PowerShell session and you have changed location to the configuration folder. If you have tried to setup the lab before run `Wipe-Lab` to remove previous set up files. Then run each of these commands individually:
211
+
212
+
*`Setup-Lab`
213
+
*`Enable-Internet`
214
+
*`Run-Lab`
215
+
216
+
Errors that affect setup should happen in one of these steps. If so, open an issue with configuration name, the step you were working on and the error message. Also include the output from `Get-PSAutolabSetting`.
217
+
218
+
After about 10 minutes, you can manually test to see if the configuration has finalized.
219
+
220
+
```powershell
221
+
Invoke-Pester .\Vmvalidate.test.ps1
222
+
```
223
+
224
+
You might still see errors, in which case try again in 10 minute intervals until the test completely passes.
225
+
208
226
### Help
209
227
210
228
All of the commands in this module have help and examples.
@@ -221,4 +239,4 @@ If you get the module installed, please include the results of `Get-PSAutolabset
221
239
If your problem is meeting one of the requirements, we will do our best to help.
222
240
Although if your computer is locked down or otherwise controlled by corporate policies there may not be much that we can do.
0 commit comments