When working on processing office designs, many begin with the model VDI (personal). I tend to go for the model (Shared) RDS. There are many reasons, but mostly it's because
- Extensibility :. Most agree that a shared office environment achieves better scalability than personal desktop environments
- Storage: Because of the shared operating system, the impact on storage is mostly a non- problem
- safety: Although desktop can be fixed, I usually find that people do a better job securing jobs in the shared model
as I I said, I usually start with the XenApp model, but as we all know, one size does not fit all. There are occasions where the staff office model is needed. Whenever I say this, I get a lot of questions asking what to user needs XenApp can not provide. Here's a start:
- control Reboot: Can you imagine if you let users restart a XenApp server. Talk about a great way to check your colleagues
- administrator rights: I hate to say it, but some users need administrative rights. Doing this on a shared office will cause a lot of problems
- specialized equipment. Some users need powerful graphics cards and sound cards. It is often easier to do so in a personal model (VDI)
- Background: Many users want a picture of Homer Simpson on their screen. Silly, that can be done with shared or personal. This is not a valid requirement to go to a home office
Of course, I'll save the most common last ...
- Applications of 'user:. Certain users need to install their own applications. Doing this on a shared model is scary, but on a personal model makes a lot of sense.
What other fields you see are the needs of viable users who dictate the need for staff (VDI) office instead of using the (RDS) shared model
Daniel - Lead Architect
XenDesktop design Handbook
0 Komentar