Windows does not track drive mappings for auditing out of the box. To audit drive mappings you will need to do the following steps:
- Turn on Object Access Auditing via Group Policy on the system(s) in questionYou will need to perform the following steps on each system that you want to track the drive mappings
- Open the registry and drill down to HKEY_CURRENT_USERNetwork
- Right click on Network and choose Permissions (if you click on the plus sign you will see each of your mapped drive listed)
- Click on the Advanced button
- Click on the Auditing tab then click on the Add button
- In the Select User or Group box type in Everyone
- This will open the Auditing dialog box
- Select the settings that you want to audit for; stay away from the Full Control option and Read Control. I recommend the following settings: Create Subkey, Create Link and Delete.
Windows will now generate event ids 560, 567 and 564 when the drive mappings are added or deleted. 564 will be generated when a mapping is deleted, 567 will be created when a mapping is deleted or added and 560 will be generated both times as well. Event ID’s 567 and 564 will not give you the full information that you are looking for, they will tell you what was done to the mappings but not WHICH mapping. To determine which mapping you will need,the Handle ID code that will be found in the event description on the 564/567 events. The Handle ID will allow you to track back to the 560 event which will give you the mapping that is being added/deleted. Event ID 567 will only be generated on Windows XP or Windows 2003 systems, Windows 2000 will not generate 567.