Yes, and why didn't I just use A and B as examples? I could have saved so much typing...lol. Host A was 192.168.1.1 let's say, because I wanted the names to match. I ran the Get-VMhostfirmware with the correct parameters and then disconnected the host. I then changed Host B to 192.168.1.1 and added it to vCenter, I ran the command and received the error below. Both were in maintenance mode
From what I read, the cmdlet wasn't designed to be used this way...oh, and sorry, I left out vital information. The hardware is different, one host is a BL460c Gen 8, and the other is a BL460c G6. I'm doing this on purpose of course, because I want to see if it will work, I also plan on trying it with the same hardware, but I'm curious about the limitations.
PS C:\Users> Get-VMHost '192.168.1.1' | Set-VMHostFirmware -Restore -SourcePath c:\ESXibackups -Force
Set-VMHostFirmware : 7/9/2013 1:47:16 PM Set-VMHostFirmware A general system error occurred: Internal error
At line:1 char:30
+ Get-VMHost '192.168.1.1' | Set-VMHostFirmware -Restore -SourcePath c:\ESXiback ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-VMHostFirmware], SystemError
+ FullyQualifiedErrorId : Client20_SystemManagementServiceImpl_RestoreVmHostFirmware_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Host.SetVM
HostFirmware