6 responses

  1. Profile photo of Cameron Fuller
    Cameron Fuller
    December 18, 2013

    Joe, this is excellent information! I’m working with PDT on a lab rebuild now and hitting similar failures which I expect may be due to the amount of memory on each virtual. Based upon your writeup I’m about to increase those and go try it again.

  2. Profile photo of Joe Thompson
    Joe Thompson
    December 19, 2013

    Glad you found the information helpful Cameron!

    The more memory (and disk) you can throw at the installation process the better! I have been disabling dynamic memory on the VM’s by specifying the same value for min and max menory in the variable.xml, which also helps. I just recently replaced my striped pair of sata disks on a 3 GB/s channel for SSD’s on the 6 GB/s channel and decreased the installation process by almost 40 minutes.

    Joe

  3. Profile photo of Lenar
    Lenar
    December 24, 2013

    This is very useful post, Joe! thank you.

    Could you tell me is it possible to install the whole SystemCenter stack using the only one SQL server with different instances? I tried to do this with PDT by modifying variable.xml, but didn’t have success.

  4. Profile photo of Joe Thompson
    Joe Thompson
    December 24, 2013

    Your best bet is to review the possible role combinations in the WORKFLOW.XML file. Most databases can be combined with the exception being Operations Manager and Service Manager.

    The possible combinations are listed in the <Roles> section of the workflow.xml

  5. Profile photo of stephanevg
    stephanevg
    March 23, 2015

    Part1 and this post have been really useful. Great post Joe! I might be a bite late. Your post helped me to understand the basics of it, and I have shared my experiences on my blog. It could help somebody perhaps?

    Link –>  http://powershelldistrict.com/powershell-deployment-toolkit/

    Feedback is highly appreciated :)

Leave a Reply

You must be to post a comment.

Back to top
mobile desktop