- of

Deployment planning. Don't do a "big-bang" deployment. Target particular areas first in order to gain understanding on how to support the new environment.
Evaluate thin clients. There are many to choose from, and the more moving parts (fans, spinning hard-disk, etc.), the higher the failure rate. Keep in mind the software footprint on the device. If you have a full operating system, expect to keep the infrastructure around to patch it.
Operationalize your processes. Don't expect processes to stay the same. Your processes for on-boarding and off-boarding will change. Don't forget to train your help desk on troubleshooting a virtual desktop.
Prepare desktop technicians. Their job will change, and troubleshooting the desktop will require them to log in to a server farm with multiple desktops on them. They will have to know how to use virtualization software.
Admin separation. Keep the management of the server infrastructure separate from the management of the virtual desktops. But both teams will have to work together.
Server infrastructure. The virtual desktops will be running on a server farm, and this farm needs to be HA enabled. If a single hard drive goes out on a desktop, one desktop will go down. If one goes down in the virtual world, it could take out a number of desktops.
Marketing plan. Develop a marketing plan to sell virtual technology top users.
Corporate security. Since the desktops are all running within the data center, you need to be determine policy around what types of devices can be attached to the USB ports on the thin clients. There are a number of security choices you'll need to build into the solution. Having them in up front will minimize rework later.
Multi-media. Thin clients aren't there yet with multi-media. It's best to leave high-end users with their desktops for this application.
Work-from-home. There are design considerations that can be made up front that make enablement of the virtual desktop through the Internet easier later on.