How to install ESX updates from the console

Steps:
1. Copy "update.zip" to the "/tmp" folder on ESX host (you can use WinSCP).
2. Enable ESX maintenance mode "vimsh -n -e /hostsvc/maintenance_mode_enter" from the console.
3. Install the update "esxupdate update --bundle=/tmp/update.zip --loglevel=INFO"
4. Exit from ESX maintenance mode "vimsh -n -e /hostsvc/maintenance_mode_exit"
5. Reboot host with "reboot" after the installation completes

Update: Full instruction for any versions "Quickest Way to Patch an ESX/ESXi Using the Command-line"
Update2: If you use esxupdate to install third-part package, you need to add --nosigcheck to disable module signature checking during the installation.

Reload Virtual Machine settings from vmx file in vSphere Client

If you have edited vmx file manually (or changed it in the another vSphere Client), you may need to refresh Virtual Machine settings in already opened Client window.

Method 1:

you can to re-add this virtual machine.

Method 2:

open server console and type the following:

vmware-vim-cmd vmsvc/getallvms |grep "Your Virtual Machine Name"
Note: use vim-cmd command to run in ESXi server.

It outputs next result:

16 Max Virtual Machine [datastore1] Max Virtual Machine/Max Virtual Machine.vmx winXPProGuest vmx-07

"16" is inventory ID that can be used to reload configuration:
vmware-vim-cmd vmsvc/reload 16

Note: use vim-cmd command to run in ESXi server.

Now you have virtual machine settings "up to date" in all your vSphere Clients.

All ESXi host config files in webAccessibleConfigFiles.xml

ESXi 4.1 server has interesting file '/etc/vmware/hostd/webAccessibleConfigFiles.xml' where is all configuration files are listed. You can find its names and paths there.

Actually it's list of all config files those are available with web access:
...

  <configfileinfo>
     <urireference>/host/vmware.lic</urireference>
     <path>/etc/vmware/vmware.lic</path>
     <displayname>vmware.lic</displayname>
     <mimetype>text/plain</mimetype>
     <method>GET</method>
     <method>HEAD</method>
     <method>PUT</method>
  </configfileinfo>
  <configfileinfo>
     <urireference>/host/vmware_config</urireference>
     <path>/etc/vmware/config</path>
     <displayname>vmware_config</displayname>
     <mimetype>text/plain</mimetype>
     <method>GET</method>
     <method>HEAD</method>
     <method>PUT</method>
  </configfileinfo>
  <configfileinfo>
     <urireference>/host/vmware_configrules</urireference>
     <path>/etc/vmware/configrules</path>
     <displayname>vmware_configrules</displayname>
     <mimetype>text/plain</mimetype>
     <method>GET</method>
     <method>HEAD</method>
     <method>PUT</method>
  </configfileinfo>

...

Configure persistent logging (syslog) on ESXi host

ESXi 4.1 maintains a log of activity in log files, using a syslog facility. The
following logs are available:
• hostd.log
• messages
• vpxa.log (only if the host has been joined to a VirtualCenter instance)

By default, the messages log on ESXi are stored only in the in-memory file system. The logs are lost upon reboot, and only 1 day’s worth of logs are stored.
According to VMware Security Hardening Guide you can configure persistent logging to a datastore and a dedicated records of server activity are available for that host always.

VMware kb has recommendations about how to make it possible. But manual changes in 07.logger file work only for current session. After restart all changes reverted (kb has note about this). David note in this thread explains this issue. But how to resolve it and make possible persistent logging? Well, yes, vSphere Client works perfect and you can change syslog settings there. But I need to change it from TSM.

I have tried to edit '/etc/syslog.conf' file and it works! Between vSphere Client stores its changes for syslog settings in this file also.
So you need to:
- set your path to log file with 'logfile=' parameter. ie

logfile=/vmfs/volumes/4d5abbeb-22518c58-5ddc-000c2954a30d/logging/messagesX

where '4d5abbeb-22518c58-5ddc-000c2954a30d' is your storeID. You can use datastore label also (like "datastore1") in this path. Be sure that all folders in this path exist.

- find existing syslogd process and restart it:
ps | grep syslog > PID of syslogd
kill -HUP $syslogPID (restart process with selected PID)

Check that syslogd logs in the new file. Keep in mind that it continues to log in original "messages" file also (/var/log/messages). New log file is rotated and old versions are compressed automatically.

Manage ESXi Lockdown Mode from DCUI

If your VMware ESXi 4.0 & 4.1 servers are joined in VMware vCenter Server infrastructure then you can enchance security for these hosts. Follow on VMware Security Hardening you need to enable Lockdown Mode to restrict root access (HCN02 requirement).

Lockdown mode forces all operations to be performed through vCenter Server (you can continue to use Direct Console User Interface aka DCUI to manage host).

VMware Security Hardening guide notes that lockdown mode can be enabled or disabled in two places:
• In the vSphere Client, when connected to the vCenter Server managing the host
• In the DCUI of the host

In ESXi 4.0:
To check if Lockdown mode is enabled, run the command:
vim-cmd -U dcui vimsvc/auth/admin_account_is_enabled

To disable Lockdown mode, run the command:
vim-cmd -U dcui vimsvc/auth/admin_account_enable

To enable Lockdown mode, run the command:
vim-cmd -U dcui vimsvc/auth/admin_account_disable

In ESXi 4.1:
To check if Lockdown mode is enabled, run the command:
vim-cmd -U dcui vimsvc/auth/lockdown_is_enabled

To disable Lockdown mode, run the command:
vim-cmd -U dcui vimsvc/auth/lockdown_mode_exit

To enable Lockdown mode, run the command:
vim-cmd -U dcui vimsvc/auth/lockdown_mode_enter

See VMware kb to more details