Windows 7 logon error

[garethEds]

Right - have you seen this one?

Build a machine with MDT - all goes well. Machine is used all afternoon and then when the next user tries to log on we get:

'The trust relationship between this workstation and the primary domain failed.'

Machine then has to be rebuilt.

I've read about it but nobody explains why it has happened in the first place.

Gareth

[mounters]

You don't need to rebuild the machine, just unjoin from the domian, restart and then rejoin the domain should be sufficient.

[garethEds]

I would, but I cannot log in.

 

GJE

[mounters]

Use the local admin account as opposed to a domain account.

[garethEds]

I lie. Local admin is up. Hmmm - need to turn that off.

 

Gareth

[garethEds]

Nope - lying again. It isn't letting me do it.

 

There seems to be a hotfix: Error 1789 when you use the LookupAccountName function on a computer that is running Windows 7 or Windows Server 2008 R2 - I think this is the one - but I cannot log in so it's a pain.

 

Gareth

[garethEds]

If this is the correct hotfix then I shall have to add it to my image.

 

Why does it happen?

 

Gareth

[mounters]

When logged in as a local admin account you can't change the workstation to be a member of a workgroup instead of a domain?

 

As to why never really got to the bottom of what happens, its one of those infrequent events that just seems to occur.

[garethEds]

Hi Mounters,

 

Thanks for the advice. Believe it or not I cannot log in to the machine as a local administrator either. So I've left it this evening. The hotfix I mention above has been injected into the .wim image ready for deployment to other Windows 7 machines.

 

At the moment I have only 4 W7Ent machines built in a little test area of my classroom. Pupils are using them but like I said they keep loosing their trust. Hopefully the hotfix will stop that happening on other machines. As for the machine that is broken - I will re-deploy and see what happens.

 

Thanks again

 

Gareth

[pooley]

I ahve had this when either the machine is set as Disabled in AD or you havent rebooted after renaming the machine. Not sure either is related to your issue though

[garethEds]

HI Pooley,

 

I don't think so. Machines are named in the MDT database and linked to their mac address. I'm not yet an MDT expert (trying to get there), but we shall see if the above hotfix sorts anything out.

 

Regards

 

Gareth