There were a couple.
A big issue came up with user change. Not many users like to change their day-to-day activities.
There was also the major issue of thin clients versus thick clients. Installing thin clients is ideal, but, you end up with a lot of E-waste afterwards to dispose of, or re-use, or store.
Another challenge was network performance. Many users connecting to our VM infrastructure needed to be taken in to account. Switching, routing, and bandwidth management were a must.
Another challenge was memory management on the VM infrastructure side. Power users should be put on to a host with more memory than the other users.
All good things to look at when going with VDI, or any virtual desktop implementation.
Ryan
Last Wiki Answer Submitted: January 7, 2010 8:03 pm by Ryan86131,175 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
Honestly, we don’t really have a desktop virtualization strategy at this point. We have many ideas about the process, but we feel that Microsoft has been very sly in their dealings with virtualization, and when we were in a position to implement it widely, they were not sufficient for their virtualization and we did not want to move away from what we had built up.
Honestly, we don’t really have a desktop virtualization strategy at this point. We have many ideas about the process, but we feel that Microsoft has been very sly in their dealings with virtualization, and when we were in a position to implement it widely, they were not sufficient for their virtualization and we did not want to move away from what we had built up.
-Schmidtw