ADS boot to DA fails during PXE

We are trying to image a Dell server, where previously we have only
been imaging HP servers. Problem is, we can't get the Dell server to
PXE. Well, we can get it to PXE, but the image doesn't complete, it
fails and reboots.

We figure we are missing some drivers, but not sure which ones? The
image gets to about 90% before it fails. I say it's the SCSI
controller, my boss says it's the NIC card. It's possible we are both
right, or we are both wrong. But since we have to get approval to
download drivers from the internet for use on the network, we would
rather ask for the drivers we need rather than ask for alot of
unnecessary files.

Thanks for the help!

Mike

Hello Mike,

may be the KB article 841550 is helpful for you.
In case that the DA could not loaded it is in the most times a missing NIC
driver. But you can check this in the event log or if you enable the tracing
for the service "ADS Deployment Agent Builder". How you can do this is
described in the online help of ADS.

--
Mit freundlichen Grüßen / Kind regards - Alexander Ortha (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.

"Special Access" <nonyabidnezz@hotmail.com> wrote in message
news:9raob2pf1qo606od1meed6qpfkb2igomdt@4ax.com...
> We are trying to image a Dell server, where previously we have only
> been imaging HP servers. Problem is, we can't get the Dell server to
> PXE. Well, we can get it to PXE, but the image doesn't complete, it
> fails and reboots.
>
> We figure we are missing some drivers, but not sure which ones? The
> image gets to about 90% before it fails. I say it's the SCSI
> controller, my boss says it's the NIC card. It's possible we are both
> right, or we are both wrong. But since we have to get approval to
> download drivers from the internet for use on the network, we would
> rather ask for the drivers we need rather than ask for alot of
> unnecessary files.
>
> Thanks for the help!
>
> Mike

On Tue, 18 Jul 2006 16:27:47 +0200, "Alexander Ortha [MS]"
<alexor@online.microsoft.com> wrote:

>Hello Mike,
>
>may be the KB article 841550 is helpful for you.
>In case that the DA could not loaded it is in the most times a missing NIC
>driver. But you can check this in the event log or if you enable the tracing
>for the service "ADS Deployment Agent Builder". How you can do this is
>described in the online help of ADS.

Thanks for the reply. We put the drivers for both the NIC and the
RAID in the \presystem folder and stopped/restarted the DA Builder
service. Unfortunately, it still fails at the same point.

I'll check out the article tonight and see what happens.

We contacted MS today to get the second of the hotfixes for ADS 1.0
for the improper parsing of INF files. Yes, we know that ADS 1.1 is
available, but our "masters of the universe" haven't approved it's use
as yet... and being the massive gathering of non-technical minds they
are will undoubtedly grant us the right to use ADS 1.1 when ADS 3.4 is
released <grin>

Mike

Hello Mike,

if you use ADS 1.0 you need both hotfixes. The hotfix KB830413 is for ADS,
the hotfix KB829053 is for the OS.
If you have the chance to use ADS 1.1 you have a lot of performance advances
and other new features.

--
Mit freundlichen Grüßen / Kind regards - Alexander Ortha (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.

"Special Access" <nonyabidnezz@hotmail.com> wrote in message
news:m9vqb216aos6monnhsfu0tfhl4ovucdibv@4ax.com...
> On Tue, 18 Jul 2006 16:27:47 +0200, "Alexander Ortha [MS]"
> <alexor@online.microsoft.com> wrote:
>
>>Hello Mike,
>>
>>may be the KB article 841550 is helpful for you.
>>In case that the DA could not loaded it is in the most times a missing NIC
>>driver. But you can check this in the event log or if you enable the
>>tracing
>>for the service "ADS Deployment Agent Builder". How you can do this is
>>described in the online help of ADS.
>
> Thanks for the reply. We put the drivers for both the NIC and the
> RAID in the \presystem folder and stopped/restarted the DA Builder
> service. Unfortunately, it still fails at the same point.
>
> I'll check out the article tonight and see what happens.
>
> We contacted MS today to get the second of the hotfixes for ADS 1.0
> for the improper parsing of INF files. Yes, we know that ADS 1.1 is
> available, but our "masters of the universe" haven't approved it's use
> as yet... and being the massive gathering of non-technical minds they
> are will undoubtedly grant us the right to use ADS 1.1 when ADS 3.4 is
> released <grin>
>
> Mike

On Wed, 19 Jul 2006 04:32:47 +0200, "Alexander Ortha [MS]"
<alexor@online.microsoft.com> wrote:

>Hello Mike,
>
>if you use ADS 1.0 you need both hotfixes. The hotfix KB830413 is for ADS,
>the hotfix KB829053 is for the OS.
>If you have the chance to use ADS 1.1 you have a lot of performance advances
>and other new features.

I tried to find a list of the changes, but it doesn't seem to exist on
the site. Do you have a pointer or a URL, or a text file that gives
the updates from 1.0 to 1.1?

We got the second hotfix from MS yesterday and it will be installed
today. Hopefully that will fix the issue. I have also downloaded
1.1, but until those "folks" approve it's use I can't even install it
<sigh>

Thanks again for the info!

Mike

Hello Mike,

you can find the new features of ADS 1.1 in the Online Help of ADS 1.1. Look
into the doc directory of your ADS 1.1 download
Here is the snip from the online help:
------ snip

What's new in this version of ADS
This release of ADS includes the following changes.

Introduction of Windows PE 2005 as a minimal operating system for ADS
operations
This provides an alternative RAM disk boot environment to the dynamically
built Deployment Agent. Microsoft Windows Preinstallation Environment
(Windows PE) 2005 is a minimal Win32 subsystem with limited services, based
on the Windows kernel running in protected mode. For more information, see
Planning for the use of Windows PE in Automated Deployment Services.
Introduction of three new tools
ADS now includes these tools:
a.. Adspart.exe. This is the task-sequence tool you use for partitioning
tasks on devices running Windows PE. You can use this tool to create,
activate, and delete partitions and display disk geometry. For more
information, see adspart.exe.
b.. Adsrepository. This is a command-line tool that you can use to
manage the repository of files that comprise Windows PE images. ADS uses
these files to create Windows PE RAM disk images that can be used as minimal
operating systems. For more information, see adsrepository.
c.. Adsrunas.exe. This is a task-sequence tool that you can use to run
tools and programs and execute commands with a different user account and
permissions than the Administration Agent. For more information, see
adsrunas.exe.
Introduction of support for devices running a 64-bit operating system
You can now perform an unattended setup of a 64-bit operating system by
using a 64-bit version of Windows PE. ADS now includes a 64-bit
Administration Agent so you can remotely manage devices running a supported
version of a 64-bit operating system. For more information, see ADS agents
overview.
Introduction of the /controller/adsdevice command
You can use this new command in a job or task sequence to automatically
modify a device's default job template, specify a Windows PE repository, or
release control of a device. With the introduction of this command, you can
now choose whether you want to install the Administration Agent on the
Controller. The Administration Agent is used on the Controller to run tasks
that perform actions on the Controller, such as running a script or updating
the Controller database. For more information about the command, see
/controller/adsdevice.
Introduction of a method to change device control state in bulk
You can use the new ManageList method of the Devices object to change the
status of group of devices by making one call. This is a faster way to
change the control state of multiple devices. For more information, see
Devices.ManageList.
Changes to certificate management
During a new installation of ADS, Setup automatically creates the ADS
public key infrastructure (PKI) when you install the Controller, Network
Boot Services (NBS), or the Image Distribution service. The option of not
creating a PKI has been removed from Setup. If you perform an upgrade, Setup
uses the existing PKI automatically if it was created by ADS tools. This
version of ADS does not support importing or using a custom PKI, which is a
PKI created with non-ADS tools. For more information about the ADS PKI, see
ADS certificates overview. For more information about upgrading ADS, see
Planning for an upgrade of Automated Deployment Services.
Removal of the virtual floppy disk image Vfloppy.vfi and changes in
support for virtual floppy disk images
Vfloppy.vfi is no longer included with ADS, and technical support is not
provided for virtual floppy disk images. The Dskimage tool is still included
with ADS for maintaining your existing virtual floppy disk images. For
information about how an upgrade can be affected by this change, see
Planning for the use of Windows PE in Automated Deployment Services. The
introduction of Windows PE as a minimal operating system provides an
alternative to using virtual floppy disk images for performing hardware
configuration and other pre-deployment tasks.
Multiple imaging sessions
You can run one or more imaging jobs concurrently by configuring the Image
Distribution service. You also can bind the Image Distribution service to as
many as four network adapters. For instructions, see To configure the Image
Distribution service. For an overview of the Image Distribution service, see
Image deployment infrastructure.
Imaging of simple dynamic volumes.
You can use ADS imaging tools to capture and deploy simple dynamic volumes
of a primary partition. For more information, see Images overview.
Automatic device control
You can now configure the ADS Controller to automatically discover new
devices, add the devices to the database, set a job template, control the
devices, and run a task sequence on those devices. Controller service
property settings determine how the Controller responds to devices. For more
information, see Controller service properties.
Sequence Editor improvements
Sequence Editor includes a generic command that you can use to add and
modify tasks in your task sequences that are not available from the Action
menu. For more information, see Creating and modifying task sequences. For
general information about using task sequences, see Task sequence overview.
Simpler BMDP and BMCP port configuration
BMDP and BMCP ports can now be configured without applying a security
update. For more information, see Communication ports used by ADS.

snip----

--
Mit freundlichen Grüßen / Kind regards - Alexander Ortha (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.

"Special Access" <nonyabidnezz@hotmail.com> wrote in message
news:hourb2920bkg4u4ujkmd2irqj53ohmj3bj@4ax.com...
> On Wed, 19 Jul 2006 04:32:47 +0200, "Alexander Ortha [MS]"
> <alexor@online.microsoft.com> wrote:
>
>>Hello Mike,
>>
>>if you use ADS 1.0 you need both hotfixes. The hotfix KB830413 is for ADS,
>>the hotfix KB829053 is for the OS.
>>If you have the chance to use ADS 1.1 you have a lot of performance
>>advances
>>and other new features.
>
> I tried to find a list of the changes, but it doesn't seem to exist on
> the site. Do you have a pointer or a URL, or a text file that gives
> the updates from 1.0 to 1.1?
>
> We got the second hotfix from MS yesterday and it will be installed
> today. Hopefully that will fix the issue. I have also downloaded
> 1.1, but until those "folks" approve it's use I can't even install it
> <sigh>
>
> Thanks again for the info!
>
> Mike

Hi,
I would love to put in my issue that we are facing with the new HPDL380 G5
Servers.
I ahve got ADS working perfectly with the G2, G3, and various G4 models that
we have. The NIC have definately changed in the G5 but using the supplied
drivers from HP dont help a bit. Can any one help...
Quote from a recent post by myself)

Hi We have a load of the new HP DL380 G5 servers.
I have set up a nice image that does a full install with all the patches,
extra software and works just excellently on all servers (HPDL380 G2->G4, and
any other server supported by the PSP 7.51).
Unfortunately these new servers have a new Nic which ADS 1.1 does not seem
to support.
I would like some pointers where / what to do to get me further.
The location that i copy the divers is "\Program Files\Microsoft
ADS\NBS\Repository\User\PreSystem" and the restarted the adsbuilder service
to compile these into the builder service.
It cannot find the nic (PCI - id) and fails to boot into the
This MS Kb article displays mostly the problem (but we are using ADS v1.1)
KB841550
Can anyone help?

I have enabled logging and have the results if they would help anyone - I am
thinking HP need different .inf files for these.

Regards,

Stu

"Alexander Ortha [MS]" wrote:

> Hello Mike,
>
> you can find the new features of ADS 1.1 in the Online Help of ADS 1.1. Look
> into the doc directory of your ADS 1.1 download
> Here is the snip from the online help:
> ------ snip
>
> What's new in this version of ADS
> This release of ADS includes the following changes.
>
> Introduction of Windows PE 2005 as a minimal operating system for ADS
> operations
> This provides an alternative RAM disk boot environment to the dynamically
> built Deployment Agent. Microsoft Windows Preinstallation Environment
> (Windows PE) 2005 is a minimal Win32 subsystem with limited services, based
> on the Windows kernel running in protected mode. For more information, see
> Planning for the use of Windows PE in Automated Deployment Services.
> Introduction of three new tools
> ADS now includes these tools:
> a.. Adspart.exe. This is the task-sequence tool you use for partitioning
> tasks on devices running Windows PE. You can use this tool to create,
> activate, and delete partitions and display disk geometry. For more
> information, see adspart.exe.
> b.. Adsrepository. This is a command-line tool that you can use to
> manage the repository of files that comprise Windows PE images. ADS uses
> these files to create Windows PE RAM disk images that can be used as minimal
> operating systems. For more information, see adsrepository.
> c.. Adsrunas.exe. This is a task-sequence tool that you can use to run
> tools and programs and execute commands with a different user account and
> permissions than the Administration Agent. For more information, see
> adsrunas.exe.
> Introduction of support for devices running a 64-bit operating system
> You can now perform an unattended setup of a 64-bit operating system by
> using a 64-bit version of Windows PE. ADS now includes a 64-bit
> Administration Agent so you can remotely manage devices running a supported
> version of a 64-bit operating system. For more information, see ADS agents
> overview.
> Introduction of the /controller/adsdevice command
> You can use this new command in a job or task sequence to automatically
> modify a device's default job template, specify a Windows PE repository, or
> release control of a device. With the introduction of this command, you can
> now choose whether you want to install the Administration Agent on the
> Controller. The Administration Agent is used on the Controller to run tasks
> that perform actions on the Controller, such as running a script or updating
> the Controller database. For more information about the command, see
> /controller/adsdevice.
> Introduction of a method to change device control state in bulk
> You can use the new ManageList method of the Devices object to change the
> status of group of devices by making one call. This is a faster way to
> change the control state of multiple devices. For more information, see
> Devices.ManageList.
> Changes to certificate management
> During a new installation of ADS, Setup automatically creates the ADS
> public key infrastructure (PKI) when you install the Controller, Network
> Boot Services (NBS), or the Image Distribution service. The option of not
> creating a PKI has been removed from Setup. If you perform an upgrade, Setup
> uses the existing PKI automatically if it was created by ADS tools. This
> version of ADS does not support importing or using a custom PKI, which is a
> PKI created with non-ADS tools. For more information about the ADS PKI, see
> ADS certificates overview. For more information about upgrading ADS, see
> Planning for an upgrade of Automated Deployment Services.
> Removal of the virtual floppy disk image Vfloppy.vfi and changes in
> support for virtual floppy disk images
> Vfloppy.vfi is no longer included with ADS, and technical support is not
> provided for virtual floppy disk images. The Dskimage tool is still included
> with ADS for maintaining your existing virtual floppy disk images. For
> information about how an upgrade can be affected by this change, see
> Planning for the use of Windows PE in Automated Deployment Services. The
> introduction of Windows PE as a minimal operating system provides an
> alternative to using virtual floppy disk images for performing hardware
> configuration and other pre-deployment tasks.
> Multiple imaging sessions
> You can run one or more imaging jobs concurrently by configuring the Image
> Distribution service. You also can bind the Image Distribution service to as
> many as four network adapters. For instructions, see To configure the Image
> Distribution service. For an overview of the Image Distribution service, see
> Image deployment infrastructure.
> Imaging of simple dynamic volumes.
> You can use ADS imaging tools to capture and deploy simple dynamic volumes
> of a primary partition. For more information, see Images overview.
> Automatic device control
> You can now configure the ADS Controller to automatically discover new
> devices, add the devices to the database, set a job template, control the
> devices, and run a task sequence on those devices. Controller service
> property settings determine how the Controller responds to devices. For more
> information, see Controller service properties.
> Sequence Editor improvements
> Sequence Editor includes a generic command that you can use to add and
> modify tasks in your task sequences that are not available from the Action
> menu. For more information, see Creating and modifying task sequences. For
> general information about using task sequences, see Task sequence overview.
> Simpler BMDP and BMCP port configuration
> BMDP and BMCP ports can now be configured without applying a security
> update. For more information, see Communication ports used by ADS.
>
> snip----
>
> --
> Mit freundlichen Grüßen / Kind regards - Alexander Ortha (Microsoft)
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Special Access" <nonyabidnezz@hotmail.com> wrote in message
> news:hourb2920bkg4u4ujkmd2irqj53ohmj3bj@4ax.com...
> > On Wed, 19 Jul 2006 04:32:47 +0200, "Alexander Ortha [MS]"
> > <alexor@online.microsoft.com> wrote:
> >
> >>Hello Mike,
> >>
> >>if you use ADS 1.0 you need both hotfixes. The hotfix KB830413 is for ADS,
> >>the hotfix KB829053 is for the OS.
> >>If you have the chance to use ADS 1.1 you have a lot of performance
> >>advances
> >>and other new features.
> >
> > I tried to find a list of the changes, but it doesn't seem to exist on
> > the site. Do you have a pointer or a URL, or a text file that gives
> > the updates from 1.0 to 1.1?
> >
> > We got the second hotfix from MS yesterday and it will be installed
> > today. Hopefully that will fix the issue. I have also downloaded
> > 1.1, but until those "folks" approve it's use I can't even install it
> > <sigh>
> >
> > Thanks again for the info!
> >
> > Mike
>
>
>

On Thu, 17 Aug 2006 21:34:05 -0700, Stu
<Stu@discussions.microsoft.com> wrote:

>Hi,
>I would love to put in my issue that we are facing with the new HPDL380 G5
>Servers.
>I ahve got ADS working perfectly with the G2, G3, and various G4 models that
>we have. The NIC have definately changed in the G5 but using the supplied
>drivers from HP dont help a bit. Can any one help...
>Quote from a recent post by myself)
>
>Hi We have a load of the new HP DL380 G5 servers.
>I have set up a nice image that does a full install with all the patches,
>extra software and works just excellently on all servers (HPDL380 G2->G4, and
>any other server supported by the PSP 7.51).
>Unfortunately these new servers have a new Nic which ADS 1.1 does not seem
>to support.
>I would like some pointers where / what to do to get me further.
>The location that i copy the divers is "\Program Files\Microsoft
>ADS\NBS\Repository\User\PreSystem" and the restarted the adsbuilder service
>to compile these into the builder service.
>It cannot find the nic (PCI - id) and fails to boot into the
>This MS Kb article displays mostly the problem (but we are using ADS v1.1)
>KB841550
>Can anyone help?
>
>I have enabled logging and have the results if they would help anyone - I am
>thinking HP need different .inf files for these.
>
>Regards,
>
>Stu
>
<snip>

Did you look in the presystem directory and insure the INF files were
converted to PNF (I think that the extension) and that they are not
being overwritten by other files on the same name for different items?
Have you verified the missing ID is in fact the NIC and not maybe the
RAID controller card?
(some things we found the hard way as well)

Mike

[Jeffrey.prashad1001]

Problem is that i have installed ADS 1.1 and i am trying to install the administration agent on a 64-bit operating system but keep getting this is not supported is there away around this thank you