#Hp part surfer windows
Worked fine as a version 2 Windows licensed workstation because the original case was W7 licensed. I happened to get two unopened version 2 Z620 virgin motherboards several years ago and entered the proper codes from the bottom of two spare slow version 1 Z620 cases. On a practical level this just does not happen, however. If is the codes on the bottom of your case that set what the motherboard can do, and the motherboard has no idea going in to the branding process what those codes are down there.Ĭould a virgin motherboard be branded with codes from another box? Yes. It is as if the licensing goes along with your case rather than the motherboard itself. depending on the codes entered it will become a Windows 7-licensed, or a HP Linux-licensed, or another Windows-licensed motherboard.
That virgin motherboard is like a blank slate. Those codes are not workstation-specific, to my knowledge. The new codes only come from you entering things properly from the labels on your workstation, usually on the bottom. The prior BIOS with its prior branded codes is thrown out with the failed motherboard. If you buy a virgin motherboard from HP it will be unbranded and when you enter the codes for use of Windows then it can run a HP OEM COA Windows installer on the assumption that the workstation is already licensed for running that. If the proper codes had been entered for Linux there would be no licensing fee going from HP to MS. You can't flash back and forth from Linux to Win branding. A virgin motherboard can go either way, just once, in the process. To "brand" or "tattoo" a virgin motherboard is an advanced procedure and not made easy by HP.
0 kommentar(er)
