Skip to content

3. Starting an Automated Deployment (Part 1)

Jump to bottom
Raimund Andée [MSFT] edited this page Feb 7, 2017 · 5 revisions

Part 1 of the document describes the steps to deploy a Skype for Business 2015 lab based on the topology file.

  1. Test / set the requirements
  2. Convert the topology file into a script for AutomatedLab
  3. Invoke the AutomatedLab deployment script

For the following steps, it is recommended to use the ISE and not the PowerShell console windows.

1. Test / set the requirements

There are some further requirements that should be checked prior to the deployment. If this is the first deployment, you need to run the Cmdlet "Set-SfBLabRequirements" first. This Cmdlets makes sure that everything is in the right place. It will ask you for the full paths to the required ISO files. It also checks if the required hotfixes are available in the LabSources\OSUpdates folder. The information is stored in the registry (HKEY_CURRENT_USER\SOFTWARE\AutomatedLab\Cache\SfB) and will not be needed again. If you need to change something, just call "Set-SfBLabRequirements" again.

The LabSources folder should look like this: Set-SfBLabRequirements

You can always test with the Cmdlet "Test-SfBLabRequirements", if the requirements are still good. t

Please copy the following lines into the ISE. This is all it takes to create the lab environment. Actually only the call to "Start-SfBLabDeployment" is required but the other two lines are making sure that the requirements are tested.

if (-not (Test-SfBLabRequirements))
{
    Set-SfBLabRequirements
}

Start-SfBLabDeployment -LabName SfbTest1 -TopologyFilePath D:\export.tbxml

Running the script will be asked for subnet mask until all IP addresses defined in the topology could be mapped to a subnet.

Deplyment Log

asked for external adapter External Virtual Switch

Clone this wiki locally