HOW TO: Determine if VMware Tools is installed on PGP Universal Server 3.0.1-3.1.2
|Article:HOWTO42130|||||Created: 2010-09-10|||||Updated: 2012-08-14|||||Article URL http://www.symantec.com/docs/HOWTO42130|
This article describes how to determine if VMware Tools is installed on PGP Universal Server versions 3.0 up to 3.1.2
Note: PGP Universal Server 3.2 uses the vmware-open-vm-tools package now and this article is not relevant anymore since this version. If you need assistance with VMware Tools on PGP Universal Server 3.2 you should look at TECH149664
PGP Universal Server 3.1 is supported on VMware ESX 3.5.0, 4.0, and ESXi 3.5.0. VMware Tools must be installed and configured inside the PGP Universal Server operating system. VMWare ESX 4.0 is certified without VMotion.
To determine if the VMware Tools are installed:
Acess the PGP Universal Server command line interface.
At the command prompt, type rpm -q VMwareTools.
If VMware Tools 3.5 are installed, the output displays: VMwareTools-7299-64607
If VMware Tools 4.0 are installed, the output displays: VMwareTools-8193-164009
Accessing the PGP Universal Server command line for read-only purposes (such as to view settings, services, logs, processes, disk space, query the database, etc) is supported. However, performing configuration modifications or customizations via the command line may void your Symantec Support agreement unless the following procedures are followed.
Any changes made to the PGP Universal Server via the command line must be:
Authorized in writing by Symantec Technical Support or published as an approved and documented process on the Symantec Knowledge Base.
Implemented by a Symantec Partner, reseller or Symantec Technical Support.
Summarized and documented in a text file in /var/lib/ovid/customization on the PGP Universal Server itself.
Changes made through the command line may not persist through reboots and may be incompatible with future releases. Symantec Technical Support may also require reverting any custom configurations on the PGP Universal Server back to a default state when troubleshooting new issues
Article URL http://www.symantec.com/docs/HOWTO42130