Is there a reason VMTools isn't loaded into the latest OVA for v14? Or am I missing something?
Printable View
Is there a reason VMTools isn't loaded into the latest OVA for v14? Or am I missing something?
The console is not intended to be used other than initial setup. So there is no reason for the VM tools.
Got it. So I don't need to worry about having them then?
I never install it on Untangle.
With vmtools you can restart the vm and many automations work correctly in vcenter server like vmotion, HA etc.
For me is crucial and i install it afterwards always.
@bluechris steps to do so? I've found many conflicting instructions, but all for previous versions.
There is no difference in installation no matter the untangle version.
Tomorrow morning when I go to work i will find the instructions if you still want them but if you search in the forum here you will find them.
In the side of my head
1. I mounted the vmtools cdrom for linux in vcenter.
2. In untangle terminal i edited the sources.list by adding the stable debian deb
3. I installed gcc and make (i am not certain here)
4. Mounted the cdrom
5. Cd on cdrom
5. Install vmtools
6. Reboot
VMTools useless? WTF? No, just no... reverse course, stop being stupid.
VMTools inject the most recent drivers for full VMWare integration. This isn't just the agent that affords advanced functionality such as VMotion, it's also the most recent VMX drivers for the paravirtualized NICs required for high performance operation.
Advtertising a VM, for vSphere and not including the VMWare tools is logically inconsistent. However, there are multiple versions of the VMWare tools, and it's impossible to know what version every install needs.
So, what we have is the only realistic solution at this time. Untangle makes a VM that works not only with VMWare but many other platforms as well, and then the admin installs the appropriate tools. If the admin doesn't have the skill to install them as BlueChris just outlined, they probably don't need the advanced functionality anyway.
So yes, they are something that grants tremendous value, but no you don't have to have them for basic operation.
And if you need a script to do automatic shutdown or reboot, I invite you to learn how to script with a lovely little utility called plink.exe. It's part of the Putty suite.
Thanks for the quick responses. I was able to get VMTools installed using the tar installer mounted by VMware vCenter. I attempted the apt-get install method suggested by @dmorris but Untangle kept telling me that it couldn't resolve the URL for some reason (even though I had confirmed connectivity). I wish I could have done it that way.
So instead I followed, in large part, Sky-Knights suggestions in another post where I mounted the VMTools installer via vCenter and did the following:
mount /dev/cdrom/ /mnt/cdrom/
cd /mnt/cdrom/
ls -l
cp VMwareTools-x.x.x-yyyy.tar.gz /tmp/
cd /tmp/
tar zxpf /tmp/VMwareTools-x.x.x-yyyy.tar.gz
cd vmware-tools-distrib
./vmware-install.pl
At that point I just took the defaults of the VMTools installer and rebooted the Untangle VM. I'm recalling these commands and steps from memory so hopefully I didn't leave anything out. This article was particularly helpful too.
https://pubs.vmware.com/vsphere-50/i...16CC8166F.html
You can also install the open vm tools with
apt-get install --yes open-vm-tools
We removed them in 14.0 because we had video issues and we suspect open-vm-tools may have been causing issues. I now suspect its probably unlikely. If you do install the open-vm-tools and have problems with video, please let us know your setup & config.
I tried that first but for whatever reason Untangle kept telling me that it couldn't resolve the URL. I must have been doing something wrong or missing something implied.Quote:
Originally Posted by dmorris
Are the tools in the repo better suited for Untangle? That was my only concern when using the tar from VMware vCenter.
did you apt-get update first?
Yes, the ones in the repo will be updated with the regular upgrade process.
Other than that - I don't know how they compare to the tarball.
I don't think I did. I just followed what you mentioned in this post but didn't realize that I needed to run just a basic apt-get update first. I'll try that next time. Thank you.Quote:
Originally Posted by dmorris