Over the years, I’ve done quite a few wood working projects, like building a coffee table, end table, entertainment center, mudroom lockers, etc. Every project results in leftover pieces of wood. I dislike throwing perfectly good wood away, especially if it is large enough to make something.
Last year, my wife asked me if I could build her a large desk where she could help the kids with art projects, wrap presents and work on photo albums. Lo and behold, I was able to build the desk with 100% scrap wood. Of course, using scraps meant that this desk was built with at least 5 different types of wood (pine, birch, oak, masonite and medium density fiberboard).
You wouldn’t do something like this if you planned to stain and varnish the finished product as it would look a little Frankenstein-ish, but because I was painting the desk, I was able to reuse without impacting the end product. Even the paint was left over from other projects!
This desk cost me $0.00 instead of over $500. I was able to provide a great product without spending money! Being able to reuse resources is a great way to save money.
In just about everything, you can find ways to reduce costs, but there is a balance between saving money and delivering something that works well and looks good.
Look at XenApp and XenDesktop. Where can we reduce costs through reuse but still provide users with something that works and works well?
What about the Citrix Desktop Lock?
With desktop lock, we can effectively turn a traditional endpoint into a thin client. The user will no longer be able to interact with the local desktop, which is perfectly acceptable if the user will always connect to a virtual desktop. Why throw out a perfectly good piece of hardware if we can reuse it for a particular use case?
What about the different ways XenApp can encode and compress the data stream? Do we opt for the one that gives us the greatest server density in order to keep costs down? Or do we focus on user experience? As you saw in the Windows 7 and Windows 10 analysis blogs, there is a significant difference in server density between the different Citrix-based policies.
This leads us to our next XenApp best practice: