dose this tool work locally with vm's? or it requires remout connection to esxi? thx added: ok. I downloaded and read readme.txt and got an answer. ^)
If you're using ESXi, you'll need to extract the vmx file from sys.vgz yourself if you want to work locally. You'll need the vmtar tool to do that and that's only available on ESX/i afaik. ESX is possible to just extract using scp / sftp as the file's not packed up.
extracting the bios from sys.vgz being a complete nuibe at this. I have downloaded the bios tool and when atempting to remote extract the bios file i get the following error. 'Could not find datastore folder' I am running esxi4 u1 from a usb stick. i read on the post above that i wil need to manually extract the vmx file from the sys.vgz using vmtar What is the syntax of this app? once extracted i take it i need to manually extarct the bios file to be patched.
The tool looks for a datastore folder in /vmfs/volumes to put temporary files. Do you have a datastore folder with a usb install? I've never booted it that way. In VSphere client, what is the name of the folder where your vms are stored?
no i dont have a datastore folder. im my /vmfs/volumes if have 1tb main store Hypervisor1 Hypervisor2 Hypervisor3 4a4dfcd1-312d6e10-404b-001b21384daa 4b72c5e3-3a61e05b-ed4c-b9b6da83be5c 7c7b15ea-54f861ef-a388-473f43007b89 c2a427e4-2d317086-fef9-b5750d88536c the numbered folders are the real folders and the named ones are links to the numbererd folders I cant create a folder in there either I have now also tried renaming my store to datastore in vsphere client, I still get the same error, the only thing that was changed in the folder was the link was changed
The tool looks for a folder named datastore with a number on the end like datastore1. This is the standard name for the folder after a fresh install afaik. So if you rename it to datastore1 not datastore, you should be in luck. I'll put some logic into the tool to use the datastore that has the most free space some time.
the situation strange for me. I remove "#" for in ssh strings using vi but after restart exsi this file appears with "#" back/ Any ideas?
Why bother with any tools? slmgr -ipk slmgr -ilc Do you have SLIC 2.1 & you installed maching certificate? sebus
not complete. these steps are absent 8. Restart the management service “/sbin/services.sh restart” 10 – Kill inetd : kill `ps | grep inetd | cut -f2 -d” “‘ 11 – Start inetd: inetd just step 8 to restert esxi with f12... it doesn't work for me
not sure wht's this and how these 2 command will affect. in my pst above i described that i took bios with dell slic 2.1 posted by Alien2xx in here and the installed sertificate by opaTool.exe (I used it tool to activate w7 on my workstation and it works)
Are you saying that you couln't work out how to reboot the ESXi server or that rebooting didn't work? I'd be very surprised if it's the latter.. If you search in the vista / win7 / server forums you'll find plenty of explanations of this. If you do it this way, you can be sure that you are using the correct details.