Windows 10: Windows 2019 Services for NFS export not showing group name

Hi!We have IDMU and Uid and GUid are properly working and users use AD username to login to Linux using NIS and now we tested LDAPS as well which works fine.We have Services for NFS running on Win 2019 and I have enabled AD lookup.The AD domain functional level is Win 2003.When I mount the export from Linux and do a ls then I can only see username owernship and not group as you see its numeric no.dr-xrwxr-x 2 Tim 4294967294 64 Oct 7 12:52 Tim-createdI dont find any other option to set this. Is there any setting missing that its not showing the proper group name?Thanks.

:)

 

Office 2019

Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

Microsoft Office 2019 will only work on Windows 10

https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

Spoiler Office 2019
Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

• Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
• Office 2019 apps will be supported on:
  • Any supported Windows 10 SAC release
  • Windows 10 Enterprise LTSC 2018
  • The next LTSC release of Windows Server
• The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.

 

Configuring Windows Client for NFS

this question is about configuring Windows 10 Client for NFS. There are two parts to it, 1) map the export (drive), 2) set IM

Let's have NFS export (/media/NFS_share 192.168.0.*(rw,async)) already present and running properly, verified from another *nix boxes sharing same network range. Now, for mounting the export on Windows box we need Services for NFS installed and simply mount:

Command unfortunately results in:

Which is clearly incorrect:

So, 1) what is the issue with the mounting? 'Path not found' is somehow misleading message.

Next step would be setting identity mapping. While there are multiple ways, I chose local passwd and group files. But IdentityMapping log in ServicesForNFS-Client event log do not mention files at all, insisting on failed AD connection like there are no passwd/group files present in %SystemRoot%\system32\drivers\etc.
2) Are local files ment for Server only? Should AnonymousUid/Gid registry setting be used for client instead?

/edit: It would be worth of mentioning that opening \\192.168.0.2 in Windows explorer shows the share as \media\NFS_share but clicking it results in 'access denied' error, which seems to be more appropriate than err 53.

 

SERVICES FOR NFS

Old post but no one responded.

Services for NFS does not appear to be available on Windows 10 Pro, it does not show up under Windows Features. Many sites claim it is available on Windows 10 Enterprise, but I have not tried it.