How to set identity for Windows client for NFS without identity server?

For Windows 7 Client for NFS (packaged with Ultimate and Enterprise versions), you can set the AnonymousGid and AnonymousUid parameters in the registry of the client machine so that it connects as the Unix user you like.

Windows Registry Editor Version 5.00:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default]
"AnonymousGid"=dword:00000064
"AnonymousUid"=dword:000001f4

That's a tough one. Microsoft's NFS Client is designed for integrating Unix with a business network. It's not really for individual client machines. All the documentation suggests a mapping server of some kind is required.

You may have better luck with a third-party nfs client:

• nfsAxe
• DiskAccess
• Omni NFS

If you're willing to wait, the CITI research group and the University of Michigan are researching an open-source NFSv4.1 client for Windows. Ironically it is being funded by a grant from Microsoft.

On non-domain joined machines, you can setup Unix UID/GID to Windows Account mappings using the Lightweight Directory Services on Windows.

Step by step guide is available on http://technet.microsoft.com/en-us/library/dd764497(WS.10).aspx.

A scriptable solution to propagate the UNIX passwd/group files into an LDS instance is available at hhtp://support.microsoft.com/kb/973840

Both work very well when you have non-domain joined machines that need to use NFS protocol.