Excellent! Glad to hear it.
But I'm a big idiot, and edited my original post with what now turns out to have been a wrong answer, so I have to make amends in case anybody else runs into the same problem. So, to recap what I had said earlier, this sometimes happens when View is trying to protect itself from creating multiple VMs with the same name. What I had originally suggested was disabling provisioning on the pool, waiting a few minutes and then re-enabling provisioning so the pool would use the next available number. It turns out that worked, which is great. My edited post can now be disregarded. I'm really sorry for the confusion. Lesson learned.
Dave
