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 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 varies away from the typical MDT install. The files needed to be extracted from the iso and have the F# portion removed. The extracted files are then copied over local, and the installation command is ran

Microsoft Visual Studio 2013 Update 3

• A reboot needs to occur between the installation of 2010 and 2013
  

Microsoft Windows Windows 8 SDK

Microsoft Windows Windows Direct X SDK

Microsoft Net Framework 3.5

Configuration

WSUS Updates

• Various registry settings are needed
  • Refrence: https://bugzilla.mozilla.org/show_bug.cgi?id=972575
    

Data Center Deployment Configuration (MDT Task Sequence SW2008_DPLY_001)

The modification here is found under tasks sequence steps -> State Restore -> Custom Tasks -> Mozilla Custom.

Applications

Puppet

• Package installation
  • This installs version 3.4.3
  • Future updates will be managed through Puppet
• Kill the Puppet service
  • In order to control when Puppet runs
• Set Puppet Registry bits
  • "Type"=dword:00000010
  • "Start"=dword:00000003
  • "ErrorControl"=dword:00000001
• Copy over WGET from "Z:\Applications\WGET" to "C:\Windows\System32"
  • Needed to run the Puppetize vbs to obtain certs
• Copy over puppet.conf from Z:\Applications\Puppet Puppet\puppet.conf" to "C:\programdata\Puppetlabs\puppet\etc\"
  • A copy of pupept.conf is needed prior to the Pupeptize vbs being ran
  • After this initial copy the file is managed by Puppet
• Copy over the Pupeptize vbs from "Z:\Scripts\" to "C:\ProgramData\Puppetlabs\puppet\var\"
• Run Puppetize vbs
• Run Puppet
  

Configuration

Rename Administrator to root

• Copy over security template, root.inf, from "Z:\Files\root"
• Apply template cmd /c secedit /configure /db %temp%\temp.sdb /cfg C:\root.inf
• Set registry so that root may continue to auto-login during task sequence execution
  

Set a os_version "reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Environment" /v os_version /t REG_SZ /d 2008"

• • For Puppet use. Currently there is no facter fact to differentiate between Windows OSes
    

Disable Server Manager Window "reg add HKCU\Software\Microsoft\ServerManager /t REG_DWORD /v DoNotOpenServerManagerAtLogon /d 1 /f

• Because the registry setting is HKey current user it is quite difficult to implement through Puppet
  • Needs to be done after reboot post Puppet run

Cloud Deploy Configuration Capture (MDT Task Sequence ID W2008_CLD_002)

The modification here is found under tasks sequence steps -> State Restore -> Custom Tasks -> Mozilla Custom.

Puppet

• Package installation
  • This installs version 3.4.3
  • Future updates will be managed through Puppet
• Kill the Puppet service
  • In order to control when Puppet runs
• Copy over WGET from "Z:\Applications\WGET" to "C:\Windows\System32"
  • Needed to run the Puppetize vbs to obtain certs
• Copy over puppet.conf from Z:\Applications\Puppet Puppet\puppet.conf" to "C:\programdata\Puppetlabs\puppet\etc\"
  • A copy of pupept.conf is needed prior to the Pupeptize vbs being ran
  • After this initial copy the file is managed by Puppet
• Copy over the Pupeptize vbs from "Z:\Scripts\" to "C:\ProgramData\Puppetlabs\puppet\var\"
• Run Puppetize vbs
• Run Puppet
  

EC2 config service

• Installation ""Z:\Applications\AWS EC2config service\Ec2Install.exe" /passive /norestart2config service\"

Citrix PV

• Copy from "Z:\Applications\Citrix-Win_PV" to "c:\Citrix-Win"
• "C:\Citrix-Win\upgrade.bat" to install

Configuration

Rename Administrator to root

• Copy over security template, root.inf, from "Z:\Files\root"
• Apply template cmd /c secedit /configure /db %temp%\temp.sdb /cfg C:\root.inf
• Set registry so that root may continue to auto-login during task sequence execution
  

Set a os_version "reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Environment" /v os_version /t REG_SZ /d 2008"

• • For Puppet use. Currently there is no facter fact to differentiate between Windows OSes