Ghost Solution Suite

More troubles ahead !

I would like to understand WHY some of our clients are updated real time in the console (ie computer icon accurately reflects their on/off status), and some others have their computer icon permanently stay on eventhough they are off.

The console heartbeat has been set to 30 seconds, we're using bare Windows 10 installations + Dsagent, no firewall, no antivirus whatsoever, direct connection using an unmanaged 8ports switch !!!!

For crying out loud, what are the prerequisite for flawless connection ?

Thanks in advance,

Fabrice, Lycée Henri Poincaré

Hi Fabrice.

What kind of information are you talking about? Configuration request update on clients?

Regards,

Hello Fernando,

Generally speaking, some clients won't update or sporadically update their online/offline status, while some others (strictly identical cloned computers) are very snappy and stay always up to date in the console. The same lazy reporting computers won't perform simple powercycling tasks (such as wol, shutdown, restart)

Furthermore, when we issue a link status reset on console top root, some of our managed computers doesn't respawn in the console, eventhough they are powered on. Ping works both ways, so we ruled out network communication errors.

All our agents received the same production settings from the console (Direct IP connection instead of multicast + no communication encryption)

This is happening on bare machines, right now we are at a complete loss to understand this inconsistent behaviour.

Fabrice,

The issue you are experiencing could be related to encrypted sessions. This can typically cause random delays in communication. Follow the below KB and disable your encrypted sessions, I am willing to bet your connections become much more stable after this.

Dagent Connectivity Issues - Encrypted Sessions

https://support.symantec.com/en_US/article.TECH234276.html

Hello Brycen and thanks for your suggestion,

Unfortunately this can be ruled out too.

As stated in my previous post, we suspected the sessions encryption could be troublesome, so we choosed to disable it from day one.

Fabrice,

I would uncheck the encrypted sessions in the location shown in that article anyways.

What is the status of your firewall, GSS communicates over tcp PORT 402, this must be open?

Server Firewall?

Client Firewall?

Switch Firewall? if managed

Well it has always been unchecked and still is, sorry for my poor choice of words.

There's definitely no firewall enabled on clients and server side, nor on the switches. The very first communication works great after the DSagent installation, and then some of those computers reports randomly, while some others just report as expected.

We usually end up reinstalling DSagent on the computers where the communication is stuck, but it's not a permanent fix, communication troubles are back quickly after.

Mr Indrek Kaljusaar did a remote assistance session 1 week ago and suggested an OS reinstallation to solve possible WMI issues. That's what we did on our sandboxes.Still no go.

Fabrice,

What is your version of Ghost Solution Suite?

We are using GSS 3.1, MP3, version 607.

Update : We noticed that those computers stay ON in the console only when we shut them down using the power off switch.

If we remotely shut them down from the console, they effectively shutdown and their status is updated withing 30 seconds.

Right now, we are doing a comprehensive reassessment and try to figure the differences beetween reporting and non-reporting computers, but we are running out of ideas, so our next move will be a technical support request unless something new/good happen...

Fabrice,

I recommend creating a Support ticket so that a specialist can jump in and physically see your environment.