Removing a PC from the domain and then adding it back via RDP

[bodminman]

Hi there,

I have a few machine on the domain that have started to show to following in event viewer:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 30/10/2011
Time: 10:10:08
User: NT AUTHORITY\SYSTEM
Computer: YR6-TEACHER
Description:
Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

I want to remove the workstation from the domain and then add it back as part of a troubleshooting article I'm going through. My question is that if I access this machine from the DC using RDP and remove it from the domain, will I be able to access the machine again after it reboots to be able to add it to the domain again?

Thanks

[Steve21]

Might be worth having a read of netdom, commandline domain control including a command called move, which can just use new and old domain data to move it over.

Netdom move

Never tried it, but seems to be what you want.

Steve

[Arthur]

If you also receive a message saying "The trust relationship between this workstation and the primary domain failed." you may want to reset the machine account password.

netdom.exe resetpwd /server:DomainController /userD:Administrator /passwordD *

More info here. Netdom.exe isn't included with Windows 7 by default so you need to install the Remote Server Administration Tools.

[sted]

Win7 with realtek cards by any chance?

If doing manually you can ive found just add/remove .local from domain name so less reboots

[strawberry]

stick vnc on it rather than rdp, but use sted's method,it should work.

[bodminman]

Win XP with Realtek cards at the mo.

[mhundley]

We have had a similar issue ourselves (albeit 1054 not 1053) when attempting to deploy software using GPO to machines running Realtek cards, it appears to be due to the net card changing modes during startup, this can leave a machine with no link to the server at exactly the point it needs one to authenticate with the domain or check GPO info.

I have put a post up on my blog covering what we did to fix the issue along with a couple of reference pages which seem to back up the 'fix' which I have put in place.

Thoughts of a Primary School Tech: Dell Optiplex 390 fails to apply GPO settings

Although this is a different EventID to the problem you are having, when I was researching mine I did see that the two appeared to occur together every now and again.

As always with advice on Edugeek, your milage may vary and I recommend you try it on a test machine first before potentially ruining your entire network

[dhomer]

Hi you shouldn't have a problem logging back in using RDP obviously you'll have to use local credentials once you are off the domain.


Dave

CENTREL Solutions

[bodminman]

Ended up installing TightVNC which gave the required functionality.

Thanks for the responses.