Recently I had to troubleshoot network performance issues for VMs running on Citrix XenServer 6.0.2. All VMs were running W2k8R2 and it seems that CIFS copy jobs where incredible slow. The network itself couldn’t be the problem as all VMs were connected to the same virtual network on only one XenServer.
Some days ago I ran into the problem that XenCenter was not connecting to my XenServer correctly. The initial connect seems to be fine, but it got stuck at “synchronizing with …”.
The other day I encountered a problem starting the XenServer PSSnapins.
The powershell error message told me “the Windows Powershell snap-in ‘XenServerPSSnapIn’ is not installed on this computer”
The explanation for this is quite easy: the XenServer powershell cmdlet’s are not(!
As some of you might know: I’m a big fan of unattended installations – they are reproducible, portable and document themselves in a machine readable format. Normally these installations are triggered by some software distribution system (ESD).
In today’s article about Splunk monitoring we want to monitor the version of the Splunk components which are connecting to Forwarder Management. The former name of Forwarder Management was Deployment Server – which I personally prefer more as it not only configures and manages your Forwarders, but all Splunk components including Indexers and Search Heads.