Deployment–Minor PDT update 2.5.2502 available

Deployment–Minor PDT update 2.5.2502 available

  • Comments 9
  • Likes

This release corrects a bug in the Windows Azure Pack configuration, and updates the download for SharePoint 2010 Foundation to SP2 since the original release is no longer available.

Download here.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • i need to downlaod and installtion process for

  • Rob,

    Thank you for the changes...worked like a charm!

    $GreatWork = PDT is an invaluable tool

    Thanks,

    Jim

  • Hi Rob.  It seems that all the download links are broken for the R2 stuff again.

    Now they take you to page that prompts you to select the preview for download but not the product.

    Davey

  • Rob,

    PDT is great, unfortunately my deployment keeps getting stuck... I'm deploying AD, the DC is created, up and running but waiting on RD01.... I logged onto RD01 and it is never getting into the domain. I was able to manually log onto RD01, and join the domain so the DC is up and the HyperV network adapter configured properly.

    NOTE: This is with 2012 R2 / SC 2012 R2 preview bits.

    I also tried with 2012 SP1, but ran into error when using VMCreator... apparently SQL Server 2008 R2 is a pre-req and it is saying the version that was downloaded is not the right version.

    Thanks,

  • Hi Steve

    Regarding the SQL the download may have been updated.  You may need to update this line in the workflow.xml

             <FileVersion>10.50.4000.0</FileVersion>

    So right click on the setup.exe that was downloaded and extracted from the SQL path.  Then check the version number.  Search in workflow.xml for <Installable Name="SQL Server 2008 R2"> then scroll down a few lines and you should find the version number (should be about 9 - 10 lines down) update that to the correct version for what you have downloaded and then save and run.  You should now be able to deploy the SP1 version :)

    Regarding the R2 I have seen it where if the build starts all 14 - 17 machines at once and you only have a couple of disks (Home machine) that by the time the domain join happens network etc.. have timed out.  If this is the case just delete the RD01 VM (NOT THE DC :) ) remove it from disk and re-run vmcreator script.  This will then build a fresh machine that you can manually power on and ctrl c the vm creator.  you cna do this for any machines that didn't work or do it for all apart from the DC and turn them on as the script asks.

    Hope this helps.

    Davey

  • Davey,

    Thanks for the insight.  I actually found that the downloader didn't apply the service pack to the RTM image so my SQL Server was at RTM and the VMCreator was looking for SP1 version level.  I manually Slip Streamed the SP image into the directory and that resolved the issue.

    As for the other issue - the DC is up and running and it is waiting at:

               Write-Host "Waiting for `$VMName"

               While (!(Get-RegValue -Server `$VMName -Value `$VMName)) {Start-Sleep 1}

    I should be able to determine if there is a timing issue by temporarily removing the VM auto-start flag from the VMCreator script.  Then manually start each VM via HyperV manager.

    BTW... I'm doing this at work on a system with 48G of memory and about 1/2 TB of free diskspace.

    Regards,

    Steve

  • As I looked into it, I see there is a <delay> within <autostart> so I'm trying an incremental value for each subsequent VM.  So, I'm letting the DC and 1st VM auto start immediately.  After that the next VM has an autostart delay of 100 seconds, the next VM 200 seconds, etc.

    We'll see if this helps.

  • I've tried several different things...

    1. I tried the AutoStart delay, however, that did not appear to work as expected.  When I looked all VMs were powered on

    2. I tried breaking up the Variable.xml script into Pass1 and Pass2 - ultimately reducing initial deploy to only 6VMs - again it is stopped waiting for the first VM in the list.

    3. When breaking down to 6VMs didn't work, I cut that in half to 3VMs (DC, RD01, DB01)

    4. Stop RD01, shutdown, delete

    5. Start VMCreator again

    The initial VMCreator script completes, but when connecting to the DC, it shows it is still waiting for the first machine (RD01 in my case).  Specifically it is on a remote PowerShell command looking for something to be written in the registry of RD01.

    After the last try, I logged onto the DC, stopped the script that was "waiting for RD01" and then attempted to execute the powershell line individually - an error was occurring that was being masked.  The DC is not able to communicate to RD01.  I logged onto RD01 and it is able to ping the DC.

    Within Hyper-V I'm using an internal network (e.g. Isolated from our production network).  The DC has the DNS configured so I would expect the DC to be able to see RD01 on the network.  Any Ideas?

  • After a bit of debugging I have discovered the root cause of the issue.  First, I'm creating a totally isolated environment (e.g. internal network within HyperV).  I mistakenly thought that when a domain was being created that the user contained within JoinDomain would be created as the domain admin.  When a domain is being created the administrator of the machine when promoted becomes the only domain admin.  After realizing that I was able to make substantial progress.

    After my experience, I have some suggestions:

    - If domain join fails, error out and don't erase the install files... when I was trying to debug, I got to the VM and saw

     it was not joined, but didn't know why.  Only after digging around on the DC did I realize it was related to the

     domain join ID.

    - Would be nice if the VMCreator would create the user specified within "JoinDomain" if a new domain is being

     created ... this would enable something other than the administrator used to configure the domain being the only

     domain Admin.

    - Would be nice if Certificate Error on Service Provider contained some information as to what it was looking for...

     perhaps a URL reference to setup/config section on TechNet/MSDN

    - Would be nice to be able to specify multiple Virtual Network cards for the domain controller being created... the

     idea would be to have one connect to outside world and the other be used for internal w/setup.

    - Would be nice to pull all information from the various Blog posts into a document which is included with the PDT

     package.

    - Would be nice to have a way put the installable files on a VHD, unmounts the vhd once VM creator is completed

     and then in the installer instance running on the new Domain Controller - mount the VHD... that way the same

     installable files could be used (assumption is that the initial install is kicked off from same server which has DC

     VHD).

    Although I had to work through some intricacies, I found PDT to be extremely useful.

    Thanks for a great tool!

    Steve Keller