The users login in their session with their AD account, then the login script map the share drive with the documents (the n: drive for our case). The documents are hosted in a DFS file servers that you need at least to be a domain user to access the files. The File sight is installed in this DFS server. Before we had a cluster of 2 file servers with a different path to access the documents, and our File sight was working perfectly by logging every username actions. The new servers are in DFS and use a different path to access the files, instead of our old \\\server-name \share we have a path that looks like \\\domain-name \share, beside to change the new path in the login script, nothing has been changed for users, and i copied reinstalled File Sight I kept the same configuration I re-installed the File sigh on the new server. Any idea ?

The users login in their session with their AD account, then the login script map the share drive with the documents (the n: drive for our case). The documents are hosted in a DFS file servers that you need at least to be a domain user to access the files. The File sight is installed in this DFS server. Before we had a cluster of 2 file servers with a different path to access the documents, and our File sight was working perfectly by logging every username actions. The new servers are in DFS and use a different path to access the files, instead of our old \\\server-name\share \\\server-name \share we have a path that looks like \\\domain-name\share, \\\domain-name \share, beside to change the new path in the login script, nothing has been changed for users, and i copied the same configuration I re-installed the File sigh on the new server. Any idea ?

The users login in their session with their AD account, then the login script map the share drive with the documents (the n: drive for our case). The documents are hosted in a DFS file servers that you need at least to be a domain user to access the files. The File sight is installed in this DFS server. Before we had a cluster of 2 file servers with a different path to access the documents, and our File sight was working perfectly by logging every username actions. The new servers are in DFS and use a different path to access the files, instead of our old \\server_name\share \\\server-name\share we have a path that looks like \\domain_name\share, \\\domain-name\share, beside to change the new path in the login script, nothing has been changed for users, and i copied the same configuration I re-installed the File sigh on the new server. Any idea ?

The users login in their session with their AD account, then the login script map the share drive with the documents (the n: drive for our case). The documents are hosted in a DFS file servers that you need at least to be a domain user to access the files. The File sight is installed in this DFS server. Before we had a cluster of 2 file servers with a different path to access the documents, and our File sight was working perfectly by logging every username actions. The new servers are in DFS and use a different path to access the files, instead of our old \\server_name\share we have a path that looks like \\domain_name\share, beside to change the new path in the login script, nothing has been changed for users, and i copied the same configuration I re-installed the File sigh on the new server. Any idea ?