PowerShell Deployment Toolkit (PDT) Update for SQL Server 2014

The PowerShell Deployment Toolkit (PDT) is a set of scripts and knowledge for automated deployment of Microsoft System Center 2012 SP1/R2, including SQL all prerequisites, and all automatable post-setup integration. For additional knowledge on using PDT, please check out the PowerShell Deployment Toolkit Wiki on TechNet.

I’ve been using PDT for several years to keep a personal System Center 2012 lab handy for testing and troubleshooting customer issues, but up until this time, it’s been running on SQL Server 2012. More and more customers are going to SQL Server 2014, so it was time to upgrade my lab as well.

In looking through the workflow.xml for PDT, I thought I was in luck, as SQL Server 2014 is listed as a component installable. But, after a few install attempts, I realized there were some pieces missing that needed to be updated before SQL Server 2014 could be installed successfully.

Here is the process of updating PDT- to work with SQL Server 2014. Please keep in mind, I have only tested this with Operations Manager 2012 R2.

  1. Download SQL Server 2014 SP1
  2. Create a folder under your existing Installer folder called SQLServer2014.en. I create a new Installer folder for each release of PDT, so mine is called C:\Installer2620\SQLServer2014.en
  3. Extract the contents of the SQL Server 2014 evaluation package to your installer folder C:\Installer\SQLServer2014.en
  4. Download the following updated workflow.xml and variable.xml to your PDT scripts folder, mine is located at C:\PDT\2620. If you want to note the changes, search in the workflow.xml for references to SQLServer2014 and SQL Server 2014. I basically updated any section of the xml that contained references to SQL Server 2012
  5. Open a PowerShell command prompt as Administrator and change to your PDT scripts folder and run the following command. ./downloader.ps1 -DeploymentOnly . This command will download and update any prerequisites that are needed to deploy SQL Server 2014.
  6. If you use the example variable.xml included in the zip file download above, edit to insure it is referencing the correct location of your vhxd differencing disk.



Leave a Reply

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