Skip to main content

Connect ESXi to Windows Based NFS

Many people are looking for a low cost solution for external storage for their free ESXi server. In this article, I will describe how to use a Windows machine and Windows Services for UNIX (WSFU) version 3.5 to create an NFS share that can be mounted on an ESXi host for storage of Virtual Machines, ISOs, or backups. There are a lot of articles like this out there but none of them worked as advertised for me so I decided to write my own.
Because I’m thinking about using my NFS storage for backup purposes my NFS share is called esxi-backup. Call your share what you will.
There are 6 main steps in the process:
  1. Installing WSFU
  2. Enable SSH on the ESXi Server
  3. Obtaining copies of the ESXi Server passwd and group files to the WSFU server
  4. Configuring WSFU for accepting ESXi connections
  5. Sharing the Windows folder to NFS clients
  6. Creating an ESXi Datastore to mount the Window NFS Share.


1. Install WSFU
  • To install WSFU you must first download it from Microsoft. 
  • Install WSFU on the desired machine
  • Select Custom Install
  • Add NFS + Server for NFS and Authentication tools for NFS + user name mapping
  • After installation, open the windows services control panel applet and verify the service ‘User Name Mapping’ is setup to startup automatically and that the services is started.


Windows Services Screen

2. Enable SSH on the ESXi Server
  • Please note that enabling SSH on ESXi is not supported on production servers. 

3. Copy the ESXi Server passwd and group files to Windows
  • Using a program like WinSCP or Veem fastSCP you need to navigate to the /etc directory on your ESXi server and copy passwd and group files to the WSFU server.
  • I copied the files to c:\SFU\esxi-files, that way I won’t forget what the file is for.


Windows Services Screen

4. Configure WSFU to accept connections from the ESXi Server.
  • On the Windows platform where WSFU was installed Click Start, Programs, Windows Services for UNIX, Services for UNIX Administration
  • Select User Name Mappings on the left hand side then configuration on the right had side.
    • Windows Services For Unix User Screen
  • Select the Password and Group files radio button
  • Then select browse for both the password and group files that you copied from the ESXi server
  • Select apply
  • Now Select Maps
  • Once the Maps window opens, select “Show User Maps”
  • Under Windows domain name, Select the windows PC where the users are located and then select List Windows Users, then select list Unix users
  • Select a local administrator user from the Windows Users on the left.
  • Under the Unix users Select the root account
  • Select Add
  • Then click apply (upper right)

Windows Services For Unix Maps Screen

5. Sharing the Windows folder for NFS compatibility
  • Right click the local folder you wish to share via NFS (mine is c:\VMware esxi backup)
  • Select NFS sharing
  • Type in the name for the share
  • Make sure allow anonymous access is NOT selected.
    • Windows NFS Sharing
  • Select permissions
  • Change type of access to “Read+Write” then select allow root access.
    • Windows NFS Sharing Permissions

6. Configure the ESXi Server to mount the Window NFS Share as VMFS
  • Open the VI client and select your ESXi Server
  • In the Configure tab choose Storage
  • Add storage, Network File System
  • In the Server Field enter the NFS server IP address or hostname.
  • In the Folder field enter the share name you created above (mine is esxi-backup)
  • I used esxi-backup for the Datastore name.


VI Add NFS
6a. Alternate NFS Configuration
This is an advanced configuration that requires the NFS server is on a separate IP network. I would only suggest this is you know what a separate subnet is and have one configured.
  • Open the VI client and select your ESXi Server
  • In the Configure tab choose Networking
  • Select Add networking
  • A new window will open, select VMKernel then select a vSwitch, then give the VMkernel an IP that is accessible via the NFS host.
  • Now open the storage option for this host
  • Click add storage, Network File System
  • In the Server Field enter the NFS server IP address or hostname.
  • In the Folder field enter the share name you created above (mine is esxi-backup)
  • I used esxi-backup for the Datastore name.
Labels:

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...
Read more

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...
Read more

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...
Read more