Jump to content

IBM X60 Can´t join domain after win update


Recommended Posts

Posted

Hi

I have several IBMT60, HP2710p tablet, and IBM x60 tablet computers wich I have made new images for with XP SP2 (tablet for HP and x60).

Sysprep has been working fine for my computers before, but now its just working for T60 and HP2710p.

The X60 wont join the domain even though the sysprep.inf is the same and has ben working before.

I made new images from scratch with XP SP2, and the the difference between my old images and my new is that I have

updated my images with new drivers, some minor programs and of course windows update so now the images have SP3 installed.

Somehow some s*** has happend, and I don´t know why the x60 wont join the domain anymore.

My guess is that some patch of the windows updates has made som s*** with my image so the x60 won´t join the domain.

It´s really disturbing, now I mus join computers to domain manually, witch takes uneccessary time.

Is there anyone out there who can help me?

Can I be right in my guess, that some windows update patch makes joining the domain impossible?

Has anyone had a similar problem?

Thanks for any answers!

/mathew


Posted

What happens when you try to join the domain with the x60? I've not heard of or seen any problems with the x60 specifically after sysprep on SP3, so a little more info other than "it won't join the domain" would be quite helpful. Like, error messages, network traces, etc.

Posted

Thx for reply!

More info:

After sysprep, made image, push image to new computer, it halts on this kind of

message "cant join domain, do you want to coninue and join domain later".

And I can join domain manually after installation is done.

My sysprep.inf file is like the one below, and its the same sysprep.inf for HP2710p and IBM T60,

but with the difference that it works får HP and t60 and not for the X60.

I have a old image that works with this sysprep, so thats why I guess that its something with windows update patch

that are the reason for the problem, or maybe som new drivers.

My sysprep (modified with other names, pw, domain etc)

;SetupMgrTag

[unattended]

OemSkipEula=Yes

[GuiUnattended]

AdminPassword="qwert"

EncryptedAdminPassword=NO

OEMSkipRegional=1

TimeZone=110

OemSkipWelcome=1

[userData]

ProductID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

FullName="User"

OrgName="Organization"

ComputerName=*

[RegionalSettings]

LanguageGroup=1

Language=0000041d

[setupMgr]

DistFolder=C:\sysprep\i386

DistShare=whistlerdist

[identification]

JoinDomain=company.se

DomainAdmin=add domain account

DomainAdminPassword=password

MachineObjectOU="OU = computers, OU = city, OU = itg, DC = companyname, DC = se"

[Networking]

InstallDefaultComponents=Yes

I hope some one can have som tips on a solution

thx for answers

/ mathew

Posted

is the network initialized at that point? maybe the network drivers are not yet loaded. Press Shift-F10 at the error message, to open a command and see what ipconfig returns.

Posted

I tried shift+F10 and got cmd up (learned something new :-) ) and tested ipconfig, and the the reply was that no ethernet network shows up and the wireless network is not connected. So it seams that that is the big problem.... :-)

But I cant underständ why the networkdrivers isn´t loaded. In devicemanager it shows both network ethernet and wireless.

So how can I fix this?

Anyone outther who know the answer....

Thanks får replys!

/mathew

Posted

If you are not installing them manually before joining the machine to the domain then for some reason it appears the network drivers are not being installed until later in the setup process.

How are you supplying drivers? Where are you supplying the driver path?

Posted (edited)

I made a complete installation, xp, drivers, programs etc. Everything works fine, nothing missing in device manager.

After that, I sysprep the machine.

Make the image.

Reboot the new computer and it won´t join the domain, obviously because the drivers seams not to be loaded.

If I continue the installation / config after sysprep has done it´s work, the X60 works fine, nothing missing in devicemanager but is

just member in workgroup, not the domain.

I dont supply any drivers in sysprep and I havent supplied any driver path. I have never neded to do that before.

/ mathew

Edited by myfender
  • 2 months later...
Posted

Has this been resolved? Because I appear to be having the same problem, I routinely update the base images which we use within our organisation. However with the latest version of the image is unable to join our 2003 AD Domain during sysprep. It just sits at the Join domain screen and then eventually displays the following message after 15 minutes:

The domain could not be accessed due to networking problems, would you like to proceed for now and try joining a domain later.

If I add it to a Workgroup and proceed, reboot and then login as Admin. I’m able to add it to the domain.

I believe it may have something to do with a patch which has been pushed out via Microsoft since I last did updated the image (which was in September 2008.)

I will load the previous image and attempt to obtain a list of updates since then.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...