Re: Another 800704CF Error
- From: Dwayne Mccoy <DwayneMccoy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 27 Apr 2006 05:40:02 -0700
Scott, i sent the files you requested.
"aahq" wrote:
Hi Dwayne. I have taken the pieces I think should go out and injected it.
successfully but it is still making no difference. Could you send me the
inf, cat and sys file you are using to aahq @ the hotmail place. I just do
not understand what is wrong with this (whether it is the version I am using
or what)...
Regards
Scott
"Dwayne Mccoy" wrote:
It seems the problem is whit the Win 2k drivers section of the driver inf
file. The solution that worked for me is to delete all of the Win 2k
information from the broadcom inf file. After doing this everything works
fine. Thanks again to everyones assistance.
"aahq" wrote:
Hi Dwayne and others...
I have a Dell 520 (Broadcom NIC) as well and I have exactly the same issue.
My CD Version works great.
My PXE Boot Version doesn't work.
My added twist with this is that I have a 520 RAMDisk ISO that works but it
is the very manual ask all the questions (welcome screens, computername etc)
version.
Now, I found that by adding the RIPINFO.INI from my working CD to the
working RAMDISK version then it breaks... NO IP Connectivity...
Here are my two RIPINFO's.
Working Network PXE RIPINFO (very manual, asks questions):
[RIPInfo]
Images=1
LocalImage=Yes
WizTitle=SMS OSD Install CD
AllowMachineName=Yes
SiteCode=POC
ManagementPoint=test-VSMSP:80
Reserved1=gibberish
Reserved2=gibberish
Reserved3=gibberish
[ImageInfo1]
DisplayName=Windows XP Service Pack 2 - Windows XP POC LAB
PackageID=POC00001
ProgramName=Windows XP POC LAB
Working CD Based RIPINFO (asks no questions):
[RIPInfo]
Images=1
LocalImage=Yes
WizTitle=OSD 520 Install CD
AllowMachineName=No
SiteCode=TST
ManagementPoint=TEST:80
Reserved1=gibberish
Reserved2=gibberish
Reserved3=gibberish
[UserCommand]
CommandLine=""\\server\temp\csvparse.vbs" "
NetworkShare=\\server\temp
Reserved1=gibberish
Reserved2=gibberish
Reserved3=gibberish
[ImageInfo1]
DisplayName=Workstation V1.4 - Workstation V1.4 Install
PackageID=TST00007
ProgramName=Workstation V1.4 Install
Any assistance or explanation to the behaviour is appreciated...
Regards
Scott
"Dwayne Mccoy" wrote:
Yes, i am doing this with the inbox winpe.... I have added the drivers to
the winpe drivers tab. I will try removing the win2k reference in the inf
file.. Thanks for the help!
"Rob Molenaar" wrote:
Are you using the inbox winpe? You have to add the nic drivers to winpe as
well not only to the image
There is a driver tab to do it. You can also create your own winpe and
upload it to SMS, if you use BDD 2.5 you can run into problems as well
because the 520 broadcom inf has a refrence to a w2k driver so the
injectipon utility fails :-( so much pain, remove both refrences or add the
w2k driver as well
"Dwayne Mccoy" <DwayneMccoy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:410B4581-5338-41E1-AA57-732E3ABB3E42@xxxxxxxxxxxxxxxx
Yes, everything works fine when using the disk. The problem only exist
when
pushing the package through SMS. Everything is fine up to the point where
the workstation reboots and starts the install.. This is very strange...
I
have rebuilt the entire image several times. I have loaded the drivers
(NIC)
from 4 or 5 different locations and each attempt ends with the same
results!!
RIS is working perfectly fine and I am using the same exact drivers.
Anyway, i really appreciate your help!
"Bob Mac Neill (MSFT)" wrote:
Hi Dwayne,
I can only suggest verifying the drivers are in the .iso you create the
CD
with - a tool like WinRAR can open and view the .iso - if you boot using
RIS
without error then the actual drivers themselves aren't an issue.
Can you boot the same machine you are testing the CD with via RIS
successfully?
Regards,
Bob Mac Neill
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Dwayne Mccoy" <DwayneMccoy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ADDD0016-FF9E-4BF6-9340-6BDFEEE4F39B@xxxxxxxxxxxxxxxx
Good morning Bob. Yes, i am using the .lab version. When going to the
command line i am unable to run any "ip" commands. In other words, if
i
run
ipconfig i get no configuration information. I can not ping IP address
or
dns names. This tells me that the NIC drivers are not loading which is
why i
am so confused. All of the drivers are in the package. We also have a
RIS
server and that is functioning fine. I have the same drivers loaded
for
RIS
and that works fine. Thanks again for the help. Let me know if you or
anyone else has any other suggestions!
"Bob Mac Neill (MSFT)" wrote:
Hi Dwayne,
Have you tried using the OSDShell.lab to replace OSDShell.exe to open
a
command window when WinPE boots? This will allow you to check if you
can
reach the network location.
The User's Guide has a section ""Using the Lab Shell for Windows PE"
which
details the steps to use this.
If you cannot reach the network location I would guess it's a name
resolution problem.
Regards,
Bob Mac Neill
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Dwayne Mccoy" <DwayneMccoy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:DDF55421-5985-494B-BE41-49A7CF661A9E@xxxxxxxxxxxxxxxx
I failed to put the entire error message. Sorry about that.
SMS Operating System Deployment
The operating system installation failed. Please contact your
system
administrator for assistance.
Could not connect to the installation package on
\\"servername"\smspkge$\fkm0000D. The network location cannot be
reached.
For information about network troubleshooting, see Windows help.
(800704CF)
This message will automatically close in 30 Minutes.
"Dwayne Mccoy" wrote:
Good afternoon everyone. I have been researching this issue for 4
days
now
and I can not find the solution. It is the same problem that many
of
you
have experienced but i can not solve it. I have created a image
for a
Dell
GX520. I have checked and double checked to make sure the drivers
are
all in
the package and they are! I have built the OS Image Install cd and
it
works
perfectly fine! The same driver files are copied to the CD that
are
copied
to the package files for the push install!!
Any suggestions woudl be greatly appreciated!!!!
- References:
- Re: Another 800704CF Error
- From: aahq
- Re: Another 800704CF Error
- From: Dwayne Mccoy
- Re: Another 800704CF Error
- From: aahq
- Re: Another 800704CF Error
- Prev by Date: Re: Sysprep / Drivers Update Postinstall Phase in ZTI
- Next by Date: Re: Last Logged On User
- Previous by thread: Re: Another 800704CF Error
- Next by thread: Run Program from Remote Distribution point
- Index(es):
Relevant Pages
|
