{"id":3008,"date":"2020-02-04T04:02:05","date_gmt":"2020-02-04T04:02:05","guid":{"rendered":"https:\/\/davidpapkin.net\/?p=3008"},"modified":"2020-02-04T04:02:05","modified_gmt":"2020-02-04T04:02:05","slug":"mount-nfs-share-server-2016-david-papkinh","status":"publish","type":"post","link":"https:\/\/davidpapkin.com\/?p=3008","title":{"rendered":"HowTo Mount NFS share Server 2016"},"content":{"rendered":"

This David Papkin post on NFS sharing is derived from RootUsers<\/a> post https:\/\/www.rootusers.com\/how-to-mount-an-nfs-share-in-windows-server-2016\/<\/a><\/p>\n

Here we\u2019re going to show you how to mount an NFS file share in Windows Server 2016 both temporarily and persistently so that it will automatically mount after a reboot.<\/p>\n

There are a couple of different ways this can be done, including mapping a network drive or adding a network location, which we\u2019ll discuss here.<\/p>\n

Our NFS Server:<\/strong>\u00a0In this example we already have an NFS server setup on a CentOS 7 Linux system which is available at 192.168.1.14 and we have exported the \/root\/nfs directory with NFS. See our\u00a0guide on creating an NFS server in Linux here<\/a>\u00a0if you need information on how to do this.<\/p>\n

Install NFS Client<\/h2>\n

Before we can mount any NFS shares on our Windows server, we must first install the NFS client feature. This can be done through the graphical user interface (GUI) using server manager, however that takes a lot longer so we\u2019ll use some PowerShell.<\/p>\n

First we\u2019ll use the Get-WindowsFeature cmdlet to search for available features that contain the string \u2018NFS*\u2019 in the Name field.<\/p>\n

PS C:\\> Get-WindowsFeature -Name NFS*<\/strong>\n<\/pre>\n
\"Get-WindowsFeature<\/a><\/p>\n
As we can see NFS-Client is available for install but not currently installed.<\/p>\n
Next we use the Install-WindowsFeature cmdlet to install the NFS-Client feature, as shown below.<\/p>\n
PS C:\\>  Install-WindowsFeature -Name NFS-Client<\/strong>\n<\/pre>\n
\"Install-WindowsFeature<\/a><\/p>\n
Once complete we should see that the installation has completed successfully, no reboot is required for this feature, we can begin using it straight away.<\/p>\n
Mount NFS Temporarily<\/h2>\n
We can use the mount command in command prompt to quickly mount our NFS share and confirm that it\u2019s working. Note that the mount command used here is in command prompt rather than PowerShell, using it in PowerShell will fail as it is a different command.<\/p>\n
C:\\Users\\Administrators> mount \\\\192.168.1.14\\root\\nfs X:<\/strong>\nX: is now successfully connected to \\\\192.168.1.14\\root\\nfs\n\nThe command completed successfully.\n<\/pre>\n
\"Command<\/a><\/p>\n
At this point we can browse to \u201cThis PC\u201d and we should see the NFS share mounted under Network Locations.<\/p>\n
There is an issue with this however, this mount is not persistent meaning that if we perform a restart of the Windows server it will not be there afterwards. Luckily there are a few ways we can permanently map to the NFS file share.<\/p>\n
Mount NFS Persistently<\/h2>\n
Most of the time we will want our NFS mount to survive a system reboot and mount automatically after boot so that we don\u2019t have to manually mount it every time.<\/p>\n
There are a couple of different ways that we can achieve this task:<\/p>\n