Broadcom, Sysprep, and Joining Domains - Issue Resolved

Windows XP

    Sponsored Links


  • 1. Install Windows XP Question?
    I began my installation of Windows XP upgrade last night from Windows ME. As we know the installation process takes about an hour, or at least it says it does. I wouldn't know because I fell asleep after about 10-15 minutes of the installation process. My question is did I miss anything in the middle or towards the end of the installation that I would have needed to fill out or was important? My computer was in a sleep mode this morning when I woke up, so I had to restart it. After restart, XP was up and running and just wanted me to register and activate it. Can I assume that everything is good to go and that I didn't miss anything during install? Please advise and thanks in advance! -Brad
  • 2. PC won't shut off when prompted
    My PC will not shut off. I go to START, then TURN OFF COMPUTER, then TURN OFF. I click TURN OFF and nothing happens. The computer stays on. I have checked on your site and it instructs me to go to POWER OPTIONS then choose the APM tab but I do not have this tab. What can I do to correct this problem? Right now I am manually shutting off the PC right from Windows but I fear this may damage some of my programs and/or files.
  • 3. VB SCript
    I'm trying to run this script in cmdlines.txt, while building the system (XP): strComputer = "" 'create the file system object set objFso=CreateObject ("Scripting.fileSystemObject") 'create the file object Set objTextFile = objFso.CreateTextFile ("c:\Infofile.txt", True) Set wbemServices = GetObject("winmgmts:\\" & strComputer) Set wbemObjectSet = wbemServices.InstancesOf ("Win32_ComputerSystemProduct") For Each wbemObject In wbemObjectSet objTextFile.WriteLine("Vendor : " & wbemObject.Vendor) objTextFile.WriteLine("Name : " & wbemObject.Name) objTextFile.WriteLine("Identifying Number : " & wbemObject.IdentifyingNumber) Next It doesn't work at that point, (fails at the "For" line) while it doesn't have a problem to run on the same machine later on, after it actually reboots and restarts. Does anyone know why and if there is any way to force this script to run at the stage, I'm trying to get it to work? TIA, Jarek
  • 4. Windows\System32\Config\System
    Greetings, My copy of Windows XP Professional recently crashed saying that the C:\Windows\System32\Config\System file is missing or corrupted. I cannot boot in safe mode, last known good, etc; but, I know that the file is there because I can see it when I run the recovery console from the XP install CD. Does anyone know how I can get this file from the Install CD using the recovery console? I foolishly did not create automatic recovery disks so I have to use the repair console. Thanks for your help! -N.D.
  • 5. XP PRO installation hangs...any way to debug?
    I had an XP Pro system on an Asus MB. I recently upgraded to a an Athlon XP and Soyo Dragon Plus MB. Before the MB/processor switch, I removed my anti virus progam, and all devices such as LAN, sound, etc. from the system device list. I then ran Sysprep, shut the system down, did the swap, booted up off the XP cd and did a repair. Everything goes fine until it hits the "35 minutes left" while installing the devices. I have rebooted 4 times and every time, it hangs at the same exact spot. One note, the system does not lock up but rather just doesn't get past that spot (on the last reboot, I let the system run for over 4 hours and still no go). I only have the ATI All-In-Wonder AGP card in the system and have disabled the onboard sound, the virus bootblock checker and LAN in the bios (until I get it running). Is there anyway to see exactly what is hanging? I have read that I might want to swap out the video card and then put the ATI back in after a good install so I'll try that tonight. Thanks in advance to all you gurus out there...

Broadcom, Sysprep, and Joining Domains - Issue Resolved

Postby gerson j. ricardo » Sat, 08 Apr 2006 02:48:58 GMT

Besides this aforementioned autosense nonsense you can also use earlier
revisions of Broadcom's drivers, especially for the BCM5700 line of
gigabit ethernet MACs.  I have a stable (aka production) Windows XP SP2
image built upon Dell Dimensions 4XXX and Optiplex lines, in other
words chipsets and ICH class drive controllers from the venerable 845G
to latest PCI-Express 975X.

In any case, using version 7.86.00 (which is WHQL'ed by the way) solves
to domain joining issue for me.  When using images with the v8.48e
driver (released October 2005); would seemingly always result in the
machine failing to join our AD domain.  Curiously if you forced the
machine down through a 10-sec ATX power shutoff sequence (ok, ok,
pressing down the power button for >10sec) and bring the machine back
up it would actually *sometimes* join the domain - but always
erratically and never in the first imaging attempt.

Essentially backtracking to v7.86 of b57xp32.sys (dated 8/23/2004) of
this driver revision solved the auto-domain joining problem in our

It would be well advised if Broadcom did some debugging and fixed this
issue within their next salvo of driver releases.

Gables Engineering, Inc

Similar Threads:

1.Ghost Image/Sysprep/Join Domain issue

When I deploy my XP SP2 image and then join the domain, it seems to take 
about 10 minutes to build the domain list, then it tells me the domain is 
not available.  Anyone seen this?  I have to reboot with no network, then I 
am able to log on.



2.Joining a Domain with Sysprep


I'm trying to get a sysprepped machine together to use as a standard
image in our offices.  However, I'm having an issue when setting it up
to join a domain automatically.  When it gets to the point of joining
the domain during mini-setup it hangs for about 2-3 minutes and then
times out and displays a message stating that the "Workstation driver
is not installed.  Do you want to wait and try joining the domain

What is going wrong?  Why is the workstation driver not installed and
what can I do to install it?  Help! ;)


Joseph Gruber

3.joining computer to domain using sysprep mini setup

Hi All,

I have created a winXP image using sysprep.  Everything works fine when it 
is started up for the first time until it gets to joining it to a domain.  It 
prompts me for a username/pwd sits for about 5 min then reports cannot change 
the computers' network id.  

Anyone know how to prevent this?

Also what is the best practise for this?  Should you include a username/pwd 
in sysprep.ini or leave it blank and enter it when prompted?


4.Sysprep and Joining Domain

I have a problem that I am ghosting a lab of computers and am using
sysprep to supply information to the mini setup.  Once the setup has
completed, the system reboots and comes up in windows 2000.  At this
point the system is joined to the domain.  The system reboots again to
finish setup and when it comes up the second time it is no longer
joined to the domain.

When it come up the second time the name of the domain is specified
under the workgroup box instead of the domain box.

Can anyone please help?

Thanks in advance

5.Sysprep not joining domain

I am using sysprep for imaging purposes and when the mini-
setup gets to the part about joining the domain it fails.  
I get an error message that the workstation driver is not 
installed.  If I then just join a workgroup, reboot, and 
join the domain after it reboots I have no problem.  I 
have used sysprep before and I have never seen this 
before.  But now I am seeing it on two different types of 

Has anyone seen this before?  Any suggestions?

Darren Brochu

6. Unalbe to join domain during sysprep mini-setup

7. Cannot join to domain after sysprep (XP SP2)

8. Windows Server 2008 R2 DC - sysprep XP and join domain

Return to Windows XP


Who is online

Users browsing this forum: No registered users and 15 guest