End-user performance management is very critical to making VDI a successful initiative. From an end-user standpoint, the user is looking for maximum efficiency and is not concerned about HOW that is achieved or WHAT technology is used. Just like how a mobile phone user does not care about whether his phone uses GSM or CDMA technology as long as it solves its intended purpose.
Frequently, business heads and teams resist VDI based on the fact that the familiar box near them has been taken away. We saw a lot of resistance when we rolled out VDI couple of years ago, but we found out a solution to prove and measure its performance. Eventually, we made these performance metrics available for all to see so that new users who challenge VDI have reliable data to refer to.
The approach we have adopted is a combination of technology and processes. Our monitoring architecture started from the end-user application metrics and moved up the layer to the actual VDI in the data center (contrary to the traditional approach of just looking at performance counters). With this approach we were able to easily relate the application performance at the end-user level to the dependent parameters of central infrastructure. We created business views which brought in all the dependent infrastructure together but still faced a challenge of simulating actual end-user experience.
We then developed application simulators which could schedule the application access at certain periods of the hour and feed the performance numbers (equivalent to typical use case scenarios and key strokes of the users). This was again interlinked to the various system thresholds like Network, WAN, SAN IO, Virtual platform and ended up with the final VDI session performance tracking. Any deviation in the threshold would highlight the possible causes which are being monitored 24/7 by the NOC team. With this we have been able to consistently achieve user satisfaction as well as start delivering application performance guarantees to our customers – and free business heads and end-users of their VDI-related fears in the process.
Visit www.anuntatech.com to know more about our latest End-User Computing offerings.
What’s a Rich Text element?
What’s a Rich Text element?
The rich text element allows yo
u to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
gkkjk jkaks ha k sjk dhak dhak dhakd ajkdk
Static and dynamic content editing
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
How to customize formatting for each rich text
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
- License investment: If you’ve spent thousands of dollars purchasing Microsoft Office licenses for your local PCs, you may not want to abandon that investment by switching to G Suite or Microsoft 365 instead, where you will need to pay new subscription fees.
- Cost: Putting aside the issue of prior investment in licensing, Web-based office software usually requires subscription fees that, in the long run, may exceed the total cost of ownership of on-premises alternatives.
- Learning curve: Your employees are probably experts in using on-premises applications like Microsoft Word. Moving them to Web-based alternatives will require teaching them new applications and new paradigms for storing and accessing data. You may not have time to teach all of your workers these new skills without disrupting business operations. Your IT team, too, may not be as well-equipped to support a new type of office platform.
- Security: When you use Web-based office platforms, it becomes harder to isolate sensitive data or choose to keep it offline. Files that your employees create in a Web-based office environment are typically stored on shared virtual drives that, depending on how you configure security settings, may allow users to access each others’ documents, or even expose data to anyone on the Internet.