Dynamic Binding in distributed vSwitch is depreciated in vSphere 5.0

As of vSphere 5.0 the dynamic binding option in dvSwitch port groups earned the "Depreciated Status"
Why..??
I am not really sure...:)

VMware recommends using Static Binding for performance gain:

But as described in the KB 1010593 and KB 1022312 the only difference is in the way the ports are assigned to VMs. With static binding the port are assigned "once and forever" until removal from inventory or changing port group. With dynamic binding port are assigned every time during powering up.

Personally I haven't noticed any performance issues with the dynamic ports. However it is strongly recommend to change it - so its time to plan some downtime...:)

Once caveat -> all VMs with particular Port Group must be powered off to change its binding type...:) 

VMware Update Manager: The session is not authenticated

Today I ran into strange issue with the VMware Update Manager 4.

Whenever I tried to enable plug-in I received following error:
There was an error connecting to the VMware vCenter Update Manager [VUM server name:443].
: Vmomi.Fault.NotAuthenticated : The session is not authenticated.

Also the C:\Users\All Users\VMware\VMware Update Manager\Logs\vmware-vum-server-log4cpp.log logged only the "Not Authenticated" error.

------------------------------------------------------
Invoking login on integrity.SessionManager:Integrity.SessionMgr session "SessionID"
Arg userName: "DOMAIN\Username"
Arg sessionId: "Session ID"
Arg locale: "en_US"
------------------------------------------------------
[2011-11-02 08:42:01:123 'Activation.trace' 3388 DEBUG] [activationValidator, 1094] Throw vim.fault.NotAuthenticated
Result:
(vim.fault.NotAuthenticated) {
dynamicType = ,
faultCause = (vmodl.MethodFault) null,
object = 'vim.Folder:group-d1',
privilegeId = "Sessions.ValidateSession",
msg = "The session is not authenticated.",
}
[2011-11-02 08:42:08:699 'JobDispatcher' 1852 DEBUG] [JobDispatcher, 391] The number of tasks: 0



The only one change which occurred since my last logon was the time change from Summer to Winter...:) 



To solve this issue you just need to restart the VUM service:

And re-enable the vCenter Plug-in: