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]] On Behalf Of Marable, Mike Sent: Donnerstag, 30. Oktober 2014 15:01 To: '[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
