Re: The Network Location could not be found Error (800704CF)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello,
I finally got this to work. I recreated the Package and updated everything
and it worked. the Nic Drivers now load in WinPe. Now i'm getting the same
error after the image is loaded an it goes to boot to the OS to run the final
phases. I only using the CS.ini and ZTI.vbs to do ZTI installations and
this is what i have in my CS.ini

[Settings]
Priority= Default, DefaultGateway, MACADDRESS
CustomKeysUserData=UDShare, UDDir, UDProfiles, SLShare, OSInstall,
Packages(*), Administrators(*), DriverPath
CustomKeysSysprep=ComputerName,TimeZone,JoinDomain,MachineObjectOU
OSDVariableKeys=OSDINSTALLSILENT,OSDINSTALLPACKAGE,OSDINSTALLPROGRAM,OSDNEWMACHINENAME
ScanStateArgs=/i:miguser.inf /i:migapp.inf /i:migsys.inf /i:sysfiles.inf
/i:updateuser.inf /v:7 /x /s /f /o /c
LoadStateArgs=/v:7 /c
UserExit=ZTIUserExit.vbs

[Default]
UDShare=\\SMSServer\MigData
SLShare=\\SMSServer\OSDLogs
UDProfiles=*\*
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=SMS000A0
OSDINSTALLPROGRAM=ZTI Refresh
TimeZone=035
JoinDomain=OurDomain.com
MachineObjectOU=LDAP://OU=Workstations,OU=OurOU,DC=ad,DC=Domain,DC=com
ComputerName=%OSDNEWMACHINENAME%
UDDir=%OSDCOMPUTERNAME%
OSInstall=Y
DriverPath1=\\SMSserver\Drivers










--
-Maro


"Johan Arwidmark" wrote:

Does the osdwinpe.wim file on the DP (package folder) has the exact
same size and date as the one in \sms\osd?

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment


On Mon, 18 Sep 2006 09:29:01 -0700, Maro <bmarobel@xxxxxxxxxxxxx>
wrote:

Created a custom WinPE folder on the SMS server with the WinPE environment
that we use to build all of our computers with, Ran Update WinPE, then Update
OSD Package files, Update Distribution Points.

I send the OSD Advertisement to the SMS Client and it runs the first three
phases, reboots to PE and fails because the network drivers are not in the
MININT folder. I have to boot to the Installation CD for the installation to
complete.

The only way i can get this to work is to add the NIC drivers to the OSD
Package Properties.




.

Relevant Pages

  • Re: SMS 2K3 OSD Error
    ... WinPE doesn't have the correct DNS Suffix. ... You can also add a hosts file to WinPE containing the FQDN ... The Package ID or Program name or MP is incorrect in ripinfo.ini ... >I am having another issue with the Operating System Deployment feature of ...
    (microsoft.public.sms.tools)
  • Re: SMS 2K3 OSD Error
    ... client, it indeed appears that it cannot resolve the address of the MP. ... > WinPE doesn't have the correct DNS Suffix. ... > The Package ID or Program name or MP is incorrect in ripinfo.ini ... >>I am having another issue with the Operating System Deployment feature of ...
    (microsoft.public.sms.tools)
  • Re: The Network Location could not be found Error (800704CF)
    ... what phase does it fail in now? ... Windows XP (not winpe) and the machine will not join the domain during ... the Nic Drivers now load in WinPe. ...
    (microsoft.public.sms.tools)
  • RE: OS Deployment Issue
    ... subdirectories of different model NIC drivers versus specifying a directory ... Once I set the add NIC drivers to ... > have turned into a package. ... > When the PC reboots into WinPE the network never intializes thus displaying ...
    (microsoft.public.sms.misc)
  • SMS 2003 OSD
    ... When i deploy the package for the OS it does the pre install steps fine ... the SMS package version of WinPE? ... specify credentials it works fine. ...
    (microsoft.public.sms.tools)