Ste_Harve Posted July 10, 2007 Posted July 10, 2007 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
IanB Posted July 10, 2007 Posted July 10, 2007 Are you using the line 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
Ste_Harve Posted July 10, 2007 Author Posted July 10, 2007 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.
Ste_Harve Posted July 11, 2007 Author Posted July 11, 2007 Well here's my sysprep.inf file. This works absolutely fine on a realtek 8139 nic but not the intel ones. ;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[/Quote] Does anyone have any more ideas about what could be wrong?
Ravening_Wolf Posted July 11, 2007 Posted July 11, 2007 On an unrelated note, I suggest you amend your post above to obscure the admin password...
Ste_Harve Posted July 12, 2007 Author Posted July 12, 2007 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,
Geoff Posted July 12, 2007 Posted July 12, 2007 You create a computer account and assign that account the machines GUID.
maniac Posted July 17, 2007 Posted July 17, 2007 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.
Ste_Harve Posted July 18, 2007 Author Posted July 18, 2007 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
Ravening_Wolf Posted July 18, 2007 Posted July 18, 2007 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
gnarlyc Posted July 18, 2007 Posted July 18, 2007 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;\Drivers\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
PeterW Posted July 19, 2007 Posted July 19, 2007 It should be more like - OEMPNPDriversPath=\Drivers\NIC1;\Drivers\NIC2;\Drivers\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.
Ste_Harve Posted July 19, 2007 Author Posted July 19, 2007 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?
tarquel Posted July 31, 2008 Posted July 31, 2008 I didnt realise sysprep could take the computer name from AD. Thought it was only using RIS where it does that. Guess I've learnt something new there, but no, the only way around it i guess is to manually enter it. Thats what i did when i used to sysprep computers before RIS.
jsnetman Posted July 31, 2008 Posted July 31, 2008 I've got in installing the drivers but it won't pick the machine name out of AD You can get sysprep to automatically assign a random name beginning with say "myschool" which would give you computer name like "myschool1,2,3 and so on. But you cant get sysprep to pull the name from AD.
tarquel Posted July 31, 2008 Posted July 31, 2008 Sorry. I wasn't clear in my post. I meant to put: "I knew you could generate the computer name automatically to use, but didnt realise sysprep could take the computer name from AD" Been doing it various with UA installs for many a year.... which is why i didnt think that you could automatically retrieve the computername from AD [except by using RIS / another 3rd party deployment method].
Ste_Harve Posted July 31, 2008 Author Posted July 31, 2008 Well to drag this back up, I couldn't get the machines with the Pro100/VE entwork connection to pick the name out of AD but if I use another supported network card it does. I've now got all my machines staged in AD and the sysprep.inf file pulls the computername down from AD. I think it does this when you use the RIS or WDS part to setup. I can't tell you how it works but it does and it's saved me a lot of time. No more moving computer accounts between OU's, no more renaming, unless I change the motherboard!! If anyone wants any more info on this just PM me and I'll see if I can guide you in the right direction
jsnetman Posted July 31, 2008 Posted July 31, 2008 So let me get this clear, on a normal rebuild you just set it away and you do not use any sort of input like machine name in the mini setup.
Ste_Harve Posted July 31, 2008 Author Posted July 31, 2008 So let me get this clear, on a normal rebuild you just set it away and you do not use any sort of input like machine name in the mini setup. Thats right, my sysprep.inf file has the reference %AMCHINENAME% for the machine name and %MACHINEDOMAIN% for the domain to join. All I do is boot machine via PXE to WDS, set it to pull the image down, and after 10 mins it's sat at the logon box waiting to be used. If you want a copy of my sysprep.inf file i'll happily post it up here.
jsnetman Posted July 31, 2008 Posted July 31, 2008 Ok yes it's pre-staging, are these machines with intel cards new to your network.
Michael Posted July 31, 2008 Posted July 31, 2008 Thats right, my sysprep.inf file has the reference %AMCHINENAME% for the machine name and %MACHINEDOMAIN% for the domain to join. All I do is boot machine via PXE to WDS, set it to pull the image down, and after 10 mins it's sat at the logon box waiting to be used. I was under the impression you can either get Sysprep to randomly create a computer name based on domain name, specify a list of computer names it can use or you manually specify a computer name during Mini Setup. I always specify the computer name manually, because it's impossible to get Sysprep to use computer names alphanumerically. As for pulling the computer names down, I'm not so sure about that. I can only presume you've specified a list of computer names for Sysprep to use and have already created new computer objects in AD, with the correct OU. I can't see how the computer name would be pulled down from AD. The Mini Setup process itself requires you to specify the computer name (using whatever method) before joining the domain, so I doubt it's pulling the names down from AD, but more likely an answer file with computer names.
jsnetman Posted July 31, 2008 Posted July 31, 2008 If you are using RIS or WDS you can prestage them with the GUID and the settings in sysprep will pull the name down because the GUID matches. If the guy with the problem has added new machines to the network he has to pre-stage them as Geoff suggested in a previous post in this thread.
torledo Posted July 31, 2008 Posted July 31, 2008 Thats right, my sysprep.inf file has the reference %AMCHINENAME% for the machine name and %MACHINEDOMAIN% for the domain to join. All I do is boot machine via PXE to WDS, set it to pull the image down, and after 10 mins it's sat at the logon box waiting to be used. If you want a copy of my sysprep.inf file i'll happily post it up here. if you could ste, that would be great.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now