Tuesday, January 27, 2009

WDS and server 2008 - WDS and DHCP on separate boxes.

NB: After installing WDS – REBOOT!!!!

 

http://www.infotechguyz.com/server2008/wds.html

 

 

Free system imaging solution ? Server 2008 Windows Deployment Services (WDS)?

Server 2008 Windows Deployment Services (WDS) replaces Remote
Installation Services (RIS) offered in Windows Server 2003 and 2000. WDS use PXE and TFTP to boot from WDS server.

The main difference between Windows Deployment Services (WDS) and other imaging solutions like Ghost is that WDS uses file-based imaging format where others use sector based. WIM format uses single instance store which files are stored only once and referenced multiple times. As result, images are a lot smaller.

Windows Deployment Services (WDS) supported OSes:
- Windows XP
- Windows Server 2003
- Windows Vista
- Windows Server 2008

 

How to install and configure Server 2008 Windows Deployment Services (WDS)

Server 2008 Windows Deployment Services (WDS) prerequisites

- WDS server must be a member server of an Active Directory domain
- DHCP must be configured for PXE boot to work
- DNS, you will mostly have this.
- OS media
- NTFS partition on the WDS server
- Server 2008

To install Windows Deployment Services (WDS) on Server 2008

open server manager > Click on Add Roles link > click Next > on the Select Server Roles screen, select Windows Deployment Services, and
then click Next.

On the Role Services screen, verify that Deployment Server and Transport
Server are checked; then click Next, then click Install

Start > Administrative Tools > Windows Deployment Services to access
the Windows Deployment Services Management console.
Choose the path to where images will stored.
Configure PXE Server settings, choose “Respond to all”, and Click finish.

Add a Boot Image to WDS Server

Boot image is the image file used during pre-installation OS, also known as boot OS and delivered via PXE boot.

1. Start > Administrative Tools > Windows Deployment Services to access
the Windows Deployment Services Management console
2. Right click the Boot Images node. Then click Add Boot Image
3. Click Browse to locate the boot image you wish to add. (Use the Boot.wim from the Windows Server 2008 installation DVD)
4. Once completed, you should be able to see this image you when perform a PXE boot.


Create a Capture Boot Image

Capture Boot Image is a boot image used when capturing images. You will use capture image to boot a server/client to capture its image into a .wim file. You can create a capture boot image by using the Boot.wim from the Windows Server 2008 installation DVD.

1. Start > Administrative Tools > Windows Deployment Services to access
the Windows Deployment Services Management console.
2. expand the Boot Images node
3. Right click the image you added earlier (See step 2 from Add a Boot Image to WDS Server)
4. Click Create Capture Boot Image
5. Once completed, click Finish.
6. Right click on boot image folder, choose "Add Boot Image"
7. Select the capture boot image we just created and click Next
8. Once completed, you should be able to use this boot image to capture Operating System images


Create an Install Image (create an image)

Install image includes the OS, custom applications and settings. It is most likely that you will have an install image for every OS you support.

1. Create a base computer (A computer that includes the OS, custom applications and settings).
2. Install sysprep.exe (If you are using windows 2003 or XP, you can find it deploy.cab of Installation CD,), note: sysprep is included by default in Server 2008
3. Run sysprep.exe on the base computer (on XP, sysprep –mini –reseal –forceshutdown )
4. Verify that the base computer is connected to the network and powered on the system
5. Perform a network boot (Often you can do this with the F12 key)
6. In the boot menu screen, select the capture boot image that you created earlier
7. Choose the source drive and enter a name and description for the image. Click Next. Note: only Sysprep drives will appear)
8. Choose "Browse" to select a destination for the image. Enter a name and click "Save", Select "Upload image to WDS Server"
9. Enter the name of the WDS server, and then click Connect.
10. Provide a user name and password if prompted
11. Select the "Image Group" from the list
12. Click "Finish"
13. Now, you should be able to install this image to a server/client via PXE boot.


Install an Install Image (restore an image)

This process restores the Install Image we created earlier.

1. Configure your BIOS to enable PXE boot (aka Network Boot)
2. Perform a network boot (usually by press F12)
3. Select the boot image from the boot menu.
4. WDS will load the computer into GUI and follow the wizard.

 

At the Datamail Group we value teamwork, respect, achievement, client focus, and courage.  This email with any attachments is confidential and may be subject to legal privilege.   If it is not intended for you please advise by replying immediately, destroy it and do not  copy, disclose or use it in any way.  The Datamail Group, through our GoGreen programme, is committed to environmental sustainability.   Help us in our efforts by not printing this email. __________________________________________________________________   This email has been scanned by the DMZGlobal Business Quality               Electronic Messaging Suite. Please see http://www.dmzglobal.com/dmzmessaging.htm for details. __________________________________________________________________  

Saturday, January 17, 2009

What should have been a joy became a disaster....

So I got myself a new monitor - A samsung 32" 1080p LCD (cost $150 NZD more than comparable 26" monitor after some strong negotiations so great option and the desktop real estate is HUGE!

Anyway, current ATI drivers for onboard chipset (790G) couldn't scale to 1080p, cue several frsutratiing hours of installing adn uninstalling latest ATI drivers (8.12) for Windows Server 2008 x64 (which is my 'PC' and HyperV host....you can see where this is heading...)

No dice, just cannot get the server to recognise the driver install

Desparate times so I rebuilt the system thinking HyperV's will easily restart with minimal fuss. Oh. No. They. Won't.

Monitor looks great now with older drivers off DVD that came with mobo so start VMs (discover you need to create NEW>Pick your old VHD file. All systems (including a DC started OK but weird things started happening - getting unauthenticated in the network centre, needing to rework the DC. End result was drop VMs from domain and re add.

Unfortunately on my Kerio mail server this blew away ALL my mail - could not find it at all.

Arrrgh!

After much googling found some help here:

http://jigar-mehta.blogspot.com/2008/02/how-do-i-extract-file-from-virtual-hard.html

Identified that I actually had snapshots (AVHD) of my mail server disk that were a lot bigger than the original VHD so using winimage was able to open these up and extract most of my email.

HyperV - you b@stard!

My fault I'm sure but you gotta learn somewhere the old adage, "There are 2 kinds of people in the world, those who backup and those who will backup"