Re: Sysprep and joining domain



Hello Aaron,

I've searched the internet and newsgroups concerning the same issue as
yours. I'm responsible for the initial computer setup for a rather
large company and have recently received the new Dell Latitude D810
and D610 portables on my desk. We use unatteded installations scripts
to setup the new hardware with Windows 2000 SP4. The methodology in
joining the domain is fairly the same as creating an image with a
sysprep afterwards. Anyway it results in the same error message: An
invalid domain was specified. Would you like to proceed for now and
try joining a domain later?

I don't think however that it the cause is due to the incompatible
Broadcom Gigabit card (or driver) like stated in previous posts. It is
rather the combination of the broadcom wired networkcard and the dell
wireless networkcard, who both are active and loaded at the time the
computer is joined in the domain. I think that at this time the
computer is trying to join the domain through the wireless card, witch
doesn't work in our case, because we actually have no wireless network
configured in the company.

How did I come to this: In my first test both driver paths were
included in the OemPnPDriversPath parameter of my unattended file. So
on setup both devices we're discovered and provided with the correct
driver. But when joining the domain I received the above error, just
like you. In my new test today I removed the path of the wireless
networkcard and added the setup.exe of it to the [GuiRunOnce] section
of the unattended file, witch will run after the domain join. And
guess: no errors anymore when joining the domain and every device is
provided with the correct driver.

I think the same is possible with imaging. Don't apply the driver for
the wireless networkcard in the image. I'm not an sysprep expert, but
I think you can also include an [GuiRunOnce] section in it. Make the
driver files and iss file (installshield silent setup file) available
on the harddisk of the image and include the setup.exe command with -s
parameter in the sysprep file like specified below:

[GuiRunOnce]
Command0="C:\drivers\dell\R94827\setup.exe -s"

Everything is still installed in an automated way. If you have
troubles with this, please send me a mail.

Regards, Geerty
.



Relevant Pages

  • Re: 0x0000007B
    ... I got past the Windows setup infinite loop by copying NTLDR and NTDETECT.COM ... to an empty USB memory stick. ... There is an autorun Intel installation program that can be used to install ... Warning:Could not find a driver for Video Controller ...
    (microsoft.public.windowsxp.embedded)
  • Re: pit stops
    ... driver gap were so clear. ... I resent the term 'donkey work', not the full elaboration of what the ... "Massa did all the setup and tyre evaluation work so ...
    (rec.autos.sport.f1)
  • Re: HP JetDirect (now media center and HP 3310)
    ... What I have seen is the setup file will ... you can look at the driver properties for the file names. ... inf file in the temporary location. ... machine -- apparently I do still need to get the setup program to run. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Put an end to the Driver-Team contract system?
    ... we want to get rid of unfair equipment advantage a single driver ... "piece of cake" comment? ... one is the car design and the other being the ... car setup. ...
    (rec.autos.sport.f1)