Deployment Tasks, Templates and Unicast/Multicast bug.

I have discovered a very annoying and disruptive bug in SnapDeploy, and will try to explain it here to the best of my ability.

When I create a new deployment template, I always select the Unicast option for deployment. Then, I'll create a new deployment task to deploy to one or more machines and it works fine and deploys via Unicast as it should. HOWEVER, at a later time when I have a few more machines to deploy, and wish to use that same template but create a new deployment task, it will deploy via the default setting of Multicast.

This has happened several times and I've discovered this after the deployment begins because I start to get calls from users saying the printers are down (the printers and imaging take place on the same subnet). I can quickly resolve it by disconnecting our imaging switch from the network. I could see this being a much bigger problem for larger networks and in different scenarios.

I've always had trouble using the same deployment task for a different deployment altogether, maybe I'm doing something wrong. Has anyone else encountered this issue?