Re: Image pushing failing after minint folder has been installed.

Initially I did have that problem but once I pointed the package to the
correct nic driver everything was fine as far as the sms package was
concerned. It connected fine and the minint folder was installed and all
that. The problem occurs once the preinstallation phase starts. It looks
like windows PE doesn't have the correct driver. I've added the appropriate
nic driver to the following folders in the Customwinpe folder in my sms
package:

Customwinpe\inf
Customwinpe\system32
Customwinpe\system32\drivers

I don't know, I'm at a loss. I'm wondering at this point if it has some
problem with the credentials provided to connect back and not a problem with
the nic not being initialized. I guess the two big questions I have at this
point are:

Once Windows PE starts from the workstation where is it pulling the nic
drivers from?
My understanding is that I needed to provide the inf file in
Customwinpe\inf and the sys and the rest in Customwinpe/system32.

Where is Windows PE getting its network credentials from?

I'd appreciate any more ideas you may have to help shed some light on this.

Thanks.


"Jason Terpsma [MSFT]" wrote:

> Hey tyler -
>
> This looks like Windows PE does not have the correct network drivers to
> connect to your SMS Server. It sounds like you are running OSD from an SMS
> package so you will need to add the correct drivers to your package. The
> section in the users guide entitled Configuring The OS Deployment package
> Properties on pages 27 - 29 has information on how to add drivers to WinPE.
>
> Hope That Helps,
> Jason Terpsma
>
> "tyler" <tyler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:CF6EE0ED-CCC4-4195-BA38-C88318FAD208@xxxxxxxxxxxxxxxx
> >I made it this far without needing help but I'm stuck pretty good and
> >haven't
> > been able to find a similar problem anywhere here.
> > Here's the deal:
> > I'm making it as far as getting the minint folder installed before it
> > fails.
> > Here is my OSDAgent.log file, Iv'e inlcluded where it fails as well as a
> > bit
> > before the failure:
> >
> > <![LOG[Stopping OS Deployment Agent Service]LOG]!><time="10:57:15.004+000"
> > date="06-21-2005" component="OSDAgent" context="" type="1" thread="1440"
> > file="osdagent.cpp:361">
> > <![LOG[ ]LOG]!><time="10:58:52.156+000" date="06-21-2005"
> > component="OSDAgent" context="" type="1" thread="960"
> > file="osdagent.cpp:689">
> > <![LOG[*****************************************************************]LOG]!><time="10:58:52.171+000"
> > date="06-21-2005" component="OSDAgent" context="" type="1" thread="960"
> > file="osdagent.cpp:690">
> > <![LOG[Successfully intialized Logging.]LOG]!><time="10:58:52.171+000"
> > date="06-21-2005" component="OSDAgent" context="" type="1" thread="960"
> > file="osdagent.cpp:691">
> > <![LOG[OSDAgent was launched from Windows
> > PE.]LOG]!><time="10:58:52.171+000"
> > date="06-21-2005" component="OSDAgent" context="" type="1" thread="960"
> > file="osdagent.cpp:119">
> > <![LOG[Shared environment successfully
> > initialized]LOG]!><time="10:58:52.203+000" date="06-21-2005"
> > component="OSDAgent" context="" type="1" thread="960"
> > file="osdenvlib.cpp:208">
> > <![LOG[Failed to connect to \\SMHMC-SMS1\SMSPKGR$\00700060 (1231). Retry
> > in
> > 10 seconds.]LOG]!><time="10:58:52.546+000" date="06-21-2005"
> > component="OSDAgent" context="" type="2" thread="960"
> > file="connection.cpp:352">
> > <![LOG[Failed to connect to \\SMHMC-SMS1\SMSPKGR$\00700060 (1231). Retry
> > in
> > 20 seconds.]LOG]!><time="10:59:02.546+000" date="06-21-2005"
> > component="OSDAgent" context="" type="2" thread="960"
> > file="connection.cpp:352">
> > <![LOG[Failed to connect to \\SMHMC-SMS1\SMSPKGR$\00700060 (1231). Retry
> > in
> > 30 seconds.]LOG]!><time="10:59:22.546+000" date="06-21-2005"
> > component="OSDAgent" context="" type="2" thread="960"
> > file="connection.cpp:352">
> > <![LOG[Failed to connect to \\SMHMC-SMS1\SMSPKGR$\00700060 (1231). Retry
> > in
> > 40 seconds.]LOG]!><time="10:59:52.546+000" date="06-21-2005"
> > component="OSDAgent" context="" type="2" thread="960"
> > file="connection.cpp:352">
> > <![LOG[Failed to connect to \\SMHMC-SMS1\SMSPKGR$\00700060
> > (1231)]LOG]!><time="11:00:32.546+000" date="06-21-2005"
> > component="OSDAgent"
> > context="" type="3" thread="960" file="connection.cpp:325">
> > <![LOG[Stat Msg: 3221236577
> > MachineName=IMAGE-XPSP1-SMS
> > ClientID=GUID:6B21DC39-3228-418D-B72C-E2D1E496DCF2
> > ProcessID=#956
> > ThreadID=#960
> > Win32ErrorCode=#0
> > DateTime=20050621160032.562000+000
> > Attrib400=00700060
> > Attrib401=00720106
> > Insert1=\\SMHMC-SMS1\SMSPKGR$\00700060
> > ]LOG]!><time="11:00:32.562+000" date="06-21-2005" component="OSDAgent"
> > context="" type="1" thread="960" file="mpstatus.cpp:454">
> > <![LOG[Connecting to server SMHMC-SMS1 on port
> > 80]LOG]!><time="11:00:32.578+000" date="06-21-2005" component="OSDAgent"
> > context="" type="1" thread="960" file="mpstatus.cpp:151">
> > <![LOG[Failed to resolve address to server SMHMC-SMS1
> > (11004)]LOG]!><time="11:00:32.578+000" date="06-21-2005"
> > component="OSDAgent"
> > context="" type="3" thread="960" file="mpstatus.cpp:171">
> > <![LOG[Failed to send status message C0002B61
> > (80072AFC)]LOG]!><time="11:00:32.578+000" date="06-21-2005"
> > component="OSDAgent" context="" type="2" thread="960"
> > file="status.cpp:67">
> > <![LOG[Failed to unregister OSD environment object
> > (800704CF)]LOG]!><time="11:00:32.578+000" date="06-21-2005"
> > component="OSDAgent" context="" type="3" thread="960"
> > file="osdenvlib.cpp:609">
> > <![LOG[The operating system installation failed. Please contact your
> > system
> > administrator for assistance.
> >
> > There does not appear to be any other failures in the other logs.
> > Obviously
> > its not connecting to our SMS server but I'm at a complete loss as to why
> > it
> > no longer is able to do so once it reaches this point in the process. Any
> > suggestions would be very appreciated.
> >
> > Thanks.
> >
> >
>
>
>
.

Relevant Pages

  • Re: Distribution Point directory structure question
    ... > When you create a package, SMS lets you choose on a package-by-package basis ... > if you want to get source files at all, and if so, where to get them from. ... > share anywhere on the network and point SMS there. ... > SMS will create a compressed version of the source files on the site server. ...
    (microsoft.public.sms.admin)
  • RE: OSD Image Deployment via SMS advertisement (cannot connect to shar
    ... OS Deployment advertisement failed to install OS Deployment agent!. ... CD I created from the SMS Admin Console. ... The new package is created. ... Raising event: ...
    (microsoft.public.sms.swdist)
  • Re: Distribution Point directory structure question
    ... When you create a package, SMS lets you choose on a package-by-package basis ... if you want to get source files at all, and if so, where to get them from. ... SMS will create a compressed version of the source files on the site server. ...
    (microsoft.public.sms.admin)
  • Re: In search of a better line driver
    ... >the package to drive several others in parallel, ... >gates are used, lot variations in the output impedances of the gates can ... The thing is so small I can hardly solder it. ... I have a little general purpose line driver board I made using ...
    (sci.electronics.design)
  • Re: Distributing Office 2003
    ... and print server or any other member server. ... defined in the SMS Site as an assigned DP. ... transmitted, not the entire package. ... MST file after I ...
    (microsoft.public.sms.swdist)