vCenter 4.1 “No 64Bit DSN Found” DSN Error on Windows 2008 R2 Server

This error will appear when attempting to install VMware vCenter 4.1.

A work around for this issue is to create a system DSN.

Then open regedt32 on the server and go to HKLM > Software > ODBC.INI >

Update its driver to: C:WINDOWSsystem32sqlncli10.dll.

Restart the vCenter install.

Set-ExecutionPolicy : Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell’ is denied.

When running VMware PowerShell CLI you receive this error:

Set-ExecutionPolicy : Access to the registry key ‘HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1ShellIdsMicrosoft.PowerShell’ is denied.

Right click powercli and click: “Run As Administrator”

Once powershell starts type this command:

Set-ExecutionPolicy RemoteSigned

List off all the rules in order. This helps to see if an allow is overriding one of your denies:

iptables -nvL –line-numbers

Reject or Drop?

Drop means to drop everything at the interface and give no response. Best for port probes and the like.

Reject responds to the source. Best practices for TCP/IP