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

SBS 2008 Guest Blue Screen on Hyper-V 2016 - I think I just need the integration tools installed
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Pierre BengtssonIT-AdminCommented:
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
TopCat-007Author Commented:
its changed since 2016 :( that option's been removed
Lee W, MVPTechnology and Business Process AdvisorCommented:
The integration services are delivered through Windows Update now.

How about posting the BSOD error - I personally doubt it's because of integration services.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Cliff GaliherCommented:
Second that. Integration services (or lack of) would not usually cause a BSOD.
TopCat-007Author Commented:
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 ( 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.
Cliff GaliherCommented:
If the backup was a physical server, often you can't. It'll have hardware drivers that are part of the image that crash when their associated hardware is missing. DR experts will often ecommend that the source should also be a VM (alleviating that problem) or should be backed up using a product that can do "hardware independent" restores. Also alleviating the problem.

But if the backup already exists and the source can't be back led up or migrated properly, sometimes the loss permanent.

It is commonly said that having untested backups is as bad as having no backups at all. If there was no tested restore plan  you've found a major hole in your DR scenario.... And just like having no backup  it can really sting when you discover that too late.

You can look for products that strip out 3rd party drivers from an existing backup.

Worst case scenario, you can restore files and the exchange mailbox store files and manually import mailboxes and reset ACLs. But if the source is toast and you can't restore to similar hardware (replace the drives and restore back!) then AD may be lost forever.

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
Lee W, MVPTechnology and Business Process AdvisorCommented:
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.

I would try an older backup, but depending on how long the disks have been problematic you could be in trouble.
TopCat-007Author Commented:
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?  

Lee W, MVPTechnology and Business Process AdvisorCommented:
Never tried it.  It MIGHT work... but the error sounds like the key DLLs, etc are missing... the DB may be fine.
TopCat-007Author Commented:
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
TopCat-007Author Commented:
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 :)
Cliff GaliherCommented:
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.
TopCat-007Author Commented:
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.
Cliff GaliherCommented:
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.

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

From novice to tech pro — start learning today.