You should see the unlocker.py file in there, and it needs to have read and execute permissions for all 3 groups. You can check this by running “cd /etc/rc.local.d” and then running “ls -lah”. If after running the esxi-install.sh file, the smctest reports “false” then it is most likely a permissions issue. Running “tar zcf unlocker.tgz etc” would build the unlocker.tgz file using the file in the etc/rc.local.d/ directory. zip file you had (the one without the unlocker.tgz) was correct, but needed an extra command to create the. This sets up the file with the correct permissions for the system.

I found that I also needed to run “chmod 555 etc/rc.local.d/unlocker.py”. sh scripts executable by running “chmod +x esxi*”. zip file in the datastore, I needed to make the. I actually just got version 3.02 to work! It took a bit of testing, but I finally figured it out.Īfter unzipping the. **running a dual Xeon L5640 which wasn’t “supported”:P If it still does the same thing, than try replacing all the double quote characters with a copy/paste of one of the existing quotes from the vmx file’s default entries it took me forever to figure this out but it seems for whatever reason copying and pasting this stuff results in different ascii values that look the same:S(unsure why)…. rwxrwxrwx 1 501 root 341 esxi-uninstall.sh rwxrwxrwx 1 501 root 189 esxi-smctest.sh rwxrwxrwx 1 501 root 336 esxi-install.sh

Sed: /bootbank/boot.cfg: No such file or directory esxi-install.shĬopying unlocker.tgz to /bootbank/unlocker.tgzĮditing /bootbank/boot.cfg to add module unlocker.tgz Win11_English_圆4.iso esxi-uninstall.sh unlocker.tgz lsīigSur.iso esxi-install.sh esxi-unlocker-301.tgz I am not having any luck getting this to work.

Mac vmware image