Hosts provisioned with Auto Deploy usually do not have sufficient local storage to save system logs. You can specify a remote syslog server for those hosts by setting up a reference host, saving the host profile, and applying that host profile to other hosts as needed.

Best practice is to set up the syslog server on the reference host with the vSphere Client or the esxcli system syslog command and save the host profile. In some situations, setting up syslog from the Host Profiles interface is an alternative.

If you intend to use a remote syslog host, set up that host before you customize host profiles.


Use a vSphere Client to connect to the vCenter Server system.


Select the host and select View > Management > Host Profiles.


(Optional) Click Create Profile if no reference host exists in your environment.


Right-click the profile to modify and select Edit Host Profile.



ESXi 5.0, no previously configured syslog server


Right-click Advanced configuration option and select Add Profile.


Open the Advanced configuration option folder and scroll to the bottom.


Click Option Profile, click Edit, and select Configure a fixed option.


Specify as the option name and the name or IP address of the syslog server as the option value. You must specify a valid syslog server or you cannot save the host profile policy.

ESXi 5.1, or ESXi 5.0 with previously configured syslog server


Select Advanced configuration option.


Select to specify the host, and specify other settings that you want to use.


Click OK to save the host profile settings.

Write a rule that applies the host profile to all hosts that you want to provision with the settings that you specified in the reference host (see Assign a Host Profile to Hosts).

For hosts already provisioned with Auto Deploy, perform the compliance testing and repair operations to provision them with the new image profile. See Test and Repair Rule Compliance.

Turn on unprovisioned hosts to provision them with the new image profile.