HOW TO: Install VMWare Tools for PGP Universal Server 2.8 to 2.12

Article:TECH149077  |  Created: 2007-11-06  |  Updated: 2013-05-10  |  Article URL http://www.symantec.com/docs/TECH149077
Article Type
Technical Solution



Issue



Note: This product has reached End of Life/End of Support Life for PGP Universal Server Version 2.x. For more information please see TECH143377

This article describes how to install VMware Tools for PGP Universal Server for VMware ESX/ESXi. 
 


Environment



PGP Universal Server 2.8 to 2.12

VMware ESX/ESXi 3.5, 4.0, or 4.1

Note: This article applies to versions of PGP Universal Server 2.8 to 2.12 running on VMWare ESX


Solution



VMware tools is installed in two stages on the PGP Universal Server:
 
Stage 1: ISO install or PUP update will install the outer rpm (pgppackage-vmware).
Stage 2: Manual install of the inner rpm (if PGP Universal is running on ESX server)
 
First you will need to verify which VMware Tools RPM packages are already installed. You can do so with the following commands from a terminal:
rpm -qa | grep vmware
 
That command will return what RPM packages you have installed on there currently.
If you see any files like vmware-tools-3.0-PGP, then that rpm must be removed (move to solution 2). If you see any files labeled as pgppackage-vmware don't modify those, leave those intact for now.
There are two solutions depending on the current situation of the VMware Tools installation:
 
Solution 1: If this is a fresh installation of the VMware tools.
Solution 2: If the prior VMware Tools inner rpm is already installed
 
Solution 1:
Step 1. Install the new inner rpm
  • cd /usr/share/vmware-tools
  • If it's ESX 3.0 - rpm -i --nodeps vmware-tools-3.0-PGP2.8.1.i386.rpm
  • If it's esx 3.5 - rpm -i --nodeps vmware-tools-3.5-PGP2.9.1.i386.rpm
 
Note: Do NOT use rpm -Uvf here.
 
Step 2. Restart the Network services manually.
· pgpsysconf --network
 
Solution 2:
Step 1. Erase prior vmware-tools inner rpm that is installed by using the following command:
Note: Remove only the files which has vmware-tools-3.0-PGP, do not remove any files labeled as pgppackage-vmware. Also the version for the vmware tools may differ depending upon the VMware version
This can be done by issuing the following command:
  • rpm -e vmware-tools-3.0-PGP*
Step 2. Install the new inner rpm
  • cd /usr/share/vmware-tools
  • If it's ESX 3.0 - rpm -i --nodeps vmware-tools-3.0-PGP2.8.1.i386.rpm
  • If it's esx 3.5 - rpm -i --nodeps vmware-tools-3.5-PGP2.9.1.i386.rpm
 
Note: Do NOT use rpm -Uvf here.
 
Step 3. /etc/init.d/network stop -- Stops networking
 
rmmod pcnet    Removes pcnet32 driver
rmmod vmxnet                Removes vmxnet drive
[Optional] depmod -a    Recreates module dependencies
modprobe vmxnet          Adds vmxnet driver
/etc/init.d/network start Start networking
 
Questions and Answers section:
Q: What VMware related files are installed as part of PGP Universal Server installation of 2.8.1 or later?
A: Currently (2.8.1 Build 2152+), a single rpm file is installed /usr/share/vmware-tools/vmware-tools-3.0-PGP2.8.1.i386.rpm.
This can be referred to as the "inner RPM". This single file should be present if the ISO/PUP install was successful. However, if there was a problem with the ISO/PUP install, the inner rpm can be copied to the system and installed manually.
Q: How do I manually install the file vmware-tools-3.0-PGP2.8.1.i386.rpm?
A: Copy it to /usr/share/vmware-tools and install it. This rpm is self-configuring but requires networking to be restarted manually.
Q: Is there an outer RPM?
A: Yes. This should have been already installed as part of an ISO install or PUP update.
If you type the following command: 'rpm -qa | grep vmware', you should see notice something similar to "pgppackage-vmware".
This outer rpm SHOULD NOT BE ERASED manually. This outer rpm is installed automatically by the ISO install or PUP update. If this rpm is not present, then the ISO or PUP install was incorrect or the inner rpm was installed using the command "rpm -Uvf".
Q: What happens when I install the inner RPM?
A: VMware tools is installed and configured.
Installation Output: There should be a new directory "/etc/vmware-tools", "/usr/lib/vmware-tools", and there should be the new kernel modules in "/lib/modules/2.6.18-1.2869/misc/"
  • Configuration Output: /etc/modprobe.conf is modified to include an alias to vmnics. The file /etc/vmware-tools/not_configured should not be present.
NOTE: /etc/rc.d/init.d/vmware-tools should be started and launch a daemon "vmware-guestd" which should be running (check using ps -ax). "ethtool eth0" should show the use of the vmxnet driver.
Q: How do I know that vmware is running successfully?
A: Check if vmware-guestd is running the command: ps -ax | grep vmware-guestd
Q: What VMware rpms will be installed on the system when all steps are completed?
A: There should be two rpms installed
rpm -qa | grep vmware
  • vmware-tools-3.0-PGP2.xx (x denotes version) <- inner rpm
  • pgppackage-vmware-2.8.xx (x denotes version) <- outer rpm
 
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.



Legacy ID



828


Article URL http://www.symantec.com/docs/TECH149077


Terms of use for this information are found in Legal Notices