Found a weird issue yesterday that may or may not happen in anyone else's environment but I thought I would put the details here just in case. I found that a few of my Windows servers had local fixed disk drives showing up as network drives in SAM. This is a problem since our alerts only trigger on fixed disks. After poking around I noticed that all of the servers having this issue had a user logged in that had a mapped drive that was mapped to a share on that server. For example Server123 had a user logged in who had a drive mapped to \\Server123\RandomShare. This seems to confuse SAM for some reason as you can see from this screenshot.
Notice the difference in the name in the title and the info under Volume. I assume this has something to do with the fact that the VolumeName ends up the same on the local and mapped drives.
For my environment the fix was pretty easy since none of these drive mappings were actually necessary, I just removed the mappings, went to List Resources for each server in SAM and unmonitored/remonitored the drive having the issue. When SAM rescans the drive it comes back correctly.