Deployment Solution

Hi,

I am using Deployment Server 6.9 SP5 on Windows 2003 server. I have a lot of images stored in the server but cant use PXE.

Is there a way I can network boot the client computers to connect to the server and image the machines? Either using a USB drive or CD.

This is urgent any help is appreciated.

Thanks.

You can utilize the Boot Disk Creator in the Deployment Console.  This is in the Tools menu.

Using boot disc creator you can create a boot disc on USB and CD both. You can also use automation partition if the client is already connected to DS.

Take a look at here: http://www.symantec.com/docs/HOWTO9572

Thanks.

In the instructions, there is a point where it says we have to add an image to the DVD or USB. If my understanding is correct, this executes rdeploy from the DVD or USB?

I don't want to do this, I just want to network boot the computer so that it conencts to server and I can execute the rdeploy from the dos prompt manually.

Regards,

Avinash

When you launch Boot Disk Creator, it will display a welcome screen asking if you would like to create a new configuration or if you would like to go to the boot disk creator interface.  Choose to go to the boot disk creator interface.

Select your OS configuration that you want (assuming that you have more than one).

The click File --> Create Boot Disk.  On the right side it will give you three options.  You are looking for "Network boot".

Follow the prompts.  This should do what you are looking for.

Hi Guys,

I am trying to create a proper automation partition for client machines because we are not able to use PXE. I did this using the boot disk creator and on the USB. I was able to install the automation partition on the client computer but, the client network stops with an error "Unable to load tcp" and Network Card driver not installed error.

I am using HP XW4400 workstations with Broadcom Gigabit Ethernet Card and I believe I have chosen the correct network card driver.

Surprisingly, I am not able to find the option to choose Universal NIC driver while creating the boot disk.

Can anyone help me resolve this issue?

Thanks,

Hi Avinash,

It looks to me like you are wildly trying everything apart from reading the documentation in order to get this to work.... ;-)

II think you are creating a DOS automation partition, and this TCP error means you have not updated BootDisk creator with the correct DOS drivers for your NIC.

Next, UNDI is only available from the PXE stack, which is to say you have to PXE boot your machine in order to utilise this driver. You cannot use the UNDI driver from any other boot mechanism. This is not an Altiris limitation -this is just the way PXE works.

For various reasons (including troublesome machines), I have a VMWare install of Deployment Server with a bridged NIC. This allow me to test all this kind of stuff at my desk without having to bother initially with the various network pains. Once I'm happy that my Uber-simple config works, I can push the fruits of my labour up to one of our main servers.

Kind Regards,
Ian./