How To – Make a firewall rule persistent in ESXi 5.x This is a quick how

This is a quick how to make a firewall rule persistent even after reboots on ESXi 5.x,

· Find a shared Datastore or use a local one if on a standalone ESXi host, Create a firewall rule on an xml file and in this instance we have a vnc rule.


You will need a script that will call the file when the host is starting up, name it <> and this is the content of the script.

Copy both files (.xml and .sh) into your DataStore and change their permissions.

Startup script


· Edit the file /etc/rc.local.d/ and add the path to the script before the “return 0”


· Start the script for error verification if any using

This should apply the rule whenever your reboot your host.

Have Fun

How to create a custom firewall rule on ESXi

In this instance, we will have a VNC rule added to the firewall.

1- Verify if the firewall is active or not using  esxcli network firewall get

If the firewall is Active you will get the below

Enabled: true
Loaded: true

2- Create a copy of the file “/etc/vmware/firewall/service.xml”
cp /etc/vmware/firewall/service.xml /etc/VMware/firewall/service.xml-backup

3- modify the permission of the file service.xml:

chmod 644 /etc/vmware/firewall/service.xml
chmod +t /etc/vmware/firewall/service.xml

4- Edit the file and add the below at the end of the file


5- Once saved, apply the rule using the below as well as checking if the rule is functioning

esxcli network firewall refresh
esxcli network firewall ruleset list | grep VNC

Have Fun

an Internal error occurred in the vSphere client… VMware update Manager



Quickie post on how to correct the An Internal Error Occurred In The vSphere Client for  VUM Plugin.


I have searched the web and came across several cases simil to this one but my own is some kind of wired case. maybe installation issue.

let go.

Go to C:\Program Files (x86)\VMware\Infrastructure\Update Manager

Locate and open vci-integrity.xml and replace it with the FQDN of your vCenter




You do the same on the Extension.xml file where you put the FQDN of your vCenter instead of the IP Address



There will be one thing worth checking is the Firewall between the two machines, in my case, I’ve had to allow the ports on the windows built-in firewall to have this problem solved afterwards.

have fun

Syslog Configuration on All Hosts – PowerCLI

It comes to times when you will be looking at changing a setting on hosts at once avoiding the clicks, in my case I had to change a setting for around 150+ hosts on 4 datacenters from 4 vCenters and this will take a heck of a time.

This is a quick way you can change and point your ESXi hosts to a syslog server using PowerCli.

This will configure your Syslog Server IP address or hostname, Open the Outbound Ports and also restart your syslog services,

Double check your configuration through this


In case you wanted to go through this manually, these are the commands needed

To open your firewall :

To configure your Syslog entries

You will have to restart your syslog services .

Finally this command will show you the config state of your Host or hosts