Any NFS server including Isilon simply trusts in the

numerical user and group ids provided by a client machine.

So the first design question will target the client side,

how are user/group credentials  set up on your NFS clients?

AD,  or more likely, separate LDAP or NIS?

Then, ask or decide how well AD and LDAP or NIS will be kept in sync,

in particular, will the AD maintain the UNIX groups information

completely, partially, or not at all.

Thus finally you will need to see which user/group mappings will be

left to be done the Isilon side, ideally only few!

The Isilon white papers on multiprotocol acces,

AIMA and (pretty recent one) multiprotocol security

really do come in handy;  but how to set up the NFS clients

is naturally a question outside of Isilon.

Feel free to post your considerations in greater detail.

You need to contact Microsoft for the same

Hope this will help  (NFS Authentication)

Also you can refer to points below..

Windows Server 2003 R2

When a UNIX user attempts to access a file shared by Server for NFS, Server for NFS uses either Active Directory Lookup or User Name Mapping to obtain the corresponding Windows user name of that UNIX user. When the Windows user name is obtained, Server for NFS then passes this information to either a domain controller or the security authority of the local server, depending on the type of account (domain or local):

• If the Windows user name is a domain account, then the domain controller authenticates the user with Kerberos extensions called Services-For-User (S4U).
  
  
• If the Windows user name is a local account, then the local security authority needs the assistance of Server for NFS Authentication. Without Server for NFS Authentication, the local security authority cannot authenticate the user and access will be denied.

To install Server for NFS Authentication

1. In Control Panel, click Add or Remove Programs. Then click Add/Remove Windows Components.
2. From the list of components, in the Windows Components Wizard dialog box, select Other Network File and Print Services, and click Details.
3. From the list of subcomponents, select Microsoft Services for NFS, and click Details again.
4. Select Server For NFS Authentication, and click OK.
5. Click OK again and then Next, and after the configuration of the new component has completed, click Finish.
6. 
   

> The option in the NFS Export map-lookup-uid can achieve what you are trying to do here.

That's an additional twist, mostly used with more that 16 supplementary groups per user.

Because NFS transmits only the first 16 groups.

You may still want to have the full information about groups right on the clients,

visible to users/apps. So the clients should be connected to either

AD (augmented for UNIX, details as posted by chughh) or LDAP or NIS.