PowerShell Deployment Toolkit 2.4.1003

The PowerShell Deployment Toolkit (PDT) is a set of scripts and knowledge for automated deployment of System Center 2012 SP1/R2, including SQL and all prerequistes, and all automatable post-setup integration.  See Building Clouds blog Deployment track for details.This version has

 
 
 
 
 
(13)
Add to favorites
Applications
9/14/2013
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • A few questions
    2 Posts | Last post October 26, 2013
    • Hey Rob! :)
      We're trying to use PDT here at Cireson for lab build out.  A few questions: 
      1) Can we use SQL Express?
      2) How do you add multiple Network Adapters to a VM?
      3) Can you specify product keys for WS or SQL someplace or does it assume you are using VL images?
      
      Right now install is hanging on SQL and although we see that it failed in the logs there is no explanation of why.  Any ideas?
    • Hey Travis!
      
      1. No, none of the System Center components support using SQL Express to my knowledge.
      2. No, VMCreator only creates a single NIC VM.  You would have to manually add additional NICs after creation.
      3. Yes.  For SQL, include a line in Variable.xml at the top alongside SourcePath etc....
      
        <Variable Name="SQLServer2012ProductKey" Value="" />
      
      For Windows Server, I've added that option in 2.6, to be released soon.  Right now it will work with either VL or eval media.
      
      If something fails to install, the Installer logs will only tell you that it failed - you need to look at the setup logs to see why.  These are collected on the system running Installer.ps1 in C:\Temp\<GUID>.  See http://blogs.technet.com/b/privatecloud/archive/2013/02/27/deployment-troubleshooting-pdt.aspx
      
      
  • step by step guide
    2 Posts | Last post Sat 4:00 PM
    • It would be great if someone publish step by step guide how to use PDT in test VM enviroment. 
      If i publish it in my blog will i violate some legal agreements?
    • I published my experiences with PDT in a small home lab here:
      http://www.systemcentercentral.com/my-2nd-week-with-the-powershell-deployment-toolkit-pdt/
      
      You can change the download path in the variable.xml
      
        <Variable Name="SourcePath" Value="E:\Installer" />
        <Variable Name="Download" Value="E:\Installer" />
  • Downloaded Files Path
    1 Posts | Last post July 13, 2013
    • Hi Rob,
      
      First of all thanks for the Great Stuff,
      
      can we change the download path to d: my downloading to C drive is a bad idea.
  • Switch documentation?
    2 Posts | Last post June 07, 2013
    • Rob,
      
      First of all great work on this! 
      
      I'd like to see some documentation on what the switches are used for. Primarily for me, I think $Path in installer.ps1 is used to install from a drive other than $env:systemdrive, but I'm not sure.
      
      I've done a fair amount of coding myself and I've gotten into the habit of making my scripts work with Get-Help, so that the end-user can fall back on the core PowerShell help system to find out how to run one of my scripts.
      
      Aside from that, really great work!
    • I did NOT YOUR QUESTION
  • Replace WinRAR requirement with 7-zip
    3 Posts | Last post May 29, 2013
    • Hi,
      
      Is it possible to (officially) support 7-zip for the file extraction instead of WinRAR? WinRAR is a licensed product whereas 7-zip is free and supports all formats.
      
      The updates required to Downloader.ps1 are:
      Line 432: If (Test-Path "C:\Program Files\7-Zip\7z.exe") {
      Line 449: Start-Process -FilePath 'C:\Program Files\7-Zip\7z.exe' -ArgumentList "x -o`"$Download\$DownloadFolder`" `"$Download\Download\$DownloadFolder\$DownloadFile`"" -Wait -WindowStyle Hidden
      Line 455: Write-Host "7-zip not found"
      
      
    • additionally, one could use 7-zip (or WinRAR) to extract the ISOs, so you could get rid of the Server2012/Win8 requirement for the Downloader
    • Great suggestion Christian.
      
      I have created a GitHub repository to track the stable releases plus our changes to make things easier. It can be found at https://github.com/oWretch/PowerShell-Deployment-Toolkit
      
      I'll look at adding the ability to use 7-zip for ISOs also tomorrow.
  • Error with ConfigMgr prerequisites
    1 Posts | Last post May 27, 2013
    • Hi there,
      
      The saetupdl.exe which downloads the ConfigMgr prerequisites has a requirement that the destination path is <100 characters long. I ran into the issue, which causes the process to stall as the setupdl.exe is trying to notify the user but never displays anything as the /NoUI switch has been passed.
      
      Is it possible to add a path length check to Workflow.xml and fail with an error if the path to download to is too long?
  • Mount-DiskImage : The file or directory is corrupted and unreadable
    4 Posts | Last post May 23, 2013
    • The downloader is only downloading the first 43k of the windows Server 2012 iso, then is failing to extract it. If I pull the url from the workflow and use IE, I can download the entire iso. Any other reports of this?
      
      Thank you!
    • Workaround for me was to find the url link in the workflow.xml for the Windows Server 2012, make sure I was logged into live.com, then download via IE. Once downloaded, I had to mount the ISO and extract the contents to \temp\WindowsServer2012. After that, I was able to run through the downloader.ps1 error free. Now onto creating some VM's and Private Clouds!
    • I can also confirm this issue.. To be able to get it to work the you need to be logged into live.com Before trying to download the WindowsServer2012.ISO with the script.. I Think it works in "Contoso land" but not outside it :)
    • Anyone else hase issues with to install ServiceManager with PDT ? I have tested on 3 different servers but service manager Always fails to install..
      
      And in the validation process the the script fails on 2 systems of 3 in the step to validate System Center 2012 SP1 Management packs.. with the error of incorrect size of Microsoft.Windows.Server.Library.mp incorrect size (tried to copy the files from an ok download but with the same issue) by running /installer -Skipvalidation Local then It seems to work
  • next release of PDT
    1 Posts | Last post May 14, 2013
    • hey, any word on the AD deployment features of PDT that were discussed at MMS2013? really looking forward to it!
  • SQL - Create Multiple Data Files
    3 Posts | Last post May 14, 2013
    • Hi,
      Thank you for the job, it's juste amazing !
      To optimize SQL, one way is to create multiple data files. The only supported way is to pre create the database.
      There is a script to do it (.sql) , how to integrate this with PDT?
      Are, do you plan to do it later ?
      
      Regards,
      Jeremy
    • There is currently no way to do this with PDT.  I believe there is only one System Center component that supports using a pre-created database - Orchestrator - so it would be only marginally useful for System Center anyway.
    • Hi Rob,
      Great job on this solution, I am excited to start using this moving forward, and would like to get to a point where I am using this for production installs.
      
      One question I have along the same lines as Jeremy, is that in a production deployment I never install my sql databases onto the c drive, I always try to have a separate drive for mdf files and a separate drive for ldf files.  I don't see an easy way to accommodate this within the PDT, is there a way you could look to add this capability as a feature in future versions?  Maybe this is something that could be added to the Variable.xml file?  It would be nice to be able to say, here is the sql server to be used for config manager, when you use this sql server, place the mdf files on drive f and place the ldf files on drive g, for example.
      
      Thanks,
      Ralph
  • Typo in Firewall Rules for SQL Server 2012?
    1 Posts | Last post May 04, 2013
    • First, thanks for the outstanding script! It's absoluty fantastic!
      
      Everything worked great for me except the creation of the fireall rules for SQL Server 2012. The rules were created for "C:\Program Files\Microsoft SQL Server\MSSQL11_00.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" but the SQL Server gets installed in "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER...". Because of that, the rule does not work and everything depending on SQL remote connections is going to fail.
      
      After digging a bit deeper, I found that in the workflow.xml the following entry for the SQL Server 2012 firewall rule:
      <Firewall>
       <Rule>
        <Condition>$SQLFeatures.contains('SQLENGINE')</Condition>
         <Name>SQL Server 2012 Instance $Instance</Name>
          <Type>Application</Type>
          <Value>$SQLInstanceDir\MSSQL11_00.$Instance\MSSQL\Binn\sqlservr.exe</Value>
        </Rule>
      
      The "_00" part int the path is probably a typo? 
      (Same for SQL Server 2012 Analysis Services)
      
      After removeing the "_00 and every things works fine.