[mdt] 64bit Win7 Ent - Not joining domain

[garethEds]

Morning All,

 

Last week I started experimenting with 64bit Win7Ent and MDT. We have it working fine with our 32bit image and it's great. We are now in a position to take the 64 bit version across our site.

 

However - for some strange reason the 64bit image will not join the domain. It makes 4 attempts before stopping. The machine then proceeds to build without any issues. It is picking up network drivers without issues just not joining the domain.

 

I've basically copied the same Task Sequences as the 32 bit install.

 

The machine is picking up the correct name from the MDT database, installing all the drivers as well.

 

Got me stumped. So any advice is appreciated.

 

Gareth

[garethEds]

Seems we've sorted it. When re-imaging the machine using MDT I have to remove the previous instance from the OU/AD otherwise it cannot re-join or re-claim the name. This is odd as I don't have to do it when re-imaging with our 32 bit image. Only the 64bit image.

 

There must be a way to get the machine to force itself back on.

 

Oh well.

 

Gareth

[morganw]

If you rebuild a second time, does it work then? Perhaps the machine account cannot be overwritten if the CPU architecture doesn't match.

[garethEds]

If you rebuild a second time, does it work then? Perhaps the machine account cannot be overwritten if the CPU architecture doesn't match.

 

Good shout - I'll try this tomorrow with a machine that has finished rebuilding.

 

Thank you

 

Gareth

[FN-GM]

AD itself isn't aware if a machine is x64 or x86.

 

I don't see why you should have an issue, we don't have any issues at all.

[garethEds]

AD itself isn't aware if a machine is x64 or x86.

 

I don't see why you should have an issue, we don't have any issues at all.

 

I wasn't sure. Can you export your Task Sequence? I'll post my error log here tomorrow.

 

Gareth

[FN-GM]

It's in SCCM 2012. Not MDT as such but the me principle should apply.

 

What have you specified in your sysprep file?

[ChrisH]

You will probably find it will work okay next time, sometimes it doesn't "overwrite" the account if a different user account is used from the one that was used the first time.

[garethEds]

More news from this issue - we thought it was sussed but seems it wasn't.

 

I deleted some machines from the AD last night and set about rebuilding the 32bit installs to 64 bit - came in this morning and our of 7 machines, only one had succeeded. The rest were all showing 4 attempts at joining the domain.

 

A quick test of rebuilding with our 32 bit image worked straight away. Really, really strange.

 

What is funny is that during the build when updates from WSUS are being applied I can manually join the domain to the network using the same credentials as MDT. It then proceeds to build as normal.

 

Gareth

[garethEds]

After a bit of reading on the MS Deployment forums this evening, it seems there is a bug in MDT 2012 and 2012 UPdate 1 in that machines will not join the domain when imaging. There is a workaround which I am going to try out tomorrow. I'll report back but in the meantime here is the link:

 

MDT 2012 - Domain Join for different domain fails

 

and

 

MDT2012 Unattend.xml domain join no longer works

 

and many more people moaning as well.

 

Hope this helps and we'll see if it works in the morning.

 

Gareth

[garethEds]

Well it seems it worked. Am trying with another computer now.

 

Gareth

[garethEds]

Just popping back in to say that this definately seems to have fixed the issue. Until Microsoft sort it out with Update 2 or a newer MDT then this is an ideal workaround.

 

Phew.

 

Gareth