My general rule is to try NOT to boot the server whilst people are working on data contained on said server. What will take place
when the file system is yanked out from under an application is anyone's guess, and it will vary with OS / Application / Network
protocol. If you need to boot the server enough that this is a major problem, then I'd recommend that we look at why the server
needs to be re-booted so often.
jason martin
assistant idiot
frankfurt-short-bruza
www.fsb-ae.com/acadnetwork/acadnetworkfaq.htm
"balloyd66" wrote in message news:f08bcaf.-1@WebX.maYIadrTaRb...
> We are trying to implement a Win2K file server and one of our questions was: Does a drawing session open at a workstation remain
open when the server reboots? Well, sort of. The drawing remains open, but becomes read-only. This is NOT the answer we were hoping
to get! After all, we have a client who uses NT4.0 systems and their drawing sessions remain open and saveable at the workstations
when their server reboots. Anyway, does anybody have any suggestions to eliminate this unwanted behaviour?
>
