I think you've got this a little sideways.  The Isilon cluster is setup for Authentication via Active Directory.  Active Directory is configured to authenticate the client either via Kerberos or NTLM (v1 or v2).  With this security update MS15-027 applied, depending on how your clients authenticate to AD, they are unable to properly authenticate to the Isilon cluster.  So, it's not a change or configuration you need to check on the cluster, it's the allowed authentication in AD.  In our case, we mandate Kerberos only, but allow some clients to fallback to NTLM, as some are on networks that cannot reach timeservers, and others are on remote networks and have clock skew that prevent Kerberos (scientific data collection instruments).  These clients are the ones we have to remediate, as they cannot reach the cluster to access user home directories at logon.  Other clients that use Kerberos are not affected.  Let us know if that helps!  Karl
Community,  based on the resent advisory that went out this week [URL] I am trying to figure out how to find out how the server is configured for authentication?   Where do I find how the server is configured for authentication and once I am there how do I tell which configuration it is?  I navigated to Access Management - Active Directory - Viewed the details of the domain, but I am not seeing anything about authentication method.  I am running OneFS 7.1.0.5   Thank you,    . 
Isilon - How is authentication configured on the cluster?