Get started Bring yourself up to speed with our introductory content.

How do you get to VMs following a vSphere migration to the cloud?

Pulling up stakes and putting your servers into the cloud doesn't mean you won't be able to access your virtual machines.

We are planning to move our whole vSphere and View server infrastructure to a vCloud. After a vSphere migration, what do we do with the View VMs if we no longer have vCenter? We could have users use Remote Desktop Protocol to get into the individual VMs, but we have a requirement to be able to share USB devices, which View does. Any ideas?

Moving your server infrastructure to vCloud means you will still have vCenter. When you implement vCloud Director, you will use vCenter to control the vSphere servers; vCloud Director is used to communicate in that environment to manage your virtual machines.

Click here to see the "vCloud Director Installation and Upgrade Guide" to learn more about the vCloud architecture.

After a vSphere migration, you will still have vCenter in your environment, but do you want to use one vCenter environment for both VMware View and vCloud Director? Probably not.

To keep both administration and troubleshooting easier, keep a separate VMware View environment with its own vCenter server and vSphere hosts and a separate vCloud environment also with its own vCenter and vSphere hosts.

This would split the computing resources in two. If your environment is a small -- let's say you have four ESXi servers – it might not be realistic to have two two-node clusters. Another option would be to invest in more servers, but this would open up licensing implications.

Dig Deeper on VMware basics

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.