Jump to content

TPB_Cyrus

Member
  • Posts

    1
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

About TPB_Cyrus

TPB_Cyrus's Achievements

0

Reputation

  1. Hello All, I am currently running into some problems while building an image for a new piece of hardware. I am required by my employer to create an updated image on Win2K. I am using Sysprep 1.1. Here is the scenario: I have downloaded all the latest drivers for my hardware, unpacked them and put on the files needed into a sysprep folder structure broken down for each hardware model. I have added the neccessary lines to the OEMDriversPath. I might also add that I am building the generic image from a base image that was built on another model in the environment. When I run sysprep -pnp -reboot -quiet, all the OEM drivers are copied down , then machine reboots and then I ghost it. When I run my new created ghost image on the new hardware to test, everything runs properly, i do not get any errors. The only problem is that when the machine does not join the domain during mini setup. Once mini setup has completed and the machine reboots, i log in with the administrators account and check the device manager, it is not showing me any yellow question marks. I read on the Microsoft website that sometimes drivers will install after the reboot and you sign in with an admin account if they are not signed. I have verified that all of my drivers are signed. Not ending there....during mini-setup i do SHIFT+F10 to get a cmd prompt and I do a ipconfig do see if the machine gets an IP. No dice. When I omit the chipset dirvers from the sysprep at the beginning the machine joins the domain no problem. Thus I can narrow it down to the installation of the chipset drivers. It sounds like they are not installing properly or are looking for a reboot at some point. After doing some reading, I thought doing sysprep -bmsd might help me build my sysprep.inf. Though I am not sure on how to use this switch. Will it copy all of my OEM drivers down and build from there as well as the ones in the winnt\system32\drivers? Could SATA be the culprit? a bit more info 1. the hardware is all from the same vendor Can anybody tell me what I am doing wrong???? TPB_Cyrus
×
×
  • Create New...