VBscript code behind custom form in Exchange public folder is not running in Outlook 2010

In Outlook 2010, the default behavior was changed to prevent scripts from running in public folders. To re-enable this behavior in Outlook, follow these steps:

• Click File, and then click Options.
• In the list of categories, click Trust Center, and then click Trust Center Settings.
• In the Trust Center, click the E-mail Security category.
• Click to enable Allow script in Public Folders.

For more information read the following article from Microsoft

NIC teaming using EtherChannel leads to intermittent network connectivity in ESXi

When trying to team NICs using EtherChannel, the network connectivity is disrupted on an ESXi host. This issue occurs because NIC teaming properties do not propagate to the Management Network portgroup in ESXi.
When you configure the ESXi host for NIC teaming by setting the Load Balancing to Route based on ip hash, this configuration is not propagated to Management Network portgroup.
Solution:
After setting the load balancing property to Route based on ip hash for vSwitch0, set the same for Management Network portgroup.
To configure the NIC teaming properties:

    Select the ESX Server host.
    Click the Configuration tab.
    Click the Networking link.
    Click Properties link for the management network portgroup.
    Highlight the virtual switch in the Ports tab and click Edit.
    Click the NIC Teaming tab.
    Choose Route based on ip hash from the Load Balancing dropdown menu.
    Verify that there are two or more network adapters listed under Active Adapters.

Use these commands if the host does not stay connected to vCenter Server after the vSwitch load balancing policy change:
# vim-cmd hostsvc/net/vswitch_setpolicy --nicteaming-policy=loadbalance_ip vSwitch0
# vim-cmd hostsvc/net/portgroup_set --nicteaming-policy=loadbalance_ip vSwitch0 "Management Network" 

For more information read the following articles from VMware KB:
http://kb.vmware.com/kb/1022751
http://kb.vmware.com/kb/1003806
http://kb.vmware.com/kb/1004048
http://kb.vmware.com/kb/1003677

How to register a vCenter in vSphere 5 Web Client from command line

If you don't want to install Adobe Flash player in your server running vSphere 5 Web Client, then you can do that from a command line:

• cd \Program Files\VMware\Infrastructure\vSphere Web Client\scripts

• admin-cmd register https://vsclient.mydomain.local:9443/vsphere-client vcenter.mydomain.local <username> <password>

where vcenter.mydomain.local is the vCenter address, vsclient.mydomain.local is the vSphere Web Client address (it may be the same server where vCenter is installed), <username> is an Administrator account in vCenter and <password> is his password.
Open this link from a browser to check the web client: https://vsclient.mydomain.local:9443/vsphere-client/

Hyper-V gotsas

Please the following article from Microsoft

Setting the number of cores per CPU in a virtual machine

• Power off the virtual machine.
• Right-click on the virtual machine and click Edit Settings.
• Click Hardware and select CPUs.
• Choose the number of virtual processors.
• Click the Options tab.
• Click General, in the Advanced options section.
• Click Configuration Parameters.
• Include cpuid.coresPerSocket in the Name column.
• Enter a value (try 2, 4, or 8) in the Value column.

Note: Ensure that the number of vCPUs is divisible by the number of  cpuid.coresPerSocket in the virtual machine. That is, when you divide the number of vCPUs by the number of cpuid.coresPerSocket, it must return an integer value. For example, if your virtual machine is created with 8 vCPUs, coresPerSocket can only be 1, 2, 4, or 8.
The virtual machine now appears to the operating system as having multi-core CPUs with the number of cores per CPU given by the value that you provided in step 9.

• Click OK.
• Power on the virtual machine.

For example:
Create an 8 vCPU virtual machine and set cpuid.coresPerSocket = 2. Window Server 2003 SE running in this virtual machine now uses all 8 vCPUs. Under the covers, Windows sees 4 dual-core CPUs. The virtual machine is actually running on 8 physical cores.
Only values of 1, 2, 4, 8 for the cpuid.coresPerSocket are supported for the multi-core vCPU feature in ESX 4.x.
In ESX 4.0, if multi-core vCPU is used, hot-plug vCPU is not permitted, even if it is available in the UI.
Only Hardware Version 7 virtual machines support the multi-core vCPU feature.

For more information read this article from VMware
Also read the article Use Coreinfo to view VM core and socket count

Dell PowerVault MD3620f storage arrays configured with VMware ESX/ESXi fail

According to this VMware article you need to add a claim rule to ESX/ESXi host:
To add a claim rule:
Login to the ESX host as root. Run the command:
For MD3600i/MD3620i:
esxcli nmp satp addrule -V DELL -M MD36xxi -s VMW_SATP_LSI
For MD3600f /MD3620f:
esxcli nmp satp addrule -V DELL -M MD36xxf -s VMW_SATP_LSI

SNMP configuration steps for VI3 and vSphere 4.0/4.1

Please read the following article from VMware.