Fileserver EventReader
Analysis of file server resources
Identify responsible persons (data owners) or unknown accesses (e.g. machines / service accounts)
File server migrations are actually not as complicated as they are often feared! However, thorough preparation and accurate planning are essential. This includes the preparation of the shares (sizes, dates, identification of orphan directories ...), the review of the current authorization situation and structural adjustments.
Two major migration issues are addressed with the file server EventReader:
- Can you be sure that systems (production systems, applications, service accounts) will not access the file server, which would go nowhere after the restructuring?
- Who are actually the data owners of the individual directories: The people who access the most know, in any case, with whom you have to negotiate about the structures.
The EventReader evaluates the Windows events
and provides the filtered information
to use a resource as an Excel file.
extracted information
Auditing policies that generate Windows Events are enabled on the unknown share.
These include:
- Who: Account
- From Where: Hostname
- When time
- On what: directory (optional: file)
Functionality
Auditing is activated for the shares to be evaluated. These are left to run for a desired period of time and after 4-8 weeks, the events are retrieved using the EventReader from aikux.
More details on how it works can be found here here…
Why not with Powershell
The evaluation of the events only takes a few minutes with the EventReader, even for large environments. Such evaluations cannot be implemented with Powershell for performance reasons. The filtering of the events is extremely ineffective with Powershell and would take days. This was also the reason for the development of the tool.
Use EventReader
If you want to use the EventReader, please contact us using the adjacent form. The EventReader can be used from Windows Server 2008 upwards and for EMC file servers.
