Can you start Hyper-V Guest (Win 2008) in Safe Mode WITHOUT F8?

The problem is that the Hyper-V management console is not responding fast enough for us to "catch" the F8 option. We open the console, start the VM, click in the console to grab control. But the console just says, "Starting (and some misc info)..." But it does not show the usual BIOS boot info. Eventually it displays real boot up activity, but by then, it's well past the point where we could have pressed F8.

The guest VM is a 2011 SBS system that won't boot and we want to try to get started in safe mode. It would also be the DC, DNS, etc. for the network. Wer'e thinking it's unvailability to the Hyper-V may be causing the slow response and access to the console. Any ideas? Suggestions?
TACKHAsked:
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.

Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
Much like a physical system, you can just queue up the F8s. I open the console, start the machine, activate the console and then just keep pressing F8 until the keyboard buffer overflow beeps.
0
TACKHAuthor Commented:
That seems obvious, but the problem is the console is not accepting/passing along the F8 keystrokes in time to pass along to the booting system.
0
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
Hi

You need to delay the boot to give you the time to press F8.

1º You can do this by script: Check here an example:
http://jeffwouters.nl/index.php/2011/08/powershell-script-to-set-startup-delay-on-virtual-machines-in-hyper-v/

2º Or you can change the settings to delay boot. Check here:
http://www.petri.co.il/setting-virtual-machine-boot-options-windows-sever-2008-hyper-v.htm

Hope this can help

Jail
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

TACKHAuthor Commented:
Nope... that just delays the start of boot. It doesn't affect how quickly access is provided to the console after the boot starts. We are accessing the Hyper-V Host from a management console running on another Hyper-V Host. For whatever reason, probably because the guest SBS that won't start was the domain controller, the management console was taking too long to negotiate access to the remote guest we were trying to start. So, we copied the guest VHDs to the same Hyper-V host where the management console was located and mounted from that server. With everything local, we were able to boot the guest and effectively press F8 and get into safemode. After fixing the problem, which was an AVG / Windows Update compatibility problem, we moved the guest VHD back to it's original host and all is well. But thanks for everyones input.
1

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
TACKHAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for TACKH's comment http:/Q_27391466.html#36953148

for the following reason:

Solutions offered did not help. We found a solution on our own and thought it worth sharing.
0
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
We would have identified the cause of the problem as delays caused by remote access if the asker had included that fact.
0
TACKHAuthor Commented:
Please accept our apologies. But understand that we didn't know that remote access was the cause. That's the solution we were looking for from this group. If remote access is a know problem related to gaining F8 access, why didn't anyone, "Are you using remote access?" I sure couldn't find anything like that in general searches. We stumbled upon the solution trying anything we could think of to get this clients server back online and felt we should share it.
0
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
Virtualization

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.