RE: OS Deployment Issue

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

From: William B (WilliamB_at_discussions.microsoft.com)
Date: 10/29/04

  • Next message: Scott Sekinger: "RE: Can not Run Reports In SMS 2003"
    Date: Fri, 29 Oct 2004 11:58:03 -0700
    
    

    Well I found out that I was trying to select a root directory that contained
    subdirectories of different model NIC drivers versus specifying a directory
    that contained specific NIC driver files. Once I set the add NIC drivers to
    the directory that contained files for the NIC on the machine I was using
    everything started working and the drvier files were indeed copied to the
    package distribution.

    However, I am tryin to run a custom VBS script that runs great when in
    Windows XP but fails on "invalid syntax" when run under Windows PE. I
    believe it was failing on WMI portions of the script. Any suggestions there?

    "William B" wrote:

    > I am running OSD FP Release Candidate:
    >
    > I have create a capture CD and successfully captured an image file which I
    > have turned into a package. When i distribute the image to my test
    > workstation, the workstation receives the package and begins the process.
    > When the PC reboots into WinPE the network never intializes thus displaying
    > an error that it the network path to my SMSServer\SMSPKGC$\00000008 could
    > notn be located. The PC i am distibuting to is also the PC I used to the
    > Capture CD on which was able to connect and upload the image.
    >
    > I have used the lab shell to pull up a cmd prompt during the WinPE
    > initialization and have verified that the NIC was not intialized and no IP
    > has been assigned.
    >
    > Also, in the package properties I have specified additional network drivers
    > but this doesn't seem to add this driver files to the source directory of the
    > OS package...Is this normal? Seems like the drivers would be copied down
    > during the intial package installation stage so that they are avalable for
    > the network boot that is required to connect and pull the OS package down
    > through WinPE.
    >
    > Anyone have any suggestions?


  • Next message: Scott Sekinger: "RE: Can not Run Reports In SMS 2003"

    Relevant Pages

    • Re: The Network Location could not be found Error (800704CF)
      ... that we use to build all of our computers with, Ran Update WinPE, then Update ... OSD Package files, Update Distribution Points. ... The only way i can get this to work is to add the NIC drivers to the OSD ...
      (microsoft.public.sms.tools)
    • 3C905B NIC again
      ... I've installed the 3c905b NIC drivers from: ... I broke down the package and ... until I reboot then I get the looping crash. ...
      (SunManagers)
    • Re: winxppro upgrade network problem
      ... The upgrade may have resulted in a set of NIC drivers that are ... >Drive)All seemed to go ok but i am unable to access my network and router. ... >network winxp pro will only use the 1394 connection and NOT the NIC. ... >Needless to say I am using the working xp home partition to compose this. ...
      (microsoft.public.windowsxp.general)
    • explorer.exe right click error
      ... This problem was solved by re-installing the NIC drivers, ... >wireless router, desktop NIC, wireless NIC. ... The network ... >communicate from the notebook to the desktop. ...
      (microsoft.public.win2000.networking)
    • Re: Strange IP Address Behavior
      ... NIC drivers off of production hours and see what happens. ... network with the same address as this server. ... Our web developers use different internal IP addresses in their ... It seems all of a sudden, the NIC card started with the bouncing ...
      (microsoft.public.windows.server.general)