ReleaseEngineering/worker configuration/2008
Overview
The building of the 2008 builder slave image uses both the Microsoft Deployment Workbench (MDT) and Puppet configuration software. In the case of AWS instances the Amazon EC2 service is also utilized.
The initial steps is building a base image in MDT. The base image is comprised of large applications that will seldom change, Microsoft SDKs, applications that may aid in deployment, and Windows Server Update Service (WSUS) components.
The second portion of this differs according to datacenter deployment or cloud deployment. Differences are documented below.However, in both cases the image has Puppet installed, and the image is prep to be ran against the PuppetAgain. As well a configurations that Puppet needs to run or at the time made more sense to be done through MDT.
General MDT documentation: https://mana.mozilla.org/wiki/display/SYSADMIN/Microsoft+Deployment+Toolkit+2012+Update+1+General+Documentation
Windows 2008 Build Slave Configuration Managed by Microsoft Deployment Workbench Configuration
Starting Operating System
The process is begun with Windows Server 2008 R2 SP1 iso (en_windows_server_2008_r2_with_sp1_vl_build_x64_dvd_617403.iso). The iso file is mounted, in our case, using Virtual CloneDrive. Once the iso file is mounted it is then imported into the Microsoft Deployment Workbench (MDT).
Base Configuration Capture (MDT Task Sequence ID SW2008_BASE_001)
The modification here is found under tasks sequence steps -> State Restore -> Custom Tasks -> Mozilla Custom.
Applications
Microsoft Visual Studio 2010
- This application install has been customized.
Microsoft Visual Studio 2013 Update 3
Microsoft Windows Windows 8 SDK
Microsoft Windows Windows Direct X SDK
Microsoft Net Framework 3.5
Configuration
WSUS Updates