Disabling the screensaver saves valuable resources, also note that VMware KB 9275881 recommends disabling the Logon Screensaver as well.
You can disable the login screensaver via the registry: "HKEY_USERS\.DEFAULT\Control Panel\Desktop\ScreenSaveActive" should be set to 0
Set Visual Effects for Performance
These are unnecessary effects that waste CPU cycles, things like the fades transitions for windows and shadows under windows. You can change this setting under Control Panel -> System -> Advanced -> Performance Settings
If you don't need it disable it--you can stop the service to kill it entirely across the whole VM, or on a drive by drive basis by right-clicking and selecting properties. There is an option to index or not to index the drive.
Make sure VMware Tools is installed/running
This is more for remote control performance, VMware Tools improves the mouse greatly--also make sure you set the Hardware Acceleration to full
Use VMXNET Network Adapters
VMware Tools is a requirement for VMXNET Adapters, they are the best performing network adapters
Uninstall Unnecessary Hardware/Software
If the VM was P2V'd chances are it has things like OpenManage and Broadcom/Intel related software for the old physical NICs. You should remove this extra software that is no longer necessary.
Also the old network card is likely still installed, you can remove these by running "set devmgr_show_nonpresent_devices=1" at the command-line then going into device manager, select View -> Hidden Devices and you will now see all that old hardware and can right-click and uninstall.
VMware vCenter Mobile Access (vCMA) is a cool fling from VMware Labs. It allows mobile access to your vSphere environment via your vCenter(s). Setting up vCMA takes very little effort as it is packaged as a virtual appliance. You simply download vCMA as an OVF, deploy the OVF Template, and power on vCMA. Once powered on, config the network and your ready to go. Note that vCMA does not use a service account or static connector to vCenter, each user will login to vCenter via vCMA with their own credentials--think of vCMA as a web-based version of the vSphere Client.