We regularly need fresh labs with Windows Azure Pack and after having used the PowerShell Deployment Toolkit for deploying System Center 2012 R2 and Windows Azure Pack in a production environment, I felt quite confident to use PDT again for my new lab. So what could go wrong?
I took a variable.xml file from a previous installation and modified the variables in it to reflect the VMs I had already created via my Windows Azure Pack portal. Yes you are reading this correctly, I was building a Windows Azure Pack lab right from my own WAP tenant portal. I had to go easy on the memory and cpu resources so I was not able to make everything redundant. For the purpose of this lab it was fine.
Because I wanted to focus on Usage and CloudCruiser, I needed at least Operations Manager, Virtual Machine Manager, Service Provider Foundation and Windows Azure Pack. I added Service Management Automation to get some work done on SMA later. All I needed to do was use the correct user accounts, groups and passwords to get things going.