ESX / ESXi Bios Tools

pix You Rock !
v1.1.5-One Click mod tool really rocks on ESXi 5.1

Just to do some hexedit on bioscod0.rom to add some slp 1.0 for oem xp before injecting to ESXi...

Could not test real time VMotion/DRS/HA 'cause don't have VCenter, but that shouldn't be a problem since all clustered ESX have the mod...

 

You need to login to view this posts content.

 

Thx sebus : Credit & thank given to the right chap !

 

Not sure if this is the right place for that, but here's my bios440.filename for ESXi 5.1 :
hxxp://rghost.net/41992173

Mod DELL PE_SC3 slic 2.2

Added slp 1.0 to activate OEM XP/2003 : Dell System, FUJITSU, ASUS_FLASH, Hewlett & Genuine



edit : Just tested in a VMwared ESXi 5.1 as bios440.filename directive & injected into vmx


PS : What shall we do now with our KMS 2012 ?
Oh wait ! There should be an instance of Excel 2013 running somewhere...

 

Try MonsterTurbo58's post "OEM activation of Server 2012 Datacenter with SLIC 2.2 in BIOS" in the Windows Server thread.
hxxp://forums.mydigitallife.net/threads/40623-OEM-activation-of-Server-2012-Datacenter-with-SLIC-2-2-in-BIOS
Sorry can't post links < 20 posts.

 

Having a "personal" KMS server in your "deploy testing environnment" is a must have, especially if you add a Win/Bind9 DNS beside !
(Yes, Hyper-V likes Linux/Kernel 3+ very much as MS participates into the Kernel project...)

Adding _vlmcs._tcp SRV record greatly improves "automatic" activations of any MS products kind
And that helps validating autounattended xml files...

Okay my corp already paid for if against MS, but i prefer not polluting the official KMS :
never been asked why billions of Vista/7/8/2008/2012 & Office products activated once and disappeared within seconds !

 

Find your post, and just dl the file, will be testing it shortly, and i'll comeback to report.
Once again thanx for sharing it!

 

you mean you injected you ESXI? and all OS you install in the ESXI become active?

 

Thank you so much for the tool,
i copied the Dell Rom and rename it bios440.rom and i inject over the SSH to the ESXI 5.1
i injected Dell SLI 2.2 to the ESXI however when i start the machine it still shows Dump Error (SLIC Table not Found)
do i have to reboot the ESXI after i inject the bios?

 

Hi Manolo,

Can you make a 5.1 vmx with an HP SERVER SLIC?

 

Ofcourse he can, and you should be also. Not rocket science, just using Andy's Phoenix Tool
Invest a bit of your own time & learn!

 

i`ve done it in the past, until esxi 5.0, using the provided tools. Now i've tried it on a HP Proliant Gen8 Server which i had ESXi custom HP image installed, version 5.1, and i couldn`t make it work. The first time i did it, virtual machines stopped to power on. Then i tought i did something wrong, which probably happened, so i did it again. The second time, virtual machines are booting ok, but i cannot activate any VM using only cert and serial.

This is what i`ve done, can you please tell me if i did something wrong?

1. Enabled SSH on ESXi
2. SSHed to ESXi host and found s.v00 (/bootbank/s.v00)
3. Created a backup copy of s.v00
4. Extracted s.v00 with "vmtar -x s.v00 -o output.tar"
5. Created temp directory
6. Moved output.tar to temp/
7. Extracted output.tar with "tar xf s.v00"
8. SCPed bin/vmx to Windows box
9. Extracted bios440.rom with ESXBiosTools 1.15
10. Got ACPITbls.rw from a running VM
11. Openned Phoenix Bios Tools, selected "other" (because there was no HP there), selected an HP Server SLIC 2.1 bin file, selected an HP SERVER SLIC 2.1 certificate (both matched with "verificate"), and loaded the acpitbls.rw file
12. Created bios440_SLIC.rom
13. Injected bios440_SLIC.rom on vmx file, sent it back to ESXi temp folder, changed permissions and ownership
14. Packed the s.v00 file again and moved it to /bootbank
15. Reboot
16. AIDA64 on a running VM reports _ASUS_ SLIC, even after i`ve choosen other on Phoenix Bios Tools and selected "HP SERVER" cert and bin.
17. I think that because of this it won`t accept a server license because ASUS has only client licenses, not servers.

Can you tell me what i`ve done wrong?

 

And where would _ASUS_ SLIC come from?
You are you you not running something else there?

With 1.15 tool you do not need to do any extraction by hand, as it does all for you anyway...

You can test your own mod WITHOUT injecting it back, just use bios440.filename =/path/to/rom/file in vmx of a new VM (so you can see what what SlicToolkit or AIDA or whatever you use reports as existing slic)

sebus

 

thanks all you guys, I tried it but failed, I use ESX/ESXi Bios Tools 1.1.5 to extract the bios440.rom and use phoenix tool 2.1.4 and rw1.5.3.7 to modify the bios with Fujitsu/Dell SLIC2.2 and use bios440.filename directive instead of inject it back, but the guest won't start, it stuck at boot screen showing the logo only.

the extracted bios440.rom is fine, if I use bios440.filename directive to use this file, it works. It was from ESXi 5.1.0, 1021289, bios440.rom sha1: 7bd32e9d866d39af257524911ebb7ae70cfd0682

I tried _Manolo_'s modded bios440.esxi51_SLIC_dell-pe_sc3_v22.rom and it works.

are there any specific setting/tool version to mod the bios or did i miss something?

I read the whole thread and found two other people experiencing similar issue and not solved, sorry i don't have the right to post links yet:
hxxp://forums.mydigitallife.net/threads/12982-ESX-ESXi-Bios-Tools?p=562851&viewfull=1#post562851
hxxp://forums.mydigitallife.net/threads/12982-ESX-ESXi-Bios-Tools?p=674260&viewfull=1#post674260

 

Nothing special. Just plain OK/Next/Go few times

 

Hello,

Does anyone have an updated link to Manolo's Mod DELL PE_SC3 slic 2.2 from post 324?

Thanks

 

Check post #331

 

updated info:

I've upgraded to vSphere 5.1 U1 (1065491). Extracted and injected with 1.1.5 version and everythings works like a charm! (vMotion/HA/DRS included)

 

I've used 1.15 version with the phoenix tool 2.14 to inject slic 2.2 successfully, however the phoenix tool won't let me add slp (it's greyed out) any idea's?

 

You need to login to view this posts content.