Vmware tools fails with error missing freeBSD library

VMware Tools fails to start due to missing FreeBSD library

Details

If VMware Tools does not start after you install it, you might need to install a library that is missing because you do not have a full installation of FreeBSD 4.5.

Solution

Before you begin, make sure you have the FreeBSD 4.5 installation CD or access to the ISO image file.

To install the missing FreeBSD library

1. Reboot the guest operating system.
2. On the guest, in an X terminal, enter the following command to start the VMware Tools control panel:
   vmware-toolbox &
   If the following error message appears, the required library was not installed:
   Shared object 'libc.so.3' not found.
3. Insert and mount the FreeBSD 4.5 installation CD or access the ISO image file.
4. Change directories and run the installation script:
   cd /cdrom/compat3x
   ./install.sh

Workstation 7 Fails as have CPU support for CMOV, PAE, TSC, and FXSAVE instructions

Workstation 7 Fails as have CPU support for CMOV, PAE, TSC, and FXSAVE instructions

Symptoms

• Workstation 7 does not install on your computer
• The Workstation 7 installation fails
  You receive the following error:
  
  Error: This product can only be installed on a machine with CPU support for CMOV, PAE, TSC, and FXSAVE instructions.

Resolution

Due to changes in how Workstation 7 runs virtual machines, a new requirement is that host system CPUs must support PAE (Physical Address Extension) instructions. This was not a requirement in Workstation 6.x or earlier. Contact your CPU vendor to determine if your CPU has support for PAE.

Note: This also applies to Player 3.0, which has the same CPU installation requirement. This was not a requirement of Player 2.x or earlier.

If you are unable to install Workstation 7 on your host system because of this, install Workstation 7 to a different host that has a newer CPU or install an older version of Workstation.

Exporting a virtual machine to an OVF template fails

Symptoms

• Exporting a virtual machine to an OVF template fails
• VPXD fails with a Panic in VpxdViConsumerContext::AddError()
• The backtrace appears similar to:
  
  backtrace[04] eip 0x00b3f998 Panic (d:\src\vc40\vpx\common\vpxlog.cpp:258)
  backtrace[05] eip 0x013a1581 VpxdViConsumerContext::AddError (d:\src\vc40\vpx\vpxd\vapp\vpxdviconsumercontext.cpp:92)
  backtrace[06] eip 0x01767c18 Ovf::Vi2Consumer::GetDeviceIdAndAdapterType (d:\src\vimbase-vc40\vim\lib\ovf\consumer.cpp:1589)
  backtrace[07] eip 0x0176758e Ovf::Vi2Consumer::FindFiles (d:\src\vimbase-vc40\vim\lib\ovf\consumer.cpp:1540)
  backtrace[08] eip 0x01766d45 Ovf::Vi2Consumer::BuildFileList (d:\src\vimbase-vc40\vim\lib\ovf\consumer.cpp:1398)
  backtrace[09] eip 0x01766b10 Ovf::Vi2Consumer::GetIR (d:\src\vimbase-vc40\vim\lib\ovf\consumer.cpp:1373)
  backtrace[10] eip 0x0131a145 VpxdMoOvfManager::CreateDescriptor (d:\src\vc40\vpx\vpxd\vapp\vpxdmoovfmanager.cpp:793)

Resolution

This issue occurs when you create a virtual machine with a PVSCSI (VMware Paravirtualization) controller and attempt to export the virtual machine to an OVF template.

This is the only controller that VMware does not support when exporting to OVF template.

How to add Google Analytics code to phpLD Directory installation

You have to edit template/footer.tpl and put {literal} Add you Analytic code {/literal} before /body tag

you are done !! enjoy

Restart Management Agent on ESX / ESXi

Restart Management Agent on ESX / ESXi

To restart the management agents on ESX host:

1. Log in to your ESX Server as root from either an SSH session or directly from the console of the server.
2. Type service mgmt-vmware restart.
   
3. Press Enter.
4. Type service vmware-vpxa restart.
5. Press Enter.
6. Type logout and press Enter to disconnect from the ESX host.

If this process is successful, it appears as:

[root@server]# service mgmt-vmware restart
Stopping VMware ESX Server Management services:
VMware ESX Server Host Agent Watchdog [ OK ]
VMware ESX Server Host Agent [ OK ]
Starting VMware ESX Server Management services:
VMware ESX Server Host Agent (background) [ OK ]
Availability report startup (background) [ OK ]
[root@server]# service vmware-vpxa restart
Stopping vmware-vpxa: [ OK ]
Starting vmware-vpxa: [ OK ]
[root@server]#

To restart the management agents on ESXi:

1. Connect to the console of your ESXi Server.
2. Press F2 to customize the system.
3. Login as root.
4. Using the Up/Down arrows navigate to Restart Management Agents.
5. Press Enter.
6. Press F11 to restart the services.
7. When the service has been restarted, press Enter.
8. Press Esc to logout of the system.

How to remove hidden devices on Windows XP, 2003 servers

How to remove unwanted hidden devices from devices manager

Hidden devices may slow down your system by loading unwanted drivers in your system and some time it may cause problem in clonning or migration Server

Here is the 2 ways of finding hidden devices under Device Manager and removing them


Option 1:

* Start --> Run --> Cmd and press Enter
* Type command under command line with out quote "set devmgr_show_nonpresent_devices=1" and press Enter
* Type command under command line with out quote "devmgmt.msc", which should open Device Manager, click on view and navigate show hidden devices
* Expand all devices listed and remove grayed out devices.

Option 2:

* Right Click "My Computer" from Desktop and Click Properties, under Advanced tab you should see a button as "Environment variables" click on that.
* Click button "New" under Environment Variables and Enter "devmgr_show_nonpresent_devices" at "Variables name" and enter "1" under "Variable value" click on and close application.
* open Device manager and click "View" tab and navigate to show hidden devices, which will list all hidden devices
* Expand all devices listed and removed grayed out devices.