Ghost Solution Suite

Greetings,

I have been using Ghost Solution Suite since the release of GSS 3 and have one issue I have been unable to resolve.  I am able to boot any computer to network and connect just fine to the GSS console (Windows Server 2012 R2) to deploy images, configure the computer, etc.  However, once a computer has connected to the GSS console and been added to the database, I am then unable to reconnect fully to the console.  The computer will boot to PXE, connect, download the WinPE image and boot into WinPE. However, upon attempting to connect to the GSS console, I recieve the error "Failed to connect with DAgent for status updates" and then very quickly it will say "Connection Closed" and the computer will restart. I have a feeling there may be a port that needs to be opened, but I can't find it for the life of me.  Any assistance would be greatly appreciated. Thanks in advance.

You can find the Ports and Protocols used in Ghost Solution Suite 3.0 on Page 20 in "Installation and Upgrade guide for GSS 3.0"

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

Otherwise you can enable Logging in your Windows Firewall on GSS/Client and look which Ports were blocked.

Great, thanks for the reference.  However, after looking into it some more and talking with my boss, it seems that firewalls are not the issue since Windows Firewall is turned off for all campus computers (I'm at a college btw) and our corporate firewall only looks at connections from outside campus or that cross vlans.  Considering the server and the computers I am imaging are not only on the same vlan, but on the same switch, I don't think a firewall is the issue.  I'm really not sure where else to look at this time...
 

Check the drivers in your WinPE image. They need to be drivers that are appropriate to the version of WinPE that you are using - the version of operating system being deployed is irrelevant at this time.  You can check driver function by exiting to the WinPE command line and running ipconfig.  Also, have you turned off the default WinPE firewall ?

Hi Lam_Cake

Kinda feels like per design.

If the machine you are booting is known for the solution (Computer exists in console), and has no job assigned on it that need to run in WinPE, then the computer will be kicked out of the WinPe when it goes there.

basicly it is able to PXE boot but inside WinPE agent connects to server and servers sees that this client does not need to be there for anything, thus kick's the client out.

This is like a failsafe for client machines that where by mistake booted to PXE via end-user

You can try to delete the computer from console and then PXE boot it or you can try to create a simple run script task and assign it to run in the PXE WinPe

Best regards

Indrek

Thank you Indrek! I was not aware of this particular piece of information.  I did indeed test it by assigning a job with a simple script to the computer before PXE booting and the script ran fine.  Now that I know, that is very useful indeed! Thanks again!