AutomatedLab 5.5.268 - Setting up virtual labs on your local machine or in Azure

AutomatedLab 5.5.268 - released on January 30 2019. Deployment of TFS / AzureDevOps was added + lots of bug fixes. Please refer to the changelog on GitHub.For further documentation and source code please go to https://github.com/AutomatedLab/AutomatedLab. There is also a chan

AutomatedLab.msi
 
 
 
 
 
4.8 Star
(39)
6,885 times
Add to favorites
Applications
1/31/2019
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Unable to find any ISOs
    2 Posts | Last post May 15, 2019
    • Hi, I have followed the install and setup guides on git, configured Autolab to use H:\labsources. I added the iso files into H:\Labsources\ISOs and ran the "Add-LabIsoImageDefinition -Path H:\labsources\" without issue.
      However when I try and run either a script in the samples like 'Lab in a Box 1 - HyperV.ps1' or manually setup a lab as per the getting started page I get the following errors
      PS H:\labsources\Sample Scripts\Scenarios> & '.\Lab in a Box 1 - HyperV.ps1'
      
      11:20:06 - Location of lab definition files will be 'C:\ProgramData\AutomatedLab\Labs\ALTestLab1'
      11:20:06 - Location of LabSources folder is 'H:\LabSources C:\LabSources'
      Get-ChildItem : Cannot find path 'H:\LabSources C:\LabSources\' because it does not exist.
      At C:\Program Files\WindowsPowerShell\Modules\AutomatedLabDefinition\5.0.0.231\AutomatedLabDefinition.psm1:916 char:19
      + ...   if (-not (Get-ChildItem -Path "$(Get-LabSourcesLocation)\ISOs" -Fil ...
          + CategoryInfo          : ObjectNotFound: (H:\LabSources C:\LabSources\:String) [Get-ChildItem], ItemNotFoundException
          + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
      11:20:06 - No ISO files found in H:\LabSources C:\LabSources\ISOs folder. If using Hyper-V for lab machines, please add ISO files manually using 'Add-LabIsoImageDefinition'
      11:20:06 - Auto-adding ISO files
      Get-ChildItem : Cannot find path 'H:\LabSources C:\LabSources\' because it does not exist.
      At C:\Program Files\WindowsPowerShell\Modules\AutomatedLab\5.0.0.231\AutomatedLab.psm1:1068 char:17
      +     $isoFiles = Get-ChildItem -Path $Path -Filter *.iso -Recurse
          + CategoryInfo          : ObjectNotFound: (H:\LabSources C:\LabSources\:String) [Get-ChildItem], ItemNotFoundException
          + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
      11:20:06 - found 1 OS images
    • I am not monitoring this site very closely. Please use GitHub issues for faster feedback.
      
      You can have only one LabSources folder. You have one on drive H and another one on C. AL doesn't like this.
  • ok... so Where is the documentation?
    1 Posts | Last post February 21, 2018
    • I see in the description field that the documentation and some sample scripts are supposed to be in my documents folder, but nothing stands out.  Is there a file name I can search for? (myu 'My Documents' folder is rather.... large.
  • Set-LabHost
    1 Posts | Last post November 29, 2017
    • I am trying to utilise AL from a client machine connecting to a Host Server, every time i try to use the Set-LabHost cmdlet powershell (including ISE) hangs.
      
      Is it possible to use AL to deploy labs to a remote host and if so how?
  • The Script stop waiting?
    1 Posts | Last post October 29, 2017
    • I Have several times faced that the script stop waiting after the VM builds, it can be several thing like waiting for a Lab-server to start but the script looks for other IP that is not in the script?? Strange?
      
      In the ISE you se the script waiting for Connection to IP 104.122.237.146:80, but that is not an IP related in the lab settings?
      
      Test-NetCpnection - 104.122.237.146:80 - Attemting TCP Connect, Waiting for responce
      
      Before you can see that some dll have been downlodes
      https://nuget.org/MicrosoftPackageManagement.NugetProvider-2.8.5.208.dll -Completed
      
      Anyone know what going on.
  • Shell Hardware Detection (ShellHWDetection)
    1 Posts | Last post October 05, 2017
    • Hi Raimund,
      I seem to be running into an error where Hyper-V is trying to stop the Shell Hardware Detection (ShellHWDetection) service but is unable to. I can confirm that I am running the PowerShell ISE as an administrator. I have been able to get past this by killing the svchost service that is responsible for the shellhwdetection service.
      Any ideas what I can do to prevent it from happening? I have confirmed that I am running the latest version.
      Regards
      Donovan
  • Unable to find ISOs Sources folder
    3 Posts | Last post October 05, 2017
    • I keep getting the error about unable to find any ISOs in the ISOs folder. I customized the sources location when installing the msi to install it on E:\Dev\AutomatedLab and it seems to not detect the ISOs folder period whether i put it in E:\Dev\AutomatedLab\LabSources\ISOs or E:\Dev\AutomatedLab\LabSources\ISOs
      
      
      PS E:\Dev\AutomatedLab> Get-LabSourcesLocation
      
      PS E:\Dev\AutomatedLab> Add-LabIsoImageDefinition -Name "ISO" -Path "E:\Dev\AutomatedLab\LabSources\ISOs\en_windows_server_2012_r2_vl_with_update_x64_dvd_6052766.iso" -Verbose
      VERBOSE: Add-LabIsoImageDefinition Entering... (Name=ISO,Path=E:\Dev\AutomatedLab\LabSources\ISOs\en_windows
      _server_2012_r2_vl_with_update_x64_dvd_6052766.iso,Verbose=True)
      VERBOSE: Read 3 ISO images from the cache
      21:00:19|00:04:03|00:04:03.895| - Added 'E:\Dev\AutomatedLab\LabSources\ISOs\en_windows_server_2012_r2_vl_wi
      th_update_x64_dvd_6052766.iso'
      VERBOSE: Final Lab ISO count: 1
      VERBOSE: Add-LabIsoImageDefinition...leaving...(Time elapsed: 00:00:00:045)
      
      PS E:\Dev\AutomatedLab> Get-LabSourcesLocation
      
      PS E:\Dev\AutomatedLab> New-LabDefinition -Name $labName -DefaultVirtualizationEngine HyperV -Path "E:\Dev\AutomatedLab\KHANEMPIRE" -VmPath "E:\Dev\AutomatedLab\AutomatedLab-VMs"
      21:01:24|00:00:00|00:00:00.000| Initialization
      21:01:24|00:00:00|00:00:00.003| - Host operating system version: '10.0.14393'
      21:01:24|00:00:00|00:00:00.006| - Creating new lab definition with name 'KHANEMPIRE'
      21:01:24|00:00:00|00:00:00.025| - Location of lab definition files will be 'E:\Dev\AutomatedLab\KHANEMPIRE'
      21:01:24|00:00:00|00:00:00.096| - Location of LabSources folder is '()'
      21:01:25|00:00:00|00:00:00.545| - No ISO files found in \ISOs folder. If using Hyper-V for lab machines, ple
      ase add ISO files manually using 'Add-LabIsoImageDefinition'
      21:01:25|00:00:00|00:00:00.548| - Path for VMs specified as 'E:\Dev\AutomatedLab\AutomatedLab-VMs'
      
      PS E:\Dev\AutomatedLab> 
    • OK so I ran a repair and it reset the lab sources folder to C:\LabSources. How can I change this as I want to utilize the ISO's stored in the E:\Dev\AutomatedLab\LabSources Folder?
    • Hi Raimund,
      I seem to be running into an error where Hyper-V is trying to stop the Shell Hardware Detection (ShellHWDetection) service but is unable to. I can confirm that I am running the PowerShell ISE as an administrator. I have been able to get past this by killing the svchost service that is responsible for the shellhwdetection service.
      Any ideas what I can do to prevent it from happening? I have confirmed that I am running the latest version.
      Regards
      Donovan
  • Is this project based on DSC?
    8 Posts | Last post May 17, 2017
    • Hi Raandree -
      
      I recently came across your AutomatedLab (AL) project, before this, I was using the AutoLab by JasonHelmick (https://github.com/theJasonHelmick/PS-AutoLab-Env). I like AL because it has more options. However, since Microsoft is moving towards DSC, I was wondering if this project is based on DSC. Other than Powershell, are there any requirements to learn and understand this project? Also, if it's not using DSC, do you have a reason why you chose not to integrated it. 
      
      Thanks for your time.
      Raj
    • Hi Raj,
      
      we have decided not to use DSC to be able to support older OS versions and reduce the requirements. The requirements for AL is just having the ISO files for Hyper-V and for Azure there are not additional requirements at all.
      
      However we see the need for DSC and are working on an implementation: https://github.com/AutomatedLab/AutomatedLab/issues/91. So, in the very near future you will be able to configure the lab VMs after the deployment using DSC. If you have some input, please participate in the discussion on GitHub. If the DSC supports in AL has reached a certain step and old OS versions are no longer of interest, we will pretty likely replace functions inside AL with DSC.
      
      -Raimund
    • Thanks for the quick response. I thought DSC supported Windows 7. Anyway, I don't know much about it, other than the fact that is can do a whole lot very easily. Anyway, is knowing Powershell the only requirement to understand this framework? I've always looked for ways to create automated lab environments. is this built in Visual Studio? just want to set it up and see if i can make changes and learn from this. 
      
      Thanks,
    • Please look at https://github.com/AutomatedLab/AutomatedLab/wiki to get started. The introduction scripts should give you an idea about what AL can do and the flexibility it offers. The first Version of PowerShell that supports DSC is 4.0 and it only supports DSC very well after applying a huge fix, just don’t know the KB number.
      
      Don’t get me wrong, DSC is great and we will add it to AL.
      BTW, if you want to get started with a DSC lab, take a look at the two DSC scenario scripts we offer here: https://github.com/AutomatedLab/AutomatedLab/tree/master/SampleScripts/Scenarios
      
    • just looking for how to start learning this framework, and how it all fits together. Not sure if this a C# project or Powershell? 
    • The the wiki on GitHub is your best place to start then. I have just seen these numbers: PowerShell 83.8%, C# 16.2%. Almost everything is done in PowerShell, just the code to handle the internal lab definitions and XML files are written in C#. 
    • Thanks for quick response. I will play with and let you know if i have questions. I'm sure it has a way to install custom software like Sysmon, 7zip, etc.. Will explore it..
    • It surely has and there is also some documentation on this: https://github.com/AutomatedLab/AutomatedLab/wiki/Installing-Software.
  • Configuring Network Settings
    4 Posts | Last post April 06, 2017
    • Hello,
      
      Thanks for the great tool. Using it to learn PowerShell while building a test lab. I apologize if I missed it in the documentation but I was curious where the hyper-v switch settings were configured. I would like to setup the switch as external and pull dhcp for the IP addresses. This lab is only accessible via VPN and is going to be used for our security team to practice and learn in. The only parameter I see that might be applicable is the -hypervproperties in the add-labmachinedefinition cmdlet.
      
      Any tips or a point in the right direction would be greatly appreciated!
    • Can you please have a look at this script? https://github.com/AutomatedLab/AutomatedLab/blob/master/SampleScripts/Introduction/05%20Single%20domain-joined%20server%20(internet%20facing).ps1
      
      In this sample script we define an external and internal adapter and also configure routing so all lab machines can access the interne.
      
      Does this help?
    • That is definitely where I need to start. Thank you!
    • We are extending the Wiki on GitHub constantly and the network stuff is the next item on my list.
  • New / customized roles
    7 Posts | Last post March 22, 2017
    • Hi, 
      
      i apologize if I missed something obvious in the documentation. Are there any documented ways of creating new roles (Skype for Business for example) and/or customize existing. I would also like to have a "standard server" role, where nothing is added. 
      
      Thanks!
    • Hi,
      
      if you add a server without a role, that's a standard server and AutomatedLab does not install any additional stuff.
      
      Unfortunately we do not have a guide that describes how to add new roles. Skype for Business for example is too complex and we have written an extra module that is based on AutomatedLab. Please checkout https://github.com/AutomatedLab/SfBAutomatedLab.
      
      What other roles are you thinking about?
      
      Thanks,
      Raimund
    • Thanks for your input. I did not know about the SfBAutomatedLab, that helps alot. Bummer that it couldnt be fully automatized. Not sure i if i understand the reason for that, there is a Publish-CsTopology cmdlet which could do the same thing as you suggest in your screenshots. 
      
      My question about customizing the roles would example be if i wanted to have a Exchange 2016 Role, based on Windows Server 2016. 
    • Ah i see now in the documentation that using Publish-CsTopology can't be used anymore. Bummer.. 
      
      An on the Exchange question, i could tweak it myself i think, but the ISO image is hard-coded, any way of changing that in the future? So you could define your own ISO for Exchange? 2016 and 2013 is very similar, the only change needed except the ISO is the Role (only mailbox role). 
      
      Thanks
    • Exchange 2013 and 2016 is already available as a role in AL. However the implementation is pretty basic, just a standard installation. If you want to extend it, you are very welcome. We should move the communication to GitHub then.
      
      Regarding SfB: Publish-CsTopology works with xml files exported previously in a SfB environment but not with the tbxml files create by the topology builder. Anyway, anything expect of this can be automated so far.
    • Ok, i will start a discussion on Github around that. 
      
      But you say that 2016 is already available, i can see the role. But i can't see the role definition in the modules folder. And when trying to install servers based on the Exchange 2016 Role, it installs the server but doesnt try to install Exchange at all. No errors or warnings when running the script. 
    • Which version of AL do you use? We have 4.0.0.2 on GitHub. It is beta but as stable as version 3.x. I am not sure when we have added support for Exchange 2016.
      
      I will update the MSI and documentation here quite soon as well.
  • Change default location
    2 Posts | Last post October 25, 2016
    • Is it possible to change the default file location? 
      What I want to do is to store the Hyper-V machines on a different volume. Not on C:\automatedlab-VM but on the d:\ drive for example.
    • Sure you can:
      
      New-LabDefinition -Name 'Lab1' -DefaultVirtualizationEngine HyperV -VmPath d:\AL
      
      AutomatedLab tries to do as much automatically, but you can always overwrite this.
1 - 10 of 32 Items