6.0.3

Prerequisites
Connect to vCenter Server with the vSphere Web Client.
Procedure
1 Browse to a host in the vSphere Web Client inventory, and select a host.
2 Click the Manage tab and click .
3 Under System, select Security  and click Edit.
4 Scroll to the service that you wish to change.
5 In the Service Details pane, select Start, Stop, or Restart for a one-time change to the host's status, or
select from the Startup Policy menu to change the status of the host across reboots.
n
Start automatically if any ports are open, and stop when all ports are closed: The default seing
for these services. If any port is open, the client aempts to contact the network resources for the
service. If some ports are open, but the port for a particular service is closed, the aempt fails. If
and when the applicable outgoing port is opened, the service begins completing its startup.
n
Start and stop with host: The service starts shortly after the host starts, and closes shortly before
the host shuts down. Much like Start automatically if any ports are open, and stop when all ports
are closed, this option means that the service regularly aempts to complete its tasks, such as
contacting the specied NTP server. If the port was closed but is subsequently opened, the client
begins completing its tasks shortly thereafter.
n
Start and stop manually: The host preserves the user-determined service seings, regardless of
whether ports are open or not. When a user starts the NTP service, that service is kept running as
long as the host is powered on. If the service is started and the host is powered o, the service is
stopped as part of the shutdown process, but as soon as the host is powered on, the service is
started again, preserving the user-determined state.
N These seings apply only to service seings that are congured through the vSphere Web Client
or to applications that are created with the vSphere Web Services SDK. Congurations made through
other means, such as from the ESXi Shell or with conguration les, are not aected by these seings.
Lockdown Mode
To increase the security of your ESXi hosts, you can put them in lockdown mode. In lockdown mode,
operations must be performed through vCenter Server by default.
Starting with vSphere 6.0, you can select normal lockdown mode or strict lockdown mode, which oer
dierent degrees of lockdown. vSphere 6.0 also introduces the Exception User list. Exception users do not
lose their privileges when the host enters lockdown mode. Use the Exception User list to add the accounts of
third-party solutions and external applications that need to access the host directly when the host is in
lockdown mode. See “Specify Lockdown Mode Exception Users,” on page 186.
Lockdown Mode in vSphere 6 (hp://link.brightcove.com/services/player/bcpid2296383276001?
bctid=ref:video_lockdown_mode_vsphere)
vSphere Security
180 VMware, Inc.