Deployment–PDT 2.5 is now available on the TechNet Gallery

Deployment–PDT 2.5 is now available on the TechNet Gallery

  • Comments 27
  • Likes

PowerShell Deployment Toolkit version 2.5 has now been posted to the TechNet Gallery here.  Version 2.5 adds a number of enhancements:

  • Deployment of System Center 2012 R2 Preview.
  • Creation of Active Directory during VM creation for end to end isolated environment creation.
  • Static ports for SQL Server named instances to remove requirement for default instances for several components.
  • Validation of components that require full server installations and won’t run on server core.
  • Ability for VMCreator to use either 7-Zip or WinRAR instead of just WinRAR.
  • Ability to specify network adapter identifier during VM creation to allow Windows Server 2008 R2 and non-English OS installation.
  • Ability to specify timezone during VM creation.

Several of the above will the topics of further blog posts in the next few weeks, so stay tuned!

Go Social with Building Clouds!
Building Clouds blog
Private Cloud Architecture Facebook page
Private Cloud Architecture Twitter account
Building Clouds Twitter account
Private Cloud Architecture LinkedIn Group
Building Clouds Google+ Community
Cloud TechNet forums
TechNet Cloud and Datacenter Solutions Site
Cloud and Datacenter Solutions on the TechNet Wiki

Cloud and Datacenter Solutions Hub

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • petezhang - that validation checks the server exists, the account has access, and WMI is allowed in firewall rules.  RDP doesn't test the same thing at all - can you get remote WMI from your servers?

  • OK my issue was the firewall. As soon as I made changes to it, the validation works.

  • Rob how about corrupt distrib of DPM 2012 R2 preview?

    Is there some workaround?

  • Regarding the DPM download, the DPM team are aware and are looking into it.  Unfortunately, there's nothing else I can do at this point.

  • Hi Rob.  

    Great update and love the creating the DC automatically.

    Couple of thoughts / comments.  in the VMcreator where you are adding in the firewall rules would it be worth while also adding in the RDS group as well.  Currently it is creating a machine for RDS but then not enabling anyone to login due to firewall rules.

    Search for Get-NetfirewallRule then add the following line in.

    Get-NetFirewallRule -Group "@FirewallAPI.dll,-28752" | Set-NetFirewallRule -Profile Domain -Enabled True

    That would be the firewall group enabling for RDP access.

    Also when creating the groups currently it adds in the user that is executing the script at the time.  This is the Administrator account.  But the install is all been done by the service account and should we have the domain administrator user a member of all of the groups.  I think that you want to consider changing

    Add-ADGroupMember -Identity `$PrincipalValueUserGroup -Members `$env:Username


    Add-ADGroupMember -Identity `$PrincipalValueUserGroup -Members `$ServiceAccount

    Finally when the script has finished running on the DC it then deletes all of the logs :) so you cant see what has worked or not.  This is a small catch :)

    Thanks again for the great update.


  • DPM download problem solved!

  • Hi Rob.

    On trying to install the SPF i think that there is some kind of issue.  I get the following last 3 lines in the log for the install of SPF

    Loading Managed bootstrapper application

    'P@ssw0rd' is a malformed switch

    shutting down, exit code: 0xffffff


  • Thanks for this amazing toolkit. When I tried this new version, I took the time to blog about my experience. Look at my blog here for some tips:

    PS! The DPM 2012 R2 download seems to be fixed by Microsoft now. Earlier when I tried it, it didn't work, but it does now.

  • Hi great release for the R2 ! Perfect with the AD integration. Have a Problem with the Azure Pack, in every installtaion I have the VMM marked as "unavailable" and it is not possible to add it again after removal in the Azure Pack Admin Portal. Have you got a hint for me ?

  • @Rob, the new script looks great, with the new functionality of the AD controller, it is what I was looking for.

    When the installer.ps1 kicks off from the DC01 server, it is failing to install all instances of SQL Server. When I look at the RD01 server, the SQL Management Tools fail to install with the following error logged:

    Message: The SQL Server registry keys from a prior installlation cannot be modified. To continue, see SQL Server Setup documentation about how to fix the registry keys.

    HResult: 0x84be01ff

    FacilityCode: 1214 (4be)

    ErrorCode: 511 (01ff)

    The same errors are logged on the DB02 server.

    Reviewing the detail log on DB02, I see failures for ProcessorArchitecture cpu while running FixSqlRegistryKey_x64.exe and FixSqlRegistryKey_x86.exe. In each case, the application failed to start because its side-by-side configuration is incorrect.

    From the host server, ps1 scripts are started from C:\Temp folder, and downloaded files are located at C:\Installer.

  • Hi Rob.

    Last night for some fun i started to play around with VMCreator.ps1 :) now i have it all setup to correctly deploy Generation 2 VM's if you are interested.  At the same time i had to update some of the code that was used to deploy the AD parts so if the VHDX's have more than one partition then it still works.

    Also i added in the code for adding in VLan's as i have had a number of instances that labs need to be on a selected VLan.  (Keeping two labs on the one switch separate :) )

    The speed difference on using Generation 2 machines has reduced the time to deploy out and start the VM's up from about 15 - 30 minutes to about 5 :) So huge difference.


  • Hi Rob, it seems the download link of as part of SC2012SP1 management pack (line 3640 workflow.xml) became broken. Even manually dowloading no joy! As workaround I downloaded the MP using the following link (MSI) and extracted the MP.