Windows hyper v - virtual machine

I have a windows hyper v  that has two virtual machines running off it.
I removed all the ram chips and upgraded them and then restarted the server but the exchange virtual machine wouldn't start.
In the midst of trying to figure  that out i deleted the avhd pertaining to the exchange (all mailboxes).
How can i get my system back??? Company Down! Email is currently being spooled with a smart host service.
I have a complete system backup 4 days ago that i managed to restore the old AVHD file and replaced the old RAM which i can boot from but cannot log into the server because i get an error message saying the trust relationship between the computer and the domain is broken.
I cannot seem to log into the domain nor the local account on the virtual machine.
am i using the right file? what should i do. I realized that the virtual server is booting from a VHD file that has always been on he hard drive.

Need understanding here please!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You are getting "trust relationship" error because the password of the computer account held by the VM is not sync with the password held by AD. With this error you wont be able to log on to the server using AD credentials without disjoining and rejoining the server to the AD (not recommended, maybe last resort).

if the old avhd file is not older then 30 days(default time for computer account password refresh), then you might be able to use this avhd. However, since, you booted of the vhd, I fear this might have changed the VHD file in some way making any snapshot(avhd) invalid. You can try booting of the avhd by Virtual Hard Drive by with the avhd file, However make sure that the avhd is chained to the vhd using the inspect disk option.

Best of luck.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I guess you can run a sysprep to generate new ID for your VM, then rejoin it on the AD domain.

Good luck!
kevinhsiehNetwork Engineer Commented:
Hopefully you can use a local logon to your VM and then disjoin and rejoin the domain.
If you need to reset the local administrator password because you don't remember it, you can reset it using the following link. I would backup your VHD and AVHD files before you make the change. 
Once you get back online, you should stop using VHD snapshot files for your production servers. Thay are not backups, and have several risks including the situation you just found yourself in. 
lasanjiAuthor Commented:
Needed an explanation as to why switching all of the RAM chips for upgrade should cause this error in the first place! the add remove function only worked with the old ram modules.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Virtual Server

From novice to tech pro — start learning today.