Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows Server » The security database on the server does not have a computer account for this workstation trust relation [Part 1]

The security database on the server does not have a computer account for this workstation trust relation [Part 1]

Posted on 24/05/202019/09/2023 Christian By Christian No Comments on The security database on the server does not have a computer account for this workstation trust relation [Part 1]
security database

Windows domains provide network administrators with ways to administer a great number of devices and control them from a central location. Domains are generally made up of computers on the same local network. When a computer is joined to a domain, it doesn’t use its own local user accounts. User accounts and passwords are managed on the domain controller. When you log into a computer on that domain, the computer authenticates your user account name and password with the domain controller.

This means you can log in with the same username and password on any computer joined to the domain. You may want to see the following articles: How to synchronize your on-premises AD with Azure Active Directory using the Azure AD Connect tool, Configure TCP/IP Parameters: Post OS Installation and configuration of Windows Server 2019 properties, and how to fix the trust relationship between this workstation and the primary domain failed.

This error is a bit self-explanatory shown in the cover photo. This is because the computer object was deleted for so some other reasons in my lab environment.Please take a look at the [Part 2] guide "How to fix the issue “The Security Database on the Server does not have a Computer Account for this Workstation Trust Relationship” on Windows Server".

Server Workstation Trust Relation Issue

Solution: Log on to the device with its local user account as shown below to solve this issue. For a similar error on the Windows trust relationship between this workstation and the primary domain failing, see the following link.

computer account

You will have to take the Server out of the domain and have it rejoined.
– Click on change settings

trust relation

In order to take the PC out of the Domain
– Click on Work Group

server

Click on Ok.
– This will prompt the following information window below

security database

Click on Ok
– This will prompt you to enter your username and password as shown below.

computer account

Click on Ok
– Now you will get a welcome message saying, “Welcome to the DFF workgroup(Server Workstation Trust Relation Issue)”

security database

Click on Ok
– Ignore the restart warning at the moment.
Click on ok as shown below.

trust relation

Now we want to add the server back to the Domain
– Local the System properties as shown below
– Click on change

Enter you Domain name
– Click on Ok as shown below

This will prompt you to enter the domain administrators password as shown below

When the credentials are entered correctly, the window below will be prompted


Thereafter you will be asked to restart in order for the settings to apply.

Click on Restart Now

And that is all. Now you should be able to access your server again
– Enter your account in the sAM account or UPN as you wish

Screenshot 2020 05 24 at 23.05.55 1
Screenshot 2020 05 24 at 23.05.55 1
Screenshot 2020 05 24 at 23.06.04
Screenshot 2020 05 24 at 23.06.04

I hope you found this blog post on Server Workstation Trust Relation Issue helpful. Please let me know in the comment session if you have any questions.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:Windows 10, Windows Server 2016

Post navigation

Previous Post: Differences between Capture image, Discover image, Install and Boot images
Next Post: How to uninstall the DriveLock Agent from your device

Related Posts

  • wacxx
    How to set up System Insights on Windows Admin Center Windows Server
  • maxresdefault
    How to join a computer to the Domain Windows Server
  • powershell commands lede 1024x276 1
    Enable WinRM on Windows Servers and Windows PCs Scripts
  • dfefeq
    Error 740: Elevated permissions are required to run DISM Windows Server
  • How to Change Active Directory Group Scope
    How to change Active Directory Group Scope Windows Server
  • Enable SSh And RDP In Windows Server
    Enable SSH and Remote Desktop Connection in Windows Server Windows Server

More Related Articles

wacxx How to set up System Insights on Windows Admin Center Windows Server
maxresdefault How to join a computer to the Domain Windows Server
powershell commands lede 1024x276 1 Enable WinRM on Windows Servers and Windows PCs Scripts
dfefeq Error 740: Elevated permissions are required to run DISM Windows Server
How to Change Active Directory Group Scope How to change Active Directory Group Scope Windows Server
Enable SSh And RDP In Windows Server Enable SSH and Remote Desktop Connection in Windows Server Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

sysadmin top30a

  • images 3 4
    Fix an appropriate resource file could not be found for the file for BitLocker Management Windows Server
  • Featured image WSL2 installation
    How to install WSL2 on Windows Server Linux
  • drivelock 1280x720 1
    The server could not be reached or validated: Timeout expired. The Time out expired prior to obtaining a connection from the pool Security | Vulnerability Scans and Assessment
  • AWS Budgets
    How to create AWS Budget AWS/Azure/OpenShift
  • BitLocker34
    BitLocker Back Door: Stolen laptop to inside the company network Security | Vulnerability Scans and Assessment
  • sdfdghjk
    How to fix “Job for Mattermost service failed” error Linux
  • Norton 360 Error
    Norton Autofix identified an issue: Fix Norton 360 Installation has encountered an error 8404 on Windows Anti-Virus Solution
  • ansible vault
    Fix AttributeError ‘ShellModule’ Object Has No Attribute ‘ECHO’ Configuration Management Tool

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,824 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.