How do I install Hyper-V integration tools (Hyper-v - 2016) on guest SBS 2008 Server (Its a Disaster Recovery Scenario)

I know 2016 is different and I am not sure if this works on virtual machine version 2, if you have made the virtual machine to a hyper-v version 2 maybe you can try version one.

Otherwise I found this

its changed since 2016 :( that option's been removed

The integration services are delivered through Windows Update now.

How about posting the BSOD error - I personally doubt it's because of integration services.

Second that. Integration services (or lack of) would not usually cause a BSOD.

I have to restore SBS 2008 R2 from a Windows Backup; hopefully to a Virtual environment due to TWO disks failing in a physical servers Raid5 set.

The error I get is this one (http://www.great-one.co.uk/archives/289) but there are no .log files and the other commands don't work.  I can boot into the Directory Restore Mode but can't run WUpdate from there.

Its a single server, the only DC.

see attached screen grab of the BSOD

thanks for you help.

PS: At the moment i'm copying the VM to a 2012R2 server - where I hope to be able to install the tools.
SBS-2008-r2-BSOD.jpg

95% certain you're wasting your time. (I'm not saying you shouldn't try it, but that's one of the last things I'd try and while I was trying it I'd be looking at how I could rebuild this from scratch or an older backup).

It's likely not the integration services. It's a corrupt AD.  You said the disks were failing! You created a VM out of a system on failing disks... there is probably corruption on the disks and that translated in the conversion process.  Either that or something did something odd and removed AD.
https://support.microsoft.com/en-us/help/2737463/domain-controller-does-not-start-c00002e2-error-occurs-or-choose-an-op

I would try an older backup, but depending on how long the disks have been problematic you could be in trouble.

Thanks I do have plenty of older backups and on different USB drives.  The first drive failed a week ago, we received the replacement on Wednesday, the second disk died on Thursday before we'd installed the new one, talk about bad luck.

I also just received replacement disks for the server, I was trying to restore direct to Hyper-V for a quick fix after seeing some people have done this successfully.  With 2003 I never had an issue - tested it many times as a DR option.

Another Question and sorry if its a stupid one, can I simply replace the contents of \windows\ntds from an earlier backup?  

thanks

Never tried it.  It MIGHT work... but the error sounds like the key DLLs, etc are missing... the DB may be fine.

just throwing this out there - after looking at Device Manager while in DRMode "security processor loader driver" can't load.  I'm looking this up but wondered if anyone knew what this does and if it could be a factor

Windows Restore to the original hardware, on a new disk worked seamlessly.  So It must have been the hardware drivers causing the blue screen.

thanks for all the advice - now all I need to do is P2V this old box :)

Migrate; don't P2V.  P2V literally converts, and while some products do a decent job of stripping hardware, you can often end up in the exact same boat.  P2V is a process of last resort.  Migrate whenever possible.

Thanks Cliff, unfortunately I've a very limited time with this server and maybe more importantly my companies resources which I'm using to work on this server (other temp HV Hosts, addition iSCSI storage etc.)

My plan is:

P2V the SBS 2008 server as it stands
wipe the physical server and install 2016 Hyper-V with GUI
import the SBS 2008 VM
install a new Virtual 2016 Server
migrate data and redirected files & decommission the 2008 SBS server.  (Exchange is being migrated to the cloud anyway.)

This is for a charity so I'm doing as much as I can as cheaply as I can :)

have a great weekend everyone.

Just to be clear, I am not in the habit of making companies/clients spend more money than necessary.  With a public company, they are beholden to stockholders. For a private company, the owner is in business for a reason.  Being fiscally responsible is laudible. That it is a charity doesn't change that fundamental dynamic.

Thus you can draw the conclusion that my suggestion to avoid P2V is the *best* reasonable cost solution.  I am also a believer that time is money (and when it comes to labor costs, that's a very real cost.)  If a migration takes 30 hours, and a P2V takes 10, and then takes 40 hours to address all of the post-P2V bugs, crashes, and random issues, the overall labor of P2V was more than a migration.

If the end goal is to retire the SBS serer, VM or otherwise, I'd prioritize the migration to 2016 anyways, since apparently that is the end goal.  The process of P2V and post-move cleanup is *literally* wasted energy if that is the goal.  For both your time and their resources, skipping that is the best option you have.

-Cliff