So, how difficult is to create your own factory?
- Option 1 – Build it from Scratch using Visual Studio ALM Rangers Guidance
- You will need a good day and a couple of coffee based caffeine boosts.
- Option 2 – Use the Starter factory
- You need 2 hours elapsed time on a good LAN and occasionally flip over to the factory to check progress.
Option 2 – Step by Step
- Obtain the starter factory virtual machine, which is a VPC based image.
- Create a virtual machine using your virtualization host of choice and point at the starter factory VM. As you can see the system requirements for the factory are minimal, although we recommend that you increase the RAM is you are expecting heavy traffic on the factory.
- Start the virtual machine.
- Be a bit patient (minutes) while the sysprep’d image continues the setup.
- If you are testing, skip the licensing step. If you are creating a more permanent factory, a license key will avoid the TRIAL issues.
- Specify a machine name, that is unique and preferably based on the VSTSR-MDT-* pattern for uniformity. I chose LAB, as this will be our staging, LAB and test factory in future.
- Change the administrator password.
- Watch was the DeploymentShare environment is initialised. If you are interested in how this magic works, refer to the the full script at c:\windows\system32\sysprep\Setup-Factory.ps1, which is using the MDT PowerShell snapin.
- Please read the conclusion message carefully and select OK when done.
- At this stage we have a fully functional factory that supports the TFS2010R32TW, TFS2010R32TM, TFS2010R64TW and TFS2010R64TM profiles. In our case we have a number of other factories which are configured to support MSDN based profiles as well and therefore I execute the Syncfactory script as mentioned in the conclusion message.
- Less than half an hour later and 1.5 hours after starting the process …
… we have a fully configured and functional factory.
Need I say more … phenomenally easy!