Ghost Solution Suite

Hi,

Could anyone please help me to resolve the following issue?:

I've upgraded Symantec Ghost 8.0 to Ghost Solution Suite 2.0.0 and then to 2.0.1 through live update functionality.

Now I'm getting 'Out-of-sequence consumer completion' on Windows 2000 Pro & Server clients that had worked before the upgrade was done and clients assigned tasks are unable to be initiated from within the clients. I.e. I click on a client assigned task and nothing happens.

Please note that this doesn't happen with old version of Ghost Client. I.e. it only starts when the client is upgraded to the latest version.

Windows 2003 clients are not noticed to have the same issue.

Please let me know what should be done in order to resolve the issue.

Thanks in advance,

Sergey

Hi James,

Please check your message box. I sent you a reply.

Thanks,
Sergey

Any progress on sorting this issue out?

Is anyone having similair issues as described above?
Does anyone have Windows 2000 GSS 2.0 ghost console clients successfully connected to Ghost Console and capable of initiating tasks from within themselves?

I'm just interested whether it's me doing something wrong or if it is a bug in GSS. If later then it should be fixed as Windows 2000 is claimed as supported OS in GSS.

I'm also having issues with Windows NT 4.0 Server and Workstations. The issue is that Ghos Console Client itnermittently fails to connect to Ghost Console. I have to restart ghost console client service in order to get things back to normal. It was not the case with Ghost 8.1.
Both NT 4 and Windows 2000 worked just fine.

Is anyone having similair issues with NT 4 clients as well?

Hi, I'm getting this same error on 2000 pro clients, does anyone know how to fix the issue? Running
GSS 11.0.1.1533.

Hi, I'm getting this same error on 2000 pro clients, does anyone know how to fix the issue? Running
GSS 11.0.1.1533.

Hi James, I didn't receive your message.

Hi,

 

We are seeing the same problem in our environment, the latest Ghost Client for Solution Suite does not seem to work correctly on Windows 2000 Server or Pro. Did anyone manage to resolve this problem?