It would be great to know more about what's going on in a multicast imaging sessions. Seeing 12/40 doesn't let you know which machines have/have not joined the session. When a multicast session is running slow (some run at 15MBbs others at 300KBps), it would be wonderful to find out which machine is causing the problem. Some way to tell who is in the session - IP address, MAC address, name, other? - would help tremendously when doing large rollouts of new images. Finding the slowpoke and somehow getting it out of the session (shutting it down, resetting the port, etc) would help get things done in a much more timely manner.

by: Carol Ann C. | over a year ago | Imaging