SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Sunday, July 16, 2017

The trust relationship between this workstation and the primary domain failed

Everyone's had this problem - I just wasted a day yesterday trying to fix on a set of VM's. An update to VMWare Workstation caused a bunch of network issues - tracking many of them down was a real pain.

Additional note: this has become a common re-occurrence since updating VM Workstation 12 (specifically 12.5.7 build-5813279).

So Kudos to http://implbits.com/active-directory/2012/04/03/dont-rejoin-to-fix.html on how to fix this issue. I recommend using the netdom method - simply login to the box with problem as an administrator, open a command prompt (using Run as administrator) then enter:

netdom resetpwd /s:<domain server name> /ud:<user with permissions, domain\name> /pd:<user password>

Example:

netdom resetpwd /s:SysTestADMachine /ud:SysTest\ADManager /pd:ABC1234!

If not prompted, reboot anyway.

AS A SIDE EFFECT - your accounts might be a bit whacked, particularly if it is a server running application - be aware that you MAY have to reset the password for all system related accounts (application pools, etc.).

Some other issues that were encountered in my foray of fun yesterday:

Using NETDOM - the Target Name is Incorrect - the above corrects.

Using Remote Desktop - "The Local Security Authority Cannot Be Contacted" - simply reset the password of the account in Active Directory (Kudos: http://blog.mnewton.com/articles/solution-rdp-the-local-security-authority-cannot-be-contacted/).

NOTE: There seems another 'fix' per VMWare in which the Computer Password changes automatically which can get out of sync with clean systems. This is a Registry Fix (so if you don't know Regedit, don't try this):

  1. Open Regedit (using Run as administrator)
  2. Navigate to HKLM\System\CurrentControlSet\services\Netlogon\Parameters
  3. Change the DisablePasswordChange key from 0 to 1

A reboot may be required AND you might have to reset the computer password as above (using NetDom). Full explanation can be found here: https://communities.vmware.com/thread/327644






No comments: