Hmm. It's good to know that that option is available. I won't have pools with multiple VLANs, but still a good option for larger pools. The problem I have is having so many Pools with single VLANs attached to each. Organized, but lots of mistakes for a junior admin to make should they ever re-compose instead of refresh a pool. I like the idea of the automatic association of this network name being associated with a pool, but I'm a little concerned that if existing pools 'automagically' retain their network names, and new pools don't, I might be introducing a difficult to trace issue if full documentation isn't read. I'm gonna have to ponder this. It makes complete sense from an View Admin perpective, but might not from a Windows Admin who is running the View deployment. My PS can easily be edited and run on the required pools with a filtered variable, where as the View config file has to be populated and either modified or re-polled if new pools are created. lol - I guess it's a bit of a crap shoot anyway you look at it. What would really be nice is if View 5.2.x or higher simply puts a little drop down that lets you choose the network name / vlan - then my concerns are all gone!
I'll post back with what I end up going with - and my reasons for whatever I choose.
Thanks for the useful info! Love that VMware admins are happy to share their knowledge.