Re: OSD - Cannot find path specified 80070003
- From: "Bob Mac Neill \(MSFT\)" <bobmn@xxxxxxxxxxxxx>
- Date: Wed, 30 Mar 2005 11:17:10 -0800
Hi Stuart,
Glad you got everything sorted - hidden partitions can be a pain as they're
not immediately apparent. The OS Program can contain spaces, that should not
be an issue.
Regards,
Bob
"Stuart Green" <StuartGreen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A8B0844A-EC7E-4E66-BCAC-E7E059CC8763@xxxxxxxxxxxxxxxx
> Hi Bob,
>
> Found the problem.
>
> First of all, the program name had spaces in it and WinPE was using a UNC
> path to address it which was causing the failure.
>
> Next, the MININT directory had information from old installations in it so
> this was then forcing WinPE to look at an old package source.
>
> Finally, the resulting image was causing a STOP 7B (Inaccessible Boot
> Device) error when it booted for the first time. This was cured by
> removing
> the system partitions that Dell puts on its machines when it ships them.
>
> Aside from a couple of tweaks to the image now, all seems to be well.
>
> Thanks for your help though.
>
> Regards,
>
> Stuart
>
> "Bob Mac Neill (MSFT)" wrote:
>
>> Hi Stuart,
>>
>> When the Advertisement runs there should be a \minint folder created on
>> the
>> machine with a minimum of OSDAgent.log and OSDLaunch.log - these will
>> record
>> if the OSDAgent loaded and subsequent operations like connecting to the
>> DP
>> for the OS Package and loading the User Notification files.
>>
>> If you don't get any of this I would look at the software distribution
>> logs
>> e.g. execmgr.log - one test I always perform is can a regular software
>> distribution package run. If it can then OSD is able to get as far as the
>> logging steps I listed above.
>>
>> Regarding the APIPA addressing, I don't know but if it turns out to be a
>> probably issue I'll look into it.
>>
>> Thanks and regards,
>>
>> Bob Mac Neill | SMS OSD FP
>>
>> This posting is provided AS IS with no warranties and confers no rights
>>
>>
>> "Stuart Green" <StuartGreen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:D6C2404B-44B7-472A-A096-3A5D1F5CD328@xxxxxxxxxxxxxxxx
>> > Hello Bob,
>> >
>> > Was planning on trying the .lab option in the morning as I saw it in
>> > another
>> > post.
>> >
>> > So far as I can see, nothing is actually being written to the hard disk
>> > on
>> > the client machine.
>> >
>> > I have taken all of the boundaries from the DHCP server so if a duff
>> > address
>> > is being issued, I'd like to know how, and if an address isn't being
>> > issued,
>> > I'd like to know why. Will WinPE default to APIPA addressing if it
>> > can't
>> > pick an address up?
>> >
>> > Unfortunately, we are not allowed to send log files from this system,
>> > so
>> > if
>> > you can shed any light on to what you would be looking for, it would be
>> > very
>> > much appreciated.
>> >
>> > Thanks,
>> >
>> > Stuart
>> >
>> > "Bob Mac Neill (MSFT)" wrote:
>> >
>> >> Hi Stuart,
>> >>
>> >> Using a CD with the OSDShell.lab replacing the OSDShell.exe can you
>> >> verify
>> >> that the package/distribution point can be reached. Also if you use
>> >> site
>> >> boundaries you may want to verify the client exists in those
>> >> boundaries.
>> >>
>> >> For the user installation can you send OSDAgent.log and
>> >> OSDLaunch.log -
>> >> they
>> >> can be found in c:\minint\smsosd\
>> >>
>> >> Regards,
>> >> Bob Mac Neill | SMS OSD FP
>> >>
>> >> This posting is provided AS IS with no warranties and confers no
>> >> rights
>> >>
>> >> "Stuart Green" <StuartGreen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> message
>> >> news:6A271209-E761-4B87-B37B-EFE8D896907D@xxxxxxxxxxxxxxxx
>> >> > Hi,
>> >> >
>> >> > We seem to have developed a problem deploying operating systems.
>> >> > Using
>> >> > either CD or user installation, the error message generated by the
>> >> > wizard
>> >> > prevents the installation from progressing.
>> >> >
>> >> > This happens on either a NT4 Workstation or Clean build machine.
>> >> >
>> >> > Any ideas anyone?
>> >>
>> >>
>> >>
>>
>>
>>
.
- References:
- Re: OSD - Cannot find path specified 80070003
- From: Stuart Green
- Re: OSD - Cannot find path specified 80070003
- Prev by Date: Re: How to manage workgroup PC?
- Next by Date: Re: Remote control tools on XP / 2003 clients
- Previous by thread: Re: OSD - Cannot find path specified 80070003
- Next by thread: Re: How to manage workgroup PC?
- Index(es):
Relevant Pages
|