Windows Domain Account Login Fails with 'The Security Database on the Server Does Not Have ... '

How to Fix: Windows Domain Account Login Fails with "The Security Database on the Server Does Not Have a Computer Account for this Workstation Trust Relationship"

#Windows #ServerDoesNotHaveaComputerAccount #DomainLogin

[kyleapple]

I can't sign in as administrator! I don't what password I'm supposed to type

[Fala]

I get that error when I try to log in with the local admin account.

[kalpakrasam]

This error came in my exchange server that was connected in domain. I used this method but my all exchange configuration was lost. So what i supposed to do?

[itsumas]

The Change domain, member of is all grey'd out, can't make the change and/or reverse.

[phillipchan]

Do you know why this happened to the computer account?

[jettriver]

Its not accepting any passwords for all accounts....wot now?

[honkylips]

You dont have to add it to the workgroup. You can just rejoin to same domain and save a step

[nakaimmanuel]

this seems to be a temporary fix because the problem keep recuring.is there no permanent solution to the problem?

[yansofyandi]

but i wan leave this domain cant login

[KJL]

NOTE: if you are unable to rejoin the domain: "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed" run the following command:
net stop workstation /y
net start workstation


Re-attempt to join domain.

[inachu]

I need a app that pretends to be various computers that can be set or be taken from text file to have a list of computers.
Then grabs an account from a list of accounts then have the app log into those lets pretend 40 computers via the app using that account list.

Those 40 computers can already be logged in and on the domain but the purpose of the app is to make the Last logon time to be within showing as being logged in within 1 day.
The purpose of the app I want it to do is reset the last handshake for the computer. This way the active computers do not actually have to reboot and log back in and waste production time.

I am sure an app can be built to do this. I do know the computer or domain may complain there is already a computer logged in with that name but so what. This way
those 40 computers will not be touched by IT in any way shape or form and the 40 computers can continue doing what they are doing via what ever their assigned role was given to do.

[Mr.Elf_TYT]

Ffs im tryna to my first day of school it wont work f meeee

[inachu]

I bet yours get disjoined in the first place because it handshakes the server once a year or so. Or you have a real anal IT who remove computers from AD and SCCM that rarely
connect to the server to make that handshake that resets the the time from last This is very bad IT control and Microsoft in of itself does not care if a pc logs in
once every 5 years and it will never be disjoined because of a lack or handshake. It is OCD idiot managment who puts these rules into place.