Build a Windows Azure Pack 2013 lab using PDT

Building a Windows Azure Pack 2013 for Windows Server lab using PowerShell Deployment Toolkit (PDT).

Rob Willis over at the Building Clouds blog on TechNet released an example configuration for Windows Azure Services several months ago, but I haven’t seen an example posted for the recently released Windows Azure Pack 2013 for Windows Server.

Here are all the new Windows Azure Pack 2013 roles available in PDT.

10-29-2013 10-10-20 AM

Using the attached set of PDT files, you can build a fully functional Windows Azure Pack 2013 lab, including all integrations to Service Provider Foundation, Orchestrator, App Controller, Virtual Machine Manager and Operations Manager to enable all charge back/show back capabilities that are now included in the Windows Azure Pack.

This particular environment is deployed to 6 virtual machines and should function well on systems with at least 32GB of RAM. In a proof of concept, or production environment, you would want to spread the roles out further to allow for scale and security.

  • WAPDC01 – Domain Controller
  • WAPOM01 – Operations Manager, OMDB, OMDW and Report Server
  • WAPSCO01 – Orchestrator, Service Provider Foundation and Windows Azure Admin roles
  • WAPSQL01 – DB for all roles except Operations Manager
  • WAPTenant01 – Windows Azure Service Tenant roles
  • WAPVMM01 – Virtual Machine Manager and App Controller

I had the best luck connecting to the various sites using DC01. Here are the WAP links

During the course of testing these deployments, I discovered several minor bugs in the current release of PDT that Rob has already fixed and are included in this download. I’m sure as time permits, Rob will be releasing an update on the Building Clouds blog as well.

Once you have deployed the Windows Azure Pack, you will still need to deploy a private cloud to enable Windows Azure Pack, so I have included links below to help you get started!

Link to update files are here ==> PDT2600

Creating a Private Cloud in VMM Overview

Requirements for using VM Clouds

MSDN Installation Guide

Windows Azure Pack for Windows Server

13 thoughts on “Build a Windows Azure Pack 2013 lab using PDT

  1. Damian Flynn


    You mention in the post that you have attached a new set of files, and PDT build from Rob, however I am unable to see the attachment (I am logged in). Can you check the location of the attachment for us.

    Thanks for the post, and good work debugging PDT.
    Kind Regards

  2. Joe Thompson Post author


    The link isn’t very visible. I’ve added a bit of text to made it stand out more. It’s right above the links to the articles.

    Thank you!


  3. Marc-Andre

    I’ve tried this several times to create a home Azure lab with no success. I’ve been getting an error that the azure installation failed on WAPSCO01.  Any insight?

  4. Joe Thompson Post author

    Marc-Andre, what sort of error are you seeing? In most instances, I have seen the Orchestrator web service fail to install correctly, especially in low resource environments.

  5. Marc-Andre

    These failed to install:

    Orchestrator Management Server
    Orchestrator Primary Runbook Server
    Orchestrator Web Components Server
    Orchestrator Runbook Designer  Server

    I have 32GB Ram, I was under the impression that would be sufficient. I can try it again and take a screen shot if that helps.



  6. Joe Thompson Post author


    If you used the PDT files included in the blog post, you should have no problems with 32GB of RAM. What does your CPU and DISK configuration look like? It is possible you could be encountering timeout issues.

    Thanks for the feedback Jim!

  7. Joe Thompson Post author

    Marc-Andre, what is your current configuration? You would be surprised how much performance gains you can get just from adding an SSD drive. Just add an additional SSD drive and move all the PDT, Installer, VHDX and VM folders to it. If you go back and reference some of my earlier PDT posts, you’ll see some of the pain I had with my initial hardware

  8. Joe Thompson Post author

    Min is 256GB if you host all the Installer files, ISOs and System Center VMs on it. I have 2 striped together with storage spaces, and it is crazy fast!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.