Identify and terminate "slow clients"
Created: 14 Aug 2009 | 2 comments
It might be useful if there were a way to identify the slow client(s) from the server side and manually remove them from the session, letting the rest of the clients blaze through quickly ?
Since the Ghostcast session can only go as fast as the slowest client(?), it's inconvenient to have an entire computer lab tied up because one machine has poor network connectivity, slow drives, etc. I'd gladly sacrifice 1-2 slow clients and rerun the imaging session if it meant that my 30+ other systems would be completed within a reasonable amount of time.
idea Filed Under:
Comments
I would love this...
For the Altiris Deployment Solution as well. Nothing anoys me more than a deployment of 100 computers taking hours because the system it chose as master has a connectivity/disk issue. It would also be nice if, part way through a deployment, a client can be dropped without negatively affecting the rest of the multicast. Adding to this, if the "master" is the problem, being able to terminate it and have a new computer elected as master would rock my world.
Sorry for the partial hijack!
Quote: "I know not what other much is else. But what other else is there?" - ***** (OP hidden as that was too awful! Lol)
I agree. Currently I run an
I agree. Currently I run an inventory refresh task on a sizeable bank of computers (of which, on a good day are all powered on, but most days there are usually 5 or so that are not). These five force the server to timeout after the default time limit I have set up, but the the other PCs complete their inventory successfully. Unfortunately, this take twenty minutes, when it should be significantly less.
Would you like to reply?
Login or Register to post your comment.