次の方法で共有

Deployment–PDT 2.6 is now available on the TechNet Gallery

  • [アーティクル]

PowerShell Deployment Toolkit version 2.6 has now been posted to the TechNet Gallery here.

Version 2.6 resolves a number of bugs, and also adds the following capabilities:

  • High availability for roles that require network load balancing
  • Shared VHDX creation
  • VM creation updates:
  •        Generation 2 VMs
  •        VLAN Tagging
  •        MAC Spoofing
  •        Autostop Settings
  •        Guest Services
  • Deployment of Windows Azure Pack Web Sites
  • Deployment of cumulative updates for SQL Server 2012
  • Ability to specify groups for server admins per component
  • Ability to specify a product key for Windows Server
  • VMCreator for AD does not delete log files after Installer completes
  • VMCreator for AD does not delete source files if Installer fails
  • Check for Web Platform Installer in Downloader

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

Comments

  • Anonymous
    January 01, 2003
    Looking good Rob. A suggestion: how about allowing VMCreator to configure into an existing domain? That way, I could be sure all the necessary AD accounts & groups were created correctly. I created a PS script borrowing heavily from VMCreator, but I'm not sure if I really got everything.
  • Anonymous
    January 01, 2003
    Mark - VMCreator will already create VMs in existing domains, in fact that was the original functionality. It won't, however, create the accounts and groups - since there is no assumption that you have permissions in AD to do that.
  • Anonymous
    January 01, 2003
    Rob, I have used the early versions with an existing domain. That is where I discovered the accounts and groups were not getting created in AD. Right now, the script I use sweeps Workflow and Variable (when run on the DC) to create the necessary users, groups, OU, etc. Since there is lot in the PDT, I'm just not sure I got everything. (I'm currently trying to "fix" an error with Operations Manager which looks like it may be an AD/account/group related issue.)
  • Anonymous
    February 14, 2014
    :-) Great, thanks alot!!
  • Anonymous
    February 14, 2014
    :-) Great, thanks alot!!
  • Anonymous
    February 14, 2014
    :-) Great, thanks alot!!
  • Anonymous
    February 15, 2014
    Hi! The Gen 2 VM creator and the VLAN tagging will save me a lot of time! keep up the good work! cheers
  • Anonymous
    February 15, 2014
    Hi! The Gen 2 VM creator and the VLAN tagging will save me a lot of time! keep up the good work! cheers
  • Anonymous
    February 17, 2014
    Great new features in PDT v2.6 Rob, awesome job on all these scripts! Deploying a System Center 2012 R2 lab with PDT v2.6 http://www.systemcentercentral.com/powershell-deployment-toolkit-pdt-v2-6/
  • Anonymous
    February 21, 2014
    The comment has been removed
  • Anonymous
    March 25, 2014
    Hello Rob! Great work! Anxious to start testing it!
  • Anonymous
    May 16, 2014
    I have got to be done something seriously wrong. I thought I'd start small with just a domain controller and a SCCM server, but I sure broke it. I'm going to go grab the XML that Joe Thompson made available and start over.

    One thing I did notice though. The downloader is downloading ADK 8.1 Update 1 but that then fails the validation as being the "wrong version" of the ADK.
  • Anonymous
    June 17, 2014
    Search for WindowsAutomatedDeploymentKit81Source in Workflow.xml. check 8.100.26629 matches what is downloaded.

    Entry for SystemCenter2012R2ConfigurationManagerPrerequisitesSource. Inspects the ConfigMgr.Manifest file size and does not detect. Worflow.xml contains different value, file download is 8,450 bytes. Changed value in workflow.xml and works

    Value SystemCenter2012R2OperationsManagerSource looks for folder ..installersystemcenter2012r2operationsmanger.en > removed the .en and validations passed

    Virtual Machine Manager download from Technet contains both amd64 and i386 folders in extract, move amd64 files to root of ..systemcenter2012R2virtualmachinemanager to pass validation

    Now for my problem, VMCreator creates Generation 1 virtual machines, even if I use a sysprepped Windows Server 2012 R2 VHDK. If I create the vm manually and attach the VHDK, no issues. Inspecting VMCreator.ps1 but not sure why setting VM to correct generation. Host is Windows Server 2012 R2 and VMs are created from the same ISO used for host installation, downloaded from Technet