Re: ADS default job templates. Trouble booting into the deployment ag
From: jeff simon (jefsimon_at_microsoft.com)
Date: 03/21/05
- Next message: anonquestion: "mac osx/windows 2K server"
- Previous message: jeff simon: "Re: ADS default job templates. Trouble booting into the deployment ag"
- In reply to: jeff simon: "Re: ADS default job templates. Trouble booting into the deployment ag"
- Next in thread: Tim Net: "Re: ADS default job templates. Trouble booting into the deployment ag"
- Reply: Tim Net: "Re: ADS default job templates. Trouble booting into the deployment ag"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 21 Mar 2005 11:27:56 -0800
A few corrections:
1. the device bios date and time is used to validate a cert. It must be in
sync (roughly).
2. Configure BIOS to PXE boot 1st and then HD boot.
"jeff simon" <jefsimon@microsoft.com> wrote in message
news:423f18d0$1@news.microsoft.com...
> Booting to the DA is something you can do without first syspreping the
> box - as an experiment. here are some ideas you've got the basic ground
> covered:
>
> 1. The device (remote server) bios date is approximately correct.
> 2. The device bios is configured bios then HD
> 3. The controller, is set at auto-add unknown PXE clients. This will
> auto-create a device object when the box PXE boots the first time. It rids
> input error of those MAC addresses. Also, set the job template for
> auto-add to boot-to-da.
> 4. Boot the device (PXE) - it should hang the first time.
> 5. On the controller, identify the new device object - it is uncontrolled
> and disconnected
> 6. Take control of the particular device object AND confirm default job
> template is "Boot-to-da"
> 7. PXE boot the box again.
> 8. this time, the device should boot to the DA.
> 9. then retry the sample sequence.
>
> Notes:
>
> Numerous difficulties can occur. Most common:
>
> 1. missing NIC and storage drivers - if they aren't supplied in windows,
> they you need to find them from your OEM See docs.
> 2. the services didn't start up. run ADSSERVICE /L - all three need to be
> connected.
> 3. Do the first deployment on a simple hub; DHCP on complex networks
> requires more work.
>
>
>
>
>
> "JWG" <JWG@discussions.microsoft.com> wrote in message
> news:6DBA1B11-EC62-49D4-B9F2-02EBB224A838@microsoft.com...
>> Hey folks.
>>
>> I installed ADS and patched it up to date, and I just have a little demo
>> setup where 2 servers are plugged into the same switch in a lab
>> environment.
>> I just want to grab an image of my Win2k3 std OS, and i'm using the
>> Capture
>> Image.xml default job. It runs sysprep-->boot to deployment
>> agent-->capture
>> image
>>
>> Basically i run sysprep just fine and I put my .inf file in the directory
>> so
>> i get back to windows, but that's where this job stops. I never get into
>> the
>> deployment agent at all, and all the documentation that's out there says
>> this
>> should work no problem. I put my controller and NIC drivers on the ADS
>> controller so they are up to date, but i can't think of anything else.
>>
>> Can anyone else running ADS give me a few ideas? Nothing I do will let
>> me
>> create an image so far.
>> Thanks in advance
>
>
- Next message: anonquestion: "mac osx/windows 2K server"
- Previous message: jeff simon: "Re: ADS default job templates. Trouble booting into the deployment ag"
- In reply to: jeff simon: "Re: ADS default job templates. Trouble booting into the deployment ag"
- Next in thread: Tim Net: "Re: ADS default job templates. Trouble booting into the deployment ag"
- Reply: Tim Net: "Re: ADS default job templates. Trouble booting into the deployment ag"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|