If you do not specify this parameter a domain controller is chosen for you. Reset-ComputerMachinePassword -Credential -Server įinally, restart the VM and log in with the original credentials that you were using when the domain trust error message appeared. There is an optional parameter on the Reset-ComputerMachinePassword cmdlet to specify a domain controller in the environment as well. Reset-ComputerMachinePassword -Credential BSCORP\Administrator Also note that when you run this command a popup will appear asking you to input the password for the account specified in the PowerShell command. Be sure to replace the credentials shown below with your own domain admin account. Second, run PowerShell as an administrator and run the Reset-ComputerMachinePassword command. In this case Iâm going to log in using the account âBradleyâ. Domain Admin Account: BSCORP\Administratorįirst, log into the VM that is displaying the trust error message using a local account that is an administrator.Here is a little bit of background information that will come in handy over the next few steps as we resolve the issue: The solution for this particular error message is fairly simple but does require you to know the credentials for a local user account that is an administrator. Shift-right click an application and Run as different user to find out: To fix the trust, on the DM, run the same PowerShell command as per the shut down method above: Reset-ComputerMachinePassword -credential administrator.The problem manifests in an error message when attempting to log into Windows after applying a checkpoint and reads: The trust relationship between this workstation and the primary domain failed. The issue that I run into from time to time comes into play when I have to roll back my VM to a previous checkpoint (aka snapshot). I learned early on that rebuilding my laptop every time I needed to change a configuration for a given project or presentation was going to take up a huge chunk of my time so I started virtualizing. All of these things combine to mean I have to be ready for just about anything in relatively short amounts of time.įIXED: Hyper-V trust relationship between the workstation and domain failed. On top of my customer needs I frequently do presentations at SQL Saturdays and for Pragmatic Works. Some customers use web based VPN, others use software, sometimes I have to install a specific version of SQL while other times I remote into a workstation. Since I work as a consultant I have to handle a lot of different software scenarios. On the compliance rule check for value True. First up I created a Configuration Item that check if the relation is broken. This is based on the command Test-ComputerSecureChannel. Choose Advanced system settings in the left pane to open System Properties window. A different method is required on Windows Server 2008R2 or earlier which involves the use of the NETDOM command.įor several years now I have been using Hyper-V for building out a virtual development environment on my laptop. One of my demos was a script that repairs a trust relationship between a workstation and the primary domain. Right-click This PC and choose Properties. Note this fix only works on Windows Server 2012/Windows 8 or later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |