[mdt] New Image not joining the domain

[garethEds]

Morning all,

 

So I made a nice new image yesterday - probably the final W7 image I will ever make for the school (see other posts about W10). All procedures followed. I've been doing this for years without any issues and then BOOM.

 

The image which was imported to the Deployment share doesn't join to the network. It installs and runs through the task sequence before just stopping. No domain join at all - despite the details being in the cusomsettings.ini etc etc.

 

What would I have missed this time?

 

Gareth

[snagrat]

Is the FQDN specified in rules? Sometimes machines won’t join if only the NetBIOS name is specified

[garethEds]

I've tried a few things now - trying to remember what it used to be before our server died a death. Here are the logs from %systemroot%/debug/netsetup

 

Here is an image of the log file. I'm missing something obvious - but probably blind from years of it working.

 

 

Cheers

 

Guys

[snagrat]

Can we see the cs.ini

[garethEds]

Current log file - tries this 4 times. Struggling. I've checked the permissions for my user - they have permission to join the domain.

 

[sted]

i assume the account your using has permission to add/delete/modify computer accounts on that ou? might be worth as a test using a domain admin username and password (if it isnt)

[garethEds]

i assume the account your using has permission to add/delete/modify computer accounts on that ou? might be worth as a test using a domain admin username and password (if it isnt)

 

Yes - because when the machine is sat there as a local Admin I can join it to the domain using the credentials I have provided - so I'm not sure why it isn't happening during the deployment phase.

 

Cheers

 

Gareth

[Michael]

Presumably you've included all the latest updates as part of the snapshot? Been a while since I've deployed 7 now to be honest.

[garethEds]

Presumably you've included all the latest updates as part of the snapshot? Been a while since I've deployed 7 now to be honest.

 

Yes. The capturing has been easy.

 

Trying with a password that has no special characters now. I'm stumped.

 

Gareth

[Michael]

You're right, avoiding symbols is probably a good idea and just stick to lower, upper and numericals.

 

Other possibilities in the context of Windows 7 are LAN drivers, depending how you deploy.

[garethEds]

You're right, avoiding symbols is probably a good idea and just stick to lower, upper and numericals.

Other possibilities in the context of Windows 7 are LAN drivers, depending how you deploy.

 

Hiya @Michael - I thought of that but I am testing using HyperV2012r2 which has always worked. I'm trying to work out what I've done that is different from when I created the server several years ago.

 

Gareth

[Michael]

Silly question, but I presume your existing/old image still deploys? Can you ascertain what updates you've included differently?

 

And definitely in my experience, newer drivers do not necessarily mean better!

[sted]

possibly relevant have you updated mdt/wadk as i dont think later versions are designed to do windows 7 i ha weird issues trying to deploy 7 using mdt/wadk past a certain point

[dapaulio]

Are you using the same answer (unattended) file.

 

Quick google on status code points to permission of the user account supplied

 

In your answer file are the credentials hashed?

 

Try (as a test) sending them in clear text. If that works then you will need to regenerate your answer file.

[garethEds]

Right - some news. I've hard wired the join password into the customsetting.ini file (don't remember doing this before). It's gone in as the DomainAdminPassword= variable.

 

So what happened? The machine joined itself to the network with a random name as I expected it to.

 

But I don't remember putting the password into the customsetting.ini file before - especially as it's plain text.

 

Gareth

[Michael]

I've never considered this a massive issue to be honest. It's so buried within the Windows directory, most users have the local drives restricted anyway, but you can always delete the answer file manually/automated thereafter, hence no security risk.

[dapaulio]

I've never considered this a massive issue to be honest. It's so buried within the Windows directory, most users have the local drives restricted anyway, but you can always delete the answer file manually/automated thereafter, hence no security risk.

 

I was thinking more on the server it’s deployed from. But yes I agree

[sted]

Right - some news. I've hard wired the join password into the customsetting.ini file (don't remember doing this before). It's gone in as the DomainAdminPassword= variable.

 

So what happened? The machine joined itself to the network with a random name as I expected it to.

 

But I don't remember putting the password into the customsetting.ini file before - especially as it's plain text.

 

Gareth

thats the only way ive ever done it both boot.ini to connect to the deploymentshare$ and customsettings.ini to joint the domain but i use a specific account that pretty much has enough permissions to join a pc to the domain and read the deploymentshare$ share

[garethEds]

Thanks everyone for their help with this. All working now. However..... (another post coming).