Multicast session takes to long to time out failed systems
I am looking for a way to change the configuration in ghost to change the timeout time on a multicast session where the entire session is limited by the failure of one bad hard drive. (When we are unaware of a failed hard drive) Is there a way to change the amount of time on one failed drive on a session of 30 computers to time out faster so the session can continue at a normal rate of speed? I have seen sessions when the timeout takes well over 10, to 20 minutes to finally proceed after the failed drive finally times out and fails. If I can time out such failures in say, 30 seconds, that would definitely boost productivity.
Any help or instructions where I can modify this configuration in ghost would be highly appreciated not only by me, but by our school district of over 10,000 computers. Thanks
Gene M. Tech Specialist I
(El Paso Independent School District Texas)