Why do you need
During Windows logon NDM ensures that all connected network drives under its control and activated when they are connected regularly again in order to prevent deactivation.
When network resources are not (yet) available or if the link is to a network resource temporarily lost (eg when resuming a notebook from standby or when a wireless network connection was interrupted), NDM actively trying to connect the network drives.
Optionally, programs, open documents or mount TrueCrypt volumes have been successfully connected to a network drive. What about mapping network drives in Windows wrong?
Windows does not bother to ensure network drives get properly connected after logon which frequently to network drives that are visible in Windows Explorer, but not active. This leads to problems when used as a central network drive for storing data like documents or settings.
Applications that use these centrally stored files will complain or even fail to start, because the network location is reachable. Even if Windows manages to connect network drives properly at startup, the next problem, disable that these network drives get (ie no longer be accessed) after a certain waiting time.
This could result complaining applications again because they are not able to access their data on the hard disk. It might even result in data loss if applications do not anticipate on these scenarios and if the Windows write caching mechanism do produces "Windows Delayed Write Failed" messages.
Network Drive Manager main features:
Network Drive Manager Requirements:
Network Drive Manager Limitations:
What's new in Network Drive Manager: