//
you're reading...

Provisioning Server

Provisioning Server: Adding servers to the farm

I’m setting up new Provisioning Servers in my lab. Here’s a step by step guide for adding a second Provisioning Server. <

Provisioning ServerW2K8-X64-PVS02 – Use Powershell to add the Provisioning Server Active Directory service account to the local administrators group and create the vDisk directory structure.

$user="lan/svc-pvs"
$group = [ADSI]("WinNT://"+$env:COMPUTERNAME+"/administrators,group")
$group.add("WinNT://$user,user")
mkdir D:\vDisk | ft Name -AutoSize
mkdir D:\vDisk\Production | ft Name -AutoSize
mkdir D:\vDisk\Development | ft Name -AutoSize
CACLS D:\vDisk /T /E /C /G lan\svc-pvs:F

image

Provisioning ServerW2K8-X64-PVS02 – Install Microsoft .Net 3.5 SP1. (You can do this with Powershell or Server Manager.)

image_thumb7

Provisioning ServerW2K8-X64-PVS02 – Download the Provisioning Server media and silently install the software.

image

The process documented below will demonstrate creating a Provisioning Server configuration answer file and silently configuring the new Provisioning Server.  THE SILENT CONFIGURATION WIZARD WILL CORRUPT THE BOOTSTRAP WHICH LEADS TO THE CONSOLE CRASHING WHEN “CONFIGURE BOOTSTRAP” IS USED.

If you’re not trying to automate your builds I would recommend using the GUI to configure your servers.  The screenshots from the previous post can be referenced if you want to use the Configuration Wizard GUI.

Provisioning ServerW2K8-X64-PVS01Running the Configuration Wizard Silently – Logon the first Provisioning Server (W2K8-X64-PVS01) and create an answer file using “ConfigWizard.exe /s” (see screenshot).

The default configuration options should be correct so you can click next on most of the screens except for the “Farm Configuration” – select “Join existing farm” and “Store” – select “Production”.

image

image

image

Provisioning Server – Copy the ConfigWizard.ans file to the new Provisioning Server (W2K8-X64-PVS02).

image

Provisioning ServerW2K8-X64-PVS02 – Open the ConfigWizard.ans file on the new provisioning server and modify the “StreamNetworkAdapter” with the new Provisioning Server’s IP address. Save the file.

image

Provisioning Server – On the new Provisioning Server – Run “ConfigWizard.exe /a” with the path to the .ans file to configure the new Provisioning Server.

image

Provisioning Server – Open the Provisioning Services Console and expand the server node.  Verify the new server has been added.

image

Provisioning Server – Right click the server and adjust it’s properties.

image

image

image

You will need to apply the hotfix mentioned here.

 

Configure Bootstrap

Open the Provisioning Services Console, expand the Farm, Sites, Site, and Servers.  Right click a server and click “Configure Bootstrap”

image

Click Read Servers from Database and click OK.

You can configure the order of the servers.  I usually put the server I’m configuring first in the list.

image

Repeat for the other servers.

image

You can have 4 servers listed in the bootstrap.