IGEL and Lakeside Systrack

Obviously I’ve been in a new role at Lakeside so I’ve been living/breathing/travelling/living that, as well as more citrix environments *cough cough* – but that doesn’t really matter if I’m honest, as systrack works equally well with both. Actually, it works brilliantly with everything you can throw it at. I’m still amazed at the pain points that systrack could have fixed for me over the past 5 years and aside from new customers I’m dealing with, I’m also seeing some familiar faces from the past that I know can make use of it!

This post is to show that IGEL, as a partner, has jointly developed a solution to monitor their IGEL OS with systrack – now, as anyone in EUC who has used thin clients or a thin OS will know, they’re a little black box unless you start digging into logs, which may not actually make much sense! Now you can use the analytics to show what’s going on, in conjunction with whatever VDI solution you’re always monitoring.

I know of projects using various zero/thin clients that still complain about latency, performance issues etc and they STILL have no monitoring or any insight whatsoever and the technical skills of the people on the ground are low, to to say the least!

IGEL and Lakeside

Troubleshooting non responsive VMs

Sorry for the gap in posting…well…anything… New role has kept me very busy!

Most of us will have our own little tips and tricks on troubleshooting, but recently I had a customer who had a machine hanging, that looked suspiciously like VMware Tools was causing an issue, but they had no idea how to troubleshoot. I’d suggested various options, including simply getting the logs, checking ESXi services and so on and it wasn’t anything they’d had to do before, so I really needed something quick and fully features to suggest to them. There’s a great VMware KB which uses the process of:

Validate the scope – find out the scope of the problem and accurately define what the symptoms are (no point in just having someone screaming “It’s crashing, IT’S CRASHING!”

Identify the cause – so many possibilities! Storage, services crashing, resource contention, a task on the VM…

Action Plan – Take action to remediate the issue – once the cause has been established, focus on what is causing the issue and define a plan to resolve it.

https://kb.vmware.com/s/article/1007819