This seems to be a fairly common occurrence with datastores on non-local disks. I presume it is to do either with service startup order such that the VMware services startup before the NAS becomes available/connected.
If I was doing this, I'd add my own service using the wonderful Microsoft utility srvany.exe that lets you run any program, such as a script by specifying the scripting engine, e.g. cmd.exe ot wscript.exe, as the executable srvany launches. This would do whatever it needed in a script to bring the NAS to life, or wait until it was (although watch for service timeouts), and would be set to depend on some networking service to ensure it didn't come up too soon. I would then make the VMware services, particularly the host agent, depend on the srvany service.
Hopefully though someone with the same problem will have a simpler workaround for you.
Guy Leech
VMware vExpert 2009
---
If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.
