I have latest snapshot of pfSense 2.0 Beta-5. I use it on vSphere ESXi hypervisor. I'v installed the Open-VM-Tools package, but this seems not to be working any more. Usually you get info that you have vm-tools installed and you get info of your interfaces etc... but not anymore. What's wrong in Open-vm-tools package when using vSphere hypervisor?

Does anyone have any info when open-vm-tools package is fixed ? I noticed that this bug has been open over half a year and seems to stalled. We have "manual" not so user friendly work around with propriatery vm-tools. I would like to use open-vm-tools package with single click and install method (works for cli amatours like me). So any info on this issue?

Today I updated all my vSphere ESXi servers with 4.1.0 update 1 patch and all other available patches. Then I updated all my pfSense 2 RC1 firewalls to latest firmware. Then I reinstalled open-vm-tools package's (just in case). Rebooted pfSense firewall.

Now vmtools are in Unmanaged status but still no interface information. Just can't figure this out. This should not be this complex to install open-vm-tools succesfully working.

Did several installs a couple of days ago trying to iron out an issue with my pfsense box and tried out the OpenVM Tools package again. Got the Unmanaged status, IP address, DNS name and Host. Seemed to be working just fine on my ESXi setup.

Did several installs a couple of days ago trying to iron out an issue with my pfsense box and tried out the OpenVM Tools package again. Got the Unmanaged status, IP address, DNS name and Host. Seemed to be working just fine on my ESXi setup.

One pfSense has now Unmaneged status and one Not installed status. Both pfSenses has the same version. All the Interfaces has manual ip-settings. No dhcp in use. Funny but I don't have any success to get any interface information.

I'm been banging my head to the wall (not helping any) with this issue. I'm lucky that I don't have any usability issues like regis. I have not done any "stress test" to pfSense with vm-tools installed just to figure out is there any major issues.

I really hope that develepers of vm-tools picks this problem up. Open-VM-Tools is only needed in virtualized environments and now it's non working => Open-Vm-Tools package is proken!