Tagging along on another old post here, I am trying to monitor if a mapped drive is present or not. I am using dirscan, but it will not recognize the "Z drive". I can enter the full mapp (\\yadda\yadda) and it will see that, but that will not alert on the mapped drive disconnecting. Any ideas?
I believe in WIndows network drive mappings are session-specific. So the dirscan probe will work fine with the Z: drive, but you have to somehow map that drive in the session in which the probe runs. If you do that, it may not always accurately reflect the status of the drive mapping in another session.
Similarly, if you and I are both logged in to a server, you can map the Z: drive to \\server1\share1, and I can map the Z: drive to \\server2\share2. The mappings are session specific and to not affect each other. Even if we both map the Z: drive to the same share, yours might get disconnected for some reason while mine still works.
So it seems like monitoring a drive mapping would not make sense because it is tied to a specific session rather than the entire system. Am I missing something here?
Unfortunately one of the programs in play bases its distribution to a mapped drive. So we are looking for the existence of that Z drive.
Not sure if this is a option but you can mount the windows drive to a linux host and it will show up as just a mount point. No session issues
I understand the reason you would want to check for a specific drive mapping, but I am saying that you probably cannot do that from Nimsoft because each drive mapping is tied to a session rather than global. I think the most likely way to achieve the desired result would be to find a way to have the application log an error if the drive is not connected. Then you could use the logmon or ntevl probe to pick up the error. Or if you can get the application to lauch a script in some fashion, you could maybe do the check in a script. If you cannot get the application to report errors or launch scripts, I am doubful there is a way to check the drive mapping the application is using.
I may be wrong about this, but the trouble you have had so far is consistent with my understanding about how drive mappings work. I hope I am wrong and that you find a way to do what you need.
Keith is absolutely right, you cannot do that with NMS, mapings are tied to a session. Therefore your application which has drive Z: mapped can be broken, but NMS can find your drive.
You have to build mechanisms within your Application to "send" you something or do some "heartbeat" to the Filesystem, or dirscan if some fileage changes.
Retrieving data ...