Okay...I'd like to say 'thank you' to the two posters who responded. You guys both helped out. It turned out to be relatively painless, but there were a couple of things I ran into
First of all, after renaming the cluster, all the VDI desktops continued running fine, except for one pool of linked clones. Since the cluster name had changed, VMview manager "lost" all settings related to the cluster, resource pool, and storage location for that pool of VDI desktops. I had to put the information back in to point to the same locations on the new cluster.
Secondly, regarding migrating VDI pools from one cluster to another, it was dead simple for non-linked clones, just used vmotion to move them and I was done. The linked clones were a bit different. I had to put in the cluster, resource pool, and storage location in the pool settings for VMview to know where to create new machines, but it left the existing machines where they were. I tried the "rebalance" thing, but it said it was going to revert them back to the base image, and I didn't want to do that. What I ended up doing, was shutting them down, migrating them to the new cluster, and powering them back on. They showed right back up in the view manager console.
If I run into any probelms tomorrow when the users come back in and start reconnecting, I'll post back. However, I tested connecting on my own and didn't have any problems. I don't expect any users to notice that anything is different.
Thanks again for the help.
Jeff
