Glad I’m not the only one, although we two must be the only ones, looking at
the responses I’ve got :)
I saw that post, and it actually would work I guess, but when I have to do that
manually, a rather cumbersome process, I’d prefer using the fix for VM directly.
Try that on the host (or against it): Get-VM "<vmname>"|Get-VMFirmware|ForEach
{Set-VMFirmware -BootOrder ($_.Bootorder )$_}
That can’t be done within OSD sadly.
Maybe I’m trying to script the whole thing from the post.
Just wasn’t sure it’s worth it. I was thinking it just happens to me and I’m
doing something wrong.
Thanks roland!
From: [email protected] [mailto:[email protected]] On
Behalf Of Jonathan Robbins
Sent: Mittwoch, 12. November 2014 16:11
To: [email protected]
Subject: Re: [mssms] Fixing firmware on Hyper-V after multiple OSD
This happens to me every time I do OSD testing with a Gen 2 VM. I haven't yet
come up with a way to script it but perhaps you can follow the guidance in this
Technet article I follow whenever my list of bootable devices get a little out
of control in Hyper-V.
http://technet.microsoft.com/en-us/library/cc749510(v=ws.10).aspx
On Sun, Nov 9, 2014 at 8:41 AM, Roland Janus <[email protected]
<mailto:[email protected]> > wrote:
Bump?
From: [email protected] <mailto:[email protected]>
[mailto:[email protected] <mailto:[email protected]>
] On Behalf Of Roland Janus
Sent: Samstag, 1. November 2014 16:46
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Fixing firmware on Hyper-V after multiple OSD
Can somebody confirm that they don’t have the issue and I’m the only one?
That would give me an idea.
-Roland
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: Donnerstag, 30. Oktober 2014 16:55
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Fixing firmware on Hyper-V after multiple OSD
I’m not sure if that is a general issue. Saw a few posts regarding firmware
messed up and also some OSD related.
But wondering why this isn’t a broader issue.
Very heavy approach, especially when OSD would need to do that. OSC having
access access to Hyper-V?
Not really a good option but thanks :)
-Roland
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Marable, Mike
Sent: Donnerstag, 30. Oktober 2014 15:01
To: '[email protected] <mailto:[email protected]> '
Subject: RE: [mssms] Fixing firmware on Hyper-V after multiple OSD
I don’t know the background of what you’re working with, but would deleting and
recreating the VM be an option? You could script deleting the existing VM,
recreate it with the same settings (including MAC), and then kicking off a
rebuild.
I know it’s kind of heavy handed approach.
Mike
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: Thursday, October 30, 2014 9:33 AM
To: [email protected] <mailto:[email protected]>
Subject: [mssms] Fixing firmware on Hyper-V after multiple OSD
Reinstalling a hyper-v UEFI client over and over breaks the bcd store somehow.
The hyper-v settings in “firmware” show “load failed”.
Rebuilding this using hyper-v cmdlets works fine, but hat obviously doesn’t
work within OSD:
Get-VM "chbs-d000002 uefi"|Get-VMFirmware|ForEach {Set-VMFirmware -BootOrder
($_.Bootorder )$_}
This is just rebuilding it with the same values, but it fixes that anyway.
I like to have the bcd store fixed after OSD finished, but working with that
store is rather complicated.
Anyone has an idea how to fix that automated during OSD?
Or nobody else has that problem?
-roland
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be
used for urgent or sensitive issues
