Sysprep help Please

Hi all,

Run into bit of a problem with a batch of machines. I'm pretty certain it's the network driver thats at fault as it's an unsigned one and when I log on it asks to install the drivers for it.

I've got my sysprep.inf file to pickup the machine name from active directory and the domain as well. his works well on a realtek based nic. However the other machines have intel ones in, and i've got the unsigned driver. I can't seem to find a signed driver on intels site. Network card in Pro/100 VE. It's built into an Intel motherboard.

Does anyone have any ideas on how to get round this?

Cheers

wots the versoin of the motherboard

Are you using the line

Quote:

---

DriverSigningPolicy=Ignore

---

in your Sysprep.inf? It goes in the [Unattended] section and should allow the driver to install during the mini-setup.
Hope this helps

LukeC - motherboard is a Intel D946GZIS. And i'm using the latest drivers from intels site.

IanB - I have that line in there. I'll have to post my details of it here and see if anyone can notice any problems with it.

Well here's my sysprep.inf file. This works absolutely fine on a realtek 8139 nic but not the intel ones.

Quote:

---

;SetupMgrTag
[Unattended]
OemSkipEula=Yes
DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes
OEMPNPDriversPath=\Drivers\NIC

[UserData]
ProductID=
FullName = "Walton-le-Dale Arts College & High School"
OrgName = "Preston"
ComputerName = %MACHINENAME%

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000809
UserLocale=00000809
InputLocale=0809:00000809

[GuiUnattended]
AdminPassword="******"
EncryptedAdminPassword=NO
OemSkipWelcome = 1
OemSkipRegional = 1
TimeZone = %TIMEZONE%

[Display]
BitsPerPel = 32
XResolution = 1024
YResolution = 768
VRefresh = 60

[Networking]

[NetServices]
MS_Server=params.MS_PSched

[Identification]
JoinDomain = %MACHINEDOMAIN%
DoOldStyleDomainJoin = Yes

---

Does anyone have any more ideas about what could be wrong?

On an unrelated note, I suggest you amend your post above to obscure the admin password...

And remove your product ID...

Got bit of a update now. I've got it to install the NIC correctly but it doesn't pick up the %MACHINENAME% from AD. I think it's something to do with the NIC install order. It now also joins the domain properly.

Next question is being able to make it pick it's name up from AD. Has anyone managed to get sysprep.inf to do this? And if so how?

Cheers,

You create a computer account and assign that account the machines GUID.

Never got sysprep to pick up the name from AD, wish I could! I'm not sure it's actually designed to do that, but I'm not a sysprep expert so I may be wrong.

What we do here is leave the machine name blank in the answer file, so it prompts you for it at re-start. Then it automatically adds itself to the domain and completes the rest of the setup process. This is the closest I've ever got to a fully automated install using sysprep.

Mike.

Well i've got it to work by putting a 8139 NIC in the machine in question and it works fine.

Is it possible to add drivers to deploy.cab?


Cheers

It is possible to add 3rd party drivers to images but blowed if I can get it to work. Currently talking to Microsoft about this because it won't work for me :(

I do believe that this line -

OEMPNPDriversPath=\Drivers\NIC

should point to each and every folder that has an .inf file...

It should be more like -

OEMPNPDriversPath=\Drivers\NIC1;\Drivers\NIC2;\Dri vers\NIC3

That's the way that I have always done it, and it seems to work fine with the 10 or more different NICs that we have.

Alan

Quote:

---

It should be more like -

OEMPNPDriversPath=\Drivers\NIC1;\Drivers\NIC2;\Dri vers\NIC3

---

Thats the correct way to do it.

OEMPNPDriversPath=\Drivers\NIC would mean you had all your nic driver(s) in that folder with no sub folders.

I've only got the one extra NIC driver. It's an intel Pro 100/VE. We've got this chipset in about 200 machines. The rest are Realtek 8139 which are built into XP.

I've got in installing the drivers but it won't pick the machine name out of AD. I think it looks for that before it runs mini-setup. Does anyone know of a way round this?