Re: Getting started with ADS

Yes, this is 1.1 on SP1.

Now, what you're suggesting sounds reasonable but I have a Q about it:
Where would I have found this in the docs? I had the honest impression from
them that none of this was necessary for a couple reasons:
- If you don't have PE, don't worry, we have the Deployment Agent to fall
back on
- No indication that pre-staging the ADS server with vendor drivers, etc.,
is necessary nor a hint that anything is required beyond the base ADS install.

I'll take your suggestions and work that out but now I'm wondering what else
is not clearly spelled out in the otherwise excellent documentation. Please,
go ahead and paint me as an idiot so I can figure out what I should have
noticed already...if it's in there!

Thanks much, Alexander!

Greg Chapman

"Alexander Ortha [MS]" wrote:

Hello,

ok, first you should be use the ADS 1.1 version. This is the current version
of ADS and you could download this from the Microsoft-Website.
Is your ADS server a Windows Server 2003 SP1?

In you case, I think you should check that all necessary drivers are
integrated into the DA. How can you do this is in the KB article 841550
described. In the most cases you need to add the NIC drivers and the mass
storage driver to the DA.

If this not help to solve you problem, please send the XML file.

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

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

"Greg Chapman" <greg@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2uke12lqc410k767r5m4ki1qb48ro1885o@xxxxxxxxxx
Working through the initial phases of learning Automatic Deployment
Services on Windows Server 2003 and I've run into a bit of a bugger
which I haven't figured out. I've been reading all I can in pursuit of
a solution and it's time to ask some experts.

When I attempt to capture an image using the default sample, the
sysprep phase runs fine, but the part of the sequence which issues the
boot-to-da command doesn't appear to work right.

When I watch the boot sequence on the destination agent, I can see the
PXE boot stub come up and get its address and see that it receives the
instruction to "boot to Deployment Agent". Perfect!

Then the damned thing reboots and the job fails because "the system
was rebooted".

At no time do I see anything like what I expected (of course, finding
out what to expect is a real mystery) since my expectations were for
something like this:

" Windows Automated Deployment Services
Deployment Agent Version 1.0 Build 0000-000000-0000

DEPLOYMENT SERVICES
Boot Selection: ramdisk(0)\windows
Boot Options: RDBUILD
RDGUID={E597073D-BCA9-4935-8257-25530A5677D0} RDSERVERS=192.168.100.5
FASTDETECT ONECPU
PXE Server: 192.168.1.5

LOCAL NETWORK CONFIGURATION (PXE BOOT)
IP Address: 192.168.100.100
Gateway: 192.168.100.200
Subnet Mask: 192.168.1.10
MAC Address: 00-10-5A-11-16

DEPLOYMENT AGENT STATUS
Connected {192.168.1.34}: Valid BMCP message received at
00:00:00"

I never see this. Why?

The controller is an HP DL380 G4 running Windows Server 2003 Ent
Edition. The system I want to image is a similar HP DL380 G4 running
W2k3 Standard. I'm depending on the built in PXE boot services and
image builder because I haven't a copy of Windows PE.

Thanks!



.

Relevant Pages

  • Re: Getting started with ADS
    ... of ADS and you could download this from the Microsoft-Website. ... Is your ADS server a Windows Server 2003 SP1? ... When I watch the boot sequence on the destination agent, ... Deployment Agent Version 1.0 Build 0000-000000-0000 ...
    (microsoft.public.windows.server.setup)
  • Getting started with ADS
    ... Working through the initial phases of learning Automatic Deployment ... When I watch the boot sequence on the destination agent, ... Deployment Agent Version 1.0 Build 0000-000000-0000 ... The controller is an HP DL380 G4 running Windows Server 2003 Ent ...
    (microsoft.public.windows.server.setup)
  • Re: Boot Up
    ... system to boot when you boot up. ... system drive before reinstalling the Windows Server 2003. ... Click to clear "Hide protected operating system files. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.general)
  • Re: How to delete setup boot files
    ... automatically into XP Pro but the windows server option is still there. ... > [Boot Loader] ... >>> I am was creating a virtual machine on my pc to load Windows Server ... >> installation (such as installation folder, ...
    (microsoft.public.windows.server.general)
  • Re: Getting started with ADS
    ... tell that PXE was in contact with the ADS server but at the point when ... DA should have been passing back a ramdisk in which to boot, ... target system simply rebooted. ... still alive and germaine to ADS even today. ...
    (microsoft.public.windows.server.setup)