2,187
edits
Difference between revisions of "Troubleshooting (Virtual Machine)"
Jump to navigation
Jump to search
m
Troubleshooting (Virtual Machine) (view source)
Revision as of 13:25, 2 August 2012
, 13:25, 2 August 2012→Revert to Snapshot Causes Trust Relationship Failure: Corrected typo etc errors
m (Sstrutt moved page Troubleshooting (Virtual Machine ) to Troubleshooting (Virtual Machine): Typo in title (erroneous space after Virtual machine) |
m (→Revert to Snapshot Causes Trust Relationship Failure: Corrected typo etc errors) |
||
| Line 188: | Line 188: | ||
=== Revert to Snapshot Causes Trust Relationship Failure === | === Revert to Snapshot Causes Trust Relationship Failure === | ||
When reverting a VM that is a member of a Windows domain to a snapshot you can get the following errors at boot up or when trying to logon | When reverting a VM that is a member of a Windows domain to a snapshot you can get the following errors at boot up, or when trying to logon | ||
* '''The trust relationship between this workstation and the primary domain failed''' | * '''The trust relationship between this workstation and the primary domain failed''' | ||
* '''Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear, contact your system administrator for assistance.''' | * '''Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear, contact your system administrator for assistance.''' | ||
The problem is caused by the VM's computer account, which is used by the domain client/snapshotted machine to access the domain controller, having an invalid password. Domain member servers periodically change the password they use to connect to the domain with (by default every 30 days). So if a VM is snapshotted, then following that updates its computer account password; on a revert to snapshot it will revert to the old invalid | The problem is caused by the VM's computer account, which is used by the domain client/snapshotted machine to access the domain controller, having an invalid password. Domain member servers periodically change the password they use to connect to the domain with (by default every 30 days). So if a VM is snapshotted, then following that updates its computer account password; on a revert to snapshot it will revert to the old invalid password and be unable to login to the domain. | ||
* '''To resolve:''' | * '''To resolve:''' | ||
| Line 207: | Line 207: | ||
{| class="vwiki-note" | {| class="vwiki-note" | ||
|- | |- | ||
! The prevention options reduce domain security | ! The prevention options reduce domain security ! | ||
|- | |- | ||
| They should only be actioned if you understand the risks and are not breaching any security policies that | | They should only be actioned if you understand the risks and are not breaching any security policies that may in force at your organisation. | ||
If its not a regular occurrence, its probably best to just live the problem, and resolve when required. Snapshots should be allowed to run for many days in normal operation, which means that the problem should not occur frequently in a well run environment. | If its not a regular occurrence, its probably best to just live the problem, and resolve when required. Snapshots should not be allowed to run for many days in normal operation, which means that the problem should not occur frequently in a well run environment. | ||
|} | |} | ||