The trust relationship between this workstation and the primary domain failed When playing around with some Hyper-V servers that have been inactive for some time, we received an error: The cause of this is due to the fact that Active Directory is doing a lot more than simple user name and password storage. We found that a Hyper-V system that remains off for some time, then is turned on again can suffer this. The reason for this has to do with the way that some applications use the Active Directory. Take Exchange Server, for example. Exchange Server stores messages in a mailbox database residing on a mailbox server. However, this is the only significant data that is stored locally on Exchange Server. All of the Exchange Server configuration data is stored within the Active Directory. In fact, it is possible to completely rebuild a failed Exchange Server from scratch (aside… Read More »The trust relationship between this workstation and the primary domain failed Hyper-V Server
Enabling Replication Failed The System Cannot Find the Path Specified Hyper-V While trying to replicate a Hyper-V server you receive the following error: Enabling replication failed Hyper-V failed to enable replication for virtual machine “Machine Name”: The system cannot find the path specified. (I0x80070003). (Virtual machine ID “ID Number”) Cause The likely cause is that you have removed the path that was set under the replication server (or receiving servers) replication settings. Under the Hyper-V Setting on the receiving or replication server, click on the “Replication Configuration Enabled as a Replication server” The Fix Browse to the directory defined under “Specify the default location to store replica files” and ensure that the path is valid. The likely cause is that the folder defined here was removed and needs to be redefined. This can happen when you are cleaning shop.
The trust relationship between this workstation and the primary domain failed Windows 2012 R2 Hyper-V snapshot
The trust relationship between this workstation and the primary domain failed Windows 2012 R2 Hyper-V ‘ After working with Hyper-V and Snap shots, you may find that a previously working domain member machine gets this error message. This is because the Domain Controller will automatically update passwords of Machine Accounts every 30 days, and a restored snapshot may not match the new pass. The solution On the effected client machine open PowerShell Run the following command “Reset-ComputerMachinePassword” or specify the credentials switch if the account your running PowerShell with doesn’t have the correct AD perms for the CMDlet “Reset-ComputerMachinePassword –credential Domain\Adaccount” (You will be prompted for the domain password). After running this give the client machine a restart After Reboot, the server will function correctly.
We recently wanted to move a physical windows 2003 server to a virtual server. This is known as P2V. The machine happened to be a Windows 2003 Server running exchange. One of the reasons we wanted to move, was because the hardware was getting a little long in the tooth, and for various reasons, we did not wish to upgrade the version of exchange. [gard] We were almost successful too, but as you will see, the nail in the coffin was a typical Microsoft issue. One that is just one more reason why our future avoids Microsoft wherever possible. Convert P2V To the physical machine, we installed a VM ware free tool known as VMware VCentre Converter. http://www.vmware.com/products/converter/ An easy to use free tool, that converts your physical machine into a virtual VM ware compatible single file. This file could be run on a VMware server. It is really easy… Read More »Converting a physical Windows Machine to a Hyper-V Virtual Machine P2V Problem
There are a few little tips that I have learned the hard way this week while getting ready for a server data centre move. When migrating from a Virtual Server 2005 to a Hyper V server, you must ensure that you uninstall the Virtual Machine add on tools for Virtual server first. If you do not, you will find that the Hyper V tools will not install until the other package is removed. And that mouse control is not available until these tools are installed. We all know what a pain in the rear end it is to work a Windows server without a mouse. It is much easier if you do it as the last thing before shitting down the VHD before moving it.