Latitude D610 Fails To Join Domain During Unattened and Sysprep Install

Question

We are seeing this problem in several different facets.  I'll provide a little background first.  We are currently using a product call ON Technology CCM to deploy operating systems and applications.  The application was not all that impressive when I first saw it, and now that Symantec bought it, it is simply awful and support is even worse:smileymad:.  Once we heard they were being bought out, myself and one of my co-workers were able to persuade management to implement Microsoft SMS 2003.  It took some work, because there was a previous failed SMS 2.0 implementation which left a bad taste in everyone's mouth.  But we have successfully implemented SMS 2003, and it is running wonderfully:smileyhappy:.  We have also begun using the OS Deployment feature pack, and life is wonderful, at least right now.  So we are phasing CCM out slowly, and our main push will be when we migrate our workstation operating systems from Windows 2000 SP4 to Windows XP SP2 later this year.      CCM uses a full unattended install to load the operating system via PXE boot.  The SMS OSD uses a sysprep'ed image and Windows PE.  During the CCM unattended install (which is installing Windows 2000 with Service Pack 4), in which the unattend.txt is configured to join our domain, the D610 fails to join the domain.  All other platforms work fine.  Upon rebooting the D610, one can manually join the domain using the same credentials that are provided in the unattend.txt file.  There are no chipset drivers loaded during the unattended install, just network, video, and audio drivers.  I had read (in a message thread regarding the D410 and D610) that some people were leaning towards the Intel Mobile chipset causing some sort of a conflict with the Broadcom driver, but my findings dispute that.  Here is a link to that thread: http://forums.us.dell.com/supportforums/board/message?board.id=latit_network&message.id=6012 However, in that thread, there is mention (by Pharma, 03-30-2005 @ 0838 AM) of not using the -PnP switch for Sysprep, and successfully loading a sysprep'ed image and joining a domain.  Unfortunately, for an unattended install, full plug and play enumeration is always done.      So I then made a Sysprep build of Windows 2000 SP4 to use with the SMS OSD.  I did use the -PnP switch when canning the image, but that is unavoidable.  We use one image per operating system for all platforms (Dell OptiPlex GX110, GX150, GX260, GX270, & GX280; Dell Latitude C400, C600, C610, C810, C840, D400, D600, D800, & D610).  The Windows 2000 SP4 sysprep'ed image works fine on all platforms except the D610.  Now here's the twist - the Windows XP SP2 sysprep'ed image works on ALL platforms (except the GX110's, which are in the process of being replaced and will never be loaded with Windows XP), including the D610.  And when I canned the Windows XP image, I did use the -PnP switch with Sysprep.      Now that I've written a book for you all to read, if anyone has any insight as to what can be done to eliminate this issue, I would be truly grateful (and more than happy to buy you several beers, should you ever happen to visit Columbus, OH).  I have been working on this for close to two weeks now, and I am at my wits end with it.  Thanks for taking the time to read my novel, and I look forwards to any help you may have to offer.  Have a good day.                      Jeff

_down_ · Answer

My D610 is configured as follows:
- ATI X300 graphics card
- TPM chip is disabled in BIOS
- TrueMobile 1450 (mini-pci) is disabled in BIOS
- Bluetooth 350 card is active
- In boot order only Onboard NIC and Internal HDD is activated
- Broadcom drivers used are 7.86 from broadcom.com (b57w2k.sys, b57win32.cat, b57win32.inf)
- I use Windows 2000 w/ SP4 CD as well

Does your D610 config differ in any way from mine? I've experienced weird behavior in early BIOS versions of other models due to bootorders.

_down_

StLouisJ · Answer

We currently do not add the chipset drivers to the unattended installs, as we have seen issues in the past. We only add audio, video, and NIC drivers. We have also tried both Windows 2000 with Service Pack 3 and Windows 2000 with Service Pack 4 CD's, to no avail. I've been dealing with our account reps at both Dell and Microsoft. Microsoft wants us to open a support call, but I don't want to burn one there. I think we are going to let Dell and Microsoft hash this out. Sorry I didn't have more info to offer.

Jeff

_down_ · Answer

Hi

I also have had this issue with the D610 and ON Command/CCM, but in my case the problem was due to that I had included the chipset inf files in the unattended installation. When removing these and just providing the graphic, network and audio drivers it worked like a charm. Afterwards I install the chipset drivers using a standard package.

Another issue with the D610 is that it hangs during boot if you enable DMA for the IDE channel that hosts the DVD if you've installed intelide.sys during chipset installation. Guess that the intelide.sys doesn't support the chipset fully.

Don't know if this helps at all since my working configuration in unattended is the same as your that isn't working(!?) :/

BIOS version is A03

Regards
_down_

StLouisJ · Answer

Yes, in both my sysprep.inf file for the Sysprep installs, as well as the winnt.sif file for the Unattended installs, I ahve defined the Domain name to join, as well as the credentials to use.  We do not, however do the old style domain join, as you have indicated.  We are a fully integrated Active Directory environment.  I'm still waitint to get an honest answer from Dell on this.  They are saying it is an OS issue, but considering it only happens on this one platform, and both Sysprep and unattended installs are tried and true, I beg to differ.  I'm getting very frustrated at this point.  I've never had a problem with Dell until now, I've always recommend Dell until now, and now I am almost to the point that I'll say, let's buy HP instead!!!

odcheck · Answer

Please tell me anybody if your're using the sif file for RIS installation oder syspreb.inf

never-the-less Please check if You have got a similar entry there:

[Identification]

JoinDomain = risserver

DoOldStyleDomainJoin = yes

CreateComputerAccountInDomain = 0

:smileywink:

We will find out what the problem is if we all work together.

StLouisJ · Answer

Unfortunately, we still have no resolution on this. Dell and Microsoft are pointing fingers. We just got some D810's today, and I'll be adding them to the process soon. I'm curious if this happens on that platform as well. If not, I'm 99.9% positive this is a BIOS issue, but I'll let you know. Thanks for keeping up on this. I find it hard to believe you and I are the only two people seeing this issue. I'll keep you posted.

Jeff

Gunstad · Answer

Hi,

Have you guys made any headway with this? I support RIS at a large company and we just started ordering the D610's and are having the exact same issue. We have several different flavors of desktops and notebooks out in the field and functional in RIS, and this is ONLY a problem on these D610's. I'm also at wits end and have tried pretty much everything I can think of. If you've discovered any solutions for this and would be willing to pass them on I would be extremely greateful. Thank you!!

Gunstad

DamoH · Answer

Hi All, Found this thread while investigating the same problem on D810 and D410 latitudes using a RIS installation that works fine on all other models. Couldn't get it working despite trying a number of things (downgrading BIOS, leaving out various drivers, changing entries in SIF files etc) and ended up doing it semi-automatically by adding a line into the script run from [GUIRunOnce] like so: c:
tdeploy
etdom join /d:domain_name %computername% /ud:domainadminaccount /pd:domainaccountpassword /OU:'OU=Our_OU,DC=xxx,DC=yyy,DC=zz' (with appropriate if statements before it to ensure it is only run for the models with the problem) It's only a workaround, but until Dell fix the problem it might be the best we have.... Damo

AndersBergman · Answer

We have the same problem in our company.   Unattended setup of Windows 2000 with SP4 and the JoinDomain fails if we have included the Chipset drivers. If we exclude the chipset drivers the installation works like a charm.   Computer model is Dell Latitude D610

AndersBergman · Answer

We have now recieved answer from Dell and there is i slight problem in the ich6core.inf for the Chipset driver. Excluding the 'PCI/VEN_8086&DEV_2448' and 'PCI/VEN_8086&DEV_2660' part of the INF solves the JoinDomain problem.   Hope it helps in your case also.

Gunstad · Answer

Thank you very much for passing this along - although I'm wondering if you'd be willing to copy the contents of your 'altered' ich6core.inf up here so I can take a look.  I've tried tweaking this - but am still having problems - and it sounds like you might have a different version of this file than I can find anywhere (I can't find an ich6core.inf with the '2448' section in it anywhere).  Thanks much!

AndersBergman · Answer

Here you go.

; ****************************************************************************
; ****************************************************************************
; **    Filename: ICH6CORE.INF
; **    Abstract: Windows* 2K, XP, 2003 Server INF File for
; **               Intel(R) 82801 core devices
; **    Last Update: April 01, 2004 (Version 6.0.0 Build 1013)
; ****************************************************************************
; ****************************************************************************

[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGuid={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
CatalogFile=ich6core.cat
DriverVer=04/01/2004, 6.0.0.1013

[ControlFlags]
ExcludeFromSelect=*

[Manufacturer]
%INTEL%=INTEL_SYS

[INTEL_SYS]
%*PNP0103.DeviceDesc% = NO_DRV, *PNP0103
%PCI\VEN_8086&DEV_2640.DeviceDesc% = ISAPNP_DRV, PCI\VEN_8086&DEV_2640
%PCI\VEN_8086&DEV_2641.DeviceDesc% = ISAPNP_DRV, PCI\VEN_8086&DEV_2641
%PCI\VEN_8086&DEV_2642.DeviceDesc% = ISAPNP_DRV, PCI\VEN_8086&DEV_2642
%PCI\VEN_8086&DEV_266A.DeviceDesc% = NO_DRV, PCI\VEN_8086&DEV_266A
%PCI\VEN_8086&DEV_244E.DeviceDesc% = PCI_DRV, PCI\VEN_8086&DEV_244E
%PCI\VEN_8086&DEV_2662.DeviceDesc% = PCI_DRV, PCI\VEN_8086&DEV_2662
%PCI\VEN_8086&DEV_2664.DeviceDesc% = PCI_DRV, PCI\VEN_8086&DEV_2664
%PCI\VEN_8086&DEV_2666.DeviceDesc% = PCI_DRV, PCI\VEN_8086&DEV_2666

[sourcedisksnames]

[sourcedisksfiles]

[PCI_DRV]
Include=machine.inf
Needs=PCI_DRV

[PCI_DRV.Services]
Include=machine.inf
Needs=PCI_DRV.Services

[PCI_DRV.HW]
Include=machine.inf
Needs=PCI_DRV.HW

;**************************************************************************
; Do-nothing section used to avoid "Unknown hardware" installation prompts.

[NO_DRV]
Include=machine.inf
Needs=NO_DRV

[NO_DRV.Services]
Include=machine.inf
Needs=NO_DRV.Services

;****************************************************
; Generic ISA Root Bus / PCI-ISA Bridge / PCI-EISA Bridge

[ISAPNP_DRV]
Include=machine.inf
Needs=ISAPNP_DRV

[ISAPNP_DRV.Services]
Include=machine.inf
Needs=ISAPNP_DRV.Services

[Strings]
INTEL="Intel"
*PNP0103.DeviceDesc = "High Precision Event Timer"
PCI\VEN_8086&DEV_2640.DeviceDesc ="Intel(R) 82801FB LPC Interface Controller - 2640"
PCI\VEN_8086&DEV_2641.DeviceDesc ="Intel(R) 82801FBM LPC Interface Controller - 2641"
PCI\VEN_8086&DEV_2642.DeviceDesc ="Intel(R) 82801FB LPC Interface Controller - 2642"
PCI\VEN_8086&DEV_266A.DeviceDesc ="Intel(R) 82801FB/FBM SMBus Controller - 266A"
PCI\VEN_8086&DEV_244E.DeviceDesc ="Intel(R) 82801 PCI Bridge - 244E"
PCI\VEN_8086&DEV_2662.DeviceDesc ="Intel(R) 82801FB/FBM PCI Express Root Port - 2662"
PCI\VEN_8086&DEV_2664.DeviceDesc ="Intel(R) 82801FB/FBM PCI Express Root Port - 2664"
PCI\VEN_8086&DEV_2666.DeviceDesc ="Intel(R) 82801FB/FBM PCI Express Root Port - 2666"

Networking, Internet, & Bluetooth

Was this post helpful?