Create a Boot Image

First thing that needs to be done is configure a boot image which will allow client machines to PXE boot into and give us a basic interface so we can choose the installation image (which we’ll cover later)

To create a boot image you need access to an operating system DVD disk or have an expanded ISO image. From my own experience it is best to use the latest operating system for the boot image as latter OS installations using an earlier PXE / boot image can cause problems. I am using the source files from Windows 2008 R2 which I downloaded from my TecthNet subscription and expanded using WinRAR

• Start Windows Deployment Services (located under Start > Control Panel > Administrative Tools > Windows Deployment Services)
• Navigate to “Boot Images” under your WDS Server of the MMC
• Right click and select “Add Boot Image”

• In the new dialogue box window navigate to the folder location where you have expanded the DVD ISO image or the DVD drive with a Operating System
• Select the “Sources” folder from the OS source files root
• Click the file boot.wim which is a Windows Imaging Format

• Confirm your selection is correct and then select Next
• You can then rename the images or leave the defaults, I’ve left the default values; click Next

The image will now be loaded to the WDS server and a summary screen displayed if the task completes successfully.

The next step is optional but I’d recommend setting a default boot image so clients can boot into an image without waiting for a choice to be made.

• Click on your WDS server so that it has the focus and right click to select “Properties”

• Select the tab “Boot” from the “Properties” dialogue box

Use the Select button to choose the boot image file that we uploaded a minute ago; in my case I’m using Windows 2008 R2 which is only 64bit and so the choice is easy I just select the boot.wim for the x64 architecture.

Installation Image

Setting up the installation image is very similar to the boot image, but you may want to create a folder structure to make the separation of different OS easier.

• Start Windows Deployment Services (located under Start > Control Panel > Administrative Tools > Windows Deployment Services)
• Navigate to “Install Images” under your WDS Server of the MMC
• Right click and select “Add Image Group”
• Choose a name for the image group, in this case I am using Windows 2008 R2 so I’ve created a Image group called “W2K8R2-Images”; Select “Ok”
• Now right click on the newly created “Image Group” and select “Add Install Image”
• In the new dialogue box window navigate to the folder location where you have expanded the DVD ISO image or the DVD drive with a Operating System
• Select the “Sources” folder from the OS source files root
• Click the file install.wim which is a Windows Imaging Format and Open

You then have a list of available images within the image file that was just selected. You can leave the default option and select all images or you can remove the ticks to only include images you know you are going to use

• Select “Next” and your choice with be "summarised” for you to check and select “Next” again

The image will now be loaded to the WDS server and a summary screen displayed if the task completes successfully.

Now the WDS server has a boot image and install images

Testing the WDS Configuration

Make sure your client computer or Hyper-V instance is enabled for PXE (or network boot) and this selected as the client boots up.

In the first article in this series I suggested that Unknown Clients continue automatically unless Esc is pressed. Clients will start the PXE process but will then be held for approval on the WDS server, the client will look like:

The client will need to be approved on the WDS server

Start up WDS, if it is not already running

• Navigate to the “Pending Devices” folder and highlight the request ID (note the number on client matches that on the server.
• Right-click and select “Name and Approve”

The client machine after a few seconds will continue PXE boot using the boot image we created.

Once the boot process has completed the splash screen will appear and clearly indicates we have booted using Windows Deployment Services

Click Next and you are prompted for a username and password to authenticate (this can be used to allocate images based on security settings)

Once authenticated a list of images are presented which you can choose from to install. (note this screenshot shows more images than I covered during the install image section)

Next screen should be familiar as it asks “Where do you want to install Windows?” Accept the default and click Next

Windows will now Install

That’s it the process can be streamlined by using unattend.xml files to skip all of the screens above as well as granular control of the OS deployment. But that is not for this article…

It is interesting to see which technologies on offer from SharePoint get people excited and enthused about adoption. From my perspective I’m seeing a pattern emerge as we attend more of these meetings:

- Forms automation is something that people definitely understand and want to explore. I think all departments have a need for form completion which is currently often paper, Word or Excel based. The ability to automatically complete elements of a form based on external data from things like Active Directory is appealing.

- Workflow again is a function that people seem to get very excited about, probably because it is easy to understand how it can save time. Many administrative tasks are ripe for workflow automation and approval which can reduce the overall burden of daily office life.

- Document Management is common to every department and the same themes run through discussions with different business areas. Finding up to date documents is key to so many tasks, think about writing a document and what template do you need to use? How can you be sure you are reading the most up to date document? Before SharePoint people send documents in emails this can easily spawn multiple copies and no overall master. Finally, with the ever increasing compliance requirements in business how can we classify a document at point of creation.? SharePoint answers all these requirements in a single unified interface.

Logistics

The meeting was organised by BTEngageIT whom we have worked with to deploy our SharePoint infrastructure. More importantly they explained the importance of end user adoption and how it is imperative to get business involvement at the early stages. The same was a reoccurring theme during the recent SharePoint Evolution conference which I was lucky enough to attend. Microsoft carried out the presentations and demo’s at their Cardinal Place offices in Victoria which is a very pleasant and modern office. I now have another blog to keep an eye on, as the presentation was very well by delivered by Jessica Meats.

Next Steps

To drive the next stage of adoption it is clear we have a growing body of interested stakeholders. It is also clear that we can’t do everything at once, especially if we want to do things well. So we’ll be trying to identify a top-ten list and prioritise the first five that will have the largest appeal across all departments.

In order to do this properly we’ll follow up with a business justification and resource requirement. We’ve realised that we don’t necessarily have the right skill set internally to do the analysis and delivery, especially as we support our existing infrastructure and user demands. That’ll be the topic of another post.

So how do we install WDS? Well I’m using Windows 2008 R2 for this installation on a separate server to the rest of my environment. You are going to need an existing infrastructure of Windows Active Directory, DHCP and DNS already installed to make use of WDS.

Installing WDS

Windows Deployment Services is a role (as opposed to a feature of Windows 2008 R2) and it can be installed via server manager.

Once the wizard starts for the Add Role you can navigate to and select “Windows Deployment Services” checkbox

• Click next and you can read the WDS Overview
• Next, leave the default of “Deployment Server” and “Transport Server” checked
• Next again and you get a summary of options prior to the installation of WDS finally click “Install”

After a short period of time you should receive a message confirming the installation has been successful and we can move on to the configuration.

Configuring WDS

Once you close the role dialogue box after the installation of WDS you’ll be back to the “Server Manager” interface and have “Windows Deployment Services” added to the Roles list (if you closed Server Manager then Windows Deployment Services is available under Administrative Tools).

The first time you expand out WDS you’ll see your server and it will have a yellow explanation triangle and the main element of the MMC will have a message:



So lets go ahead and configure our new installation

• Right click or under More Actions in the Right Actions Toolbar of the MMC select “Configure Server”
• Read the initial advice and select “Next”. You’ll be asked for a directory to hold “Remote Installation” files, as this will hold images you’ll probably want to change the default from “C:\RemoteInstall” to a data drive.
• Next your are asked about where your DHCP server is installed, if it is on the the same server as WDS then you’ll need to select both check boxes. If your DHCP server is on another server but on the same subnet then don’t select either check box. Anything else and you’ll need to read the help file for further guidance.
• Now you need to determine how you want the WDS server to respond to clients as they boot up and go through the PXE boot process. For most implementations you’ll probably find the last option works best:

The configuration wizard will now copy files to the location you selected earlier for the RemoteInstall directory.

Once the copy process completes you have the option to upload images or you can do this later, which is what I’ll show you in a bit.

Click Finish and you’re returned to the main MMC window and the WDS server will now be green with additional folders created underneath the main element.

Post Wizard Configuration

The wizard sets most parameters or asks you for choices as above, but a couple of other settings may need to be changed. From my own experimenting I’d recommend changing the following from the Properties of the WDS Server element in the MMC

• First of all you’ll probably want to create computer accounts in a specific OU of your Active Directory. Select the “AD DS” tab from the Properties of your WDS server
• Under “Computer Account Location” select browse and navigate to the OU where you want your computer accounts to be created. In my environment I’ve created a root OU to hold computer accounts for SharePoint

Note: You need to delegate control of the OU you choose to the computer account of the WDS Server so that it can create computer accounts.

• From Active Directory Users and Computers MMC select the OU that you are going to use for the computer accounts
• Right click the OU and select “Delegate Control” to start a wizard
• Select Next then Add
• In the standard AD search box you’ll need to add Computers from “Object Types” then enter the name of your WDS computer
• Click next; then “Create a custom task to delegate”
• Change the default option to “Only the following objects in the folder:” click “Create selected objects in this folder” and then select “Computer Objects” from the list
• Click Next make sure “General” is selected and from “Permissions check Full Control”
• Confirm the options on the Summary screen and click Finish

• You may also want to review how the client machine is handled by the WDS server during PXE boot. PXE boot downloads a small package via TFTP (Trivial File Transfer Protocol) to enable the machine to boot via the network card and initialise the WDS boot image.
• I’d recommend handling known clients differently to unknown clients as the latter implies machines that are new and need an OS installed. To review or make changes select the “Boot” tab from the WDS Server Properties:

That’s it for the configuration, we just need to add some images which I’ll cover in my next article.

- Windows 2008 R2 server running SQL Server 2008 (it’ll probably be SQL 2008 R2 as this also went RTM this week)

- Windows 2008 R2 running IIS as a web frontend server

- Windows 2008 R2 to run Index service for SharePoint

It’ll be a bit of a pain creating these servers manually so I want to do it automatically. Microsoft Windows 2008 has a role called Windows Deployment Services, or WDS, which for anyone that has been an ITPro for a while is the new name for RIS (Remote Installation Service).

The next post in my SharePoint 2010 series will covering the setup, configuration and use of WDS to create the new environment. If you want a more detailed and generic approach to WDS they have a look at TechNet.