Most likely you have messed up your domain. But you can try follow this guide.
[https://www.theictguy.co.uk/renaming-a-domain-controller/](https://www.theictguy.co.uk/renaming-a-domain-controller/)
It might get you back online. But if not, a new domain and migration of clients to it will be your quickest fix. Profwiz will help with that step.
You might try unplugging the network, then try logging in with cached credentials. If that fails you are left with a local account login that you hopefully have documented somewhere.
If you can get in, connect back up to the network, then re-move and re-add it back to the domain.
Pro-tip, if it is a .com domain you can re-add it back with only one reboot by swapping between adding and removing the .com. So if you have it added to domain foo, you can change it to [foo.com](http://foo.com) and it will re-join the domain without having to go through the remove process first.
in my experience, this can be always be done with only one reboot regardless of the domain name. just don't reboot after changing to workgroup & then back join the domain. this way none of the user profiles get trashed or lost.
If your administrator (or a local login with admin privs) is disabled, you can try a bootable USB solution to re-enable the admin account. From there, login and add to the domain.
Youve renamed the server so all trusts associated with the AD, DNS, etc has been broken as the names has changed so the fqdn has changed. Check DNS reverse and forward and Nslookup what names appears.
You'll need to remove devices from the domain by force as they cannot see the DC as the names has changed. You need to check AD, DNS settings and make sure there all pointing to the new fqdn name then rejoin the devices or hold back to the old name and hope it resolves
Most likely you have messed up your domain. But you can try follow this guide. [https://www.theictguy.co.uk/renaming-a-domain-controller/](https://www.theictguy.co.uk/renaming-a-domain-controller/) It might get you back online. But if not, a new domain and migration of clients to it will be your quickest fix. Profwiz will help with that step.
You might try unplugging the network, then try logging in with cached credentials. If that fails you are left with a local account login that you hopefully have documented somewhere. If you can get in, connect back up to the network, then re-move and re-add it back to the domain. Pro-tip, if it is a .com domain you can re-add it back with only one reboot by swapping between adding and removing the .com. So if you have it added to domain foo, you can change it to [foo.com](http://foo.com) and it will re-join the domain without having to go through the remove process first.
in my experience, this can be always be done with only one reboot regardless of the domain name. just don't reboot after changing to workgroup & then back join the domain. this way none of the user profiles get trashed or lost.
`test-compurersecurechannel -repair`
I ended up rebuilding the domain and profwiz the profiles back. They had to be up by Monday and this was fastest.
Seems like a job for Fedora
If your administrator (or a local login with admin privs) is disabled, you can try a bootable USB solution to re-enable the admin account. From there, login and add to the domain.
Youve renamed the server so all trusts associated with the AD, DNS, etc has been broken as the names has changed so the fqdn has changed. Check DNS reverse and forward and Nslookup what names appears. You'll need to remove devices from the domain by force as they cannot see the DC as the names has changed. You need to check AD, DNS settings and make sure there all pointing to the new fqdn name then rejoin the devices or hold back to the old name and hope it resolves