Sorry, I hadn't understood that what you're after is explicit naming and VLAN assignment per VM and not just VLAN assignment per pool. This isn't really a scenario that the product is designed for but you can get there by setting up a new pool in the UI with a list of VM names in advance (making sure you don't enable provisioning up front) and then configure the pool's vlan setting using the cmdlet before enabling provisioning to allow the VMs to be created, but that isn't something that's really scalable from a management perspective. This is the "Specify names manually" setting in the "Provisioning Settings::Virtual Machine Naming" section.
↧