Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Client seems to loose connection to the console goes to polling when

Created: 27 Jan 2013 | 18 comments

Greetings all,

I just installed Symantec Ghost Console on a windwos 8 pro box and am having great diffuculty in getting an image created.  This is what happens..

- The client is connected to the console just fine

- I start the image process and the client machine reflects the message and seems to be connected to the server without issue.

- After the reboot and the client is in preos the dos screen reflects the executed processes.

- The client seems to hang and start polling for the bound server at the 7th task

 

Has anyone had this issue and what is the fix.  I'm stuck and am trying to deliver images to test in a pilot tomorrow.

 

Thanks for any help you may be able to offer.

Robert

Comments 18 CommentsJump to latest comment

Nitin's picture

GSS have not be certified for Windows 8 operating system. From above thread it looks like you were able to install the client via Console but we have tested and we faced issue while installation of client itself. However you confirm following things :

1. Which vesion of GSS are you using? If you are using GSS 2.5.1 (build 2266) then you need to update it to latest patch (at least to patched binaries of 2269 since we have resolve new AHCI controller issue which creates the ghost binaires to work). To avail the patch, information is given on the sticky note on the top of this forum.
2. Is this machine is UEFI/UFI?

Regards,
Nitin

If you feel your issue has been addressed to, please use the "Mark as Solution" link for the relevant thread

EdT's picture

Re: Point 2 above - Ghost does not support UEFI bioses.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

R Walling's picture

I actually was not able to install the client from the GSS console.  I installed it directly from the GSS cd I created.  Ok I will update to the patch you mentioned above.  Thank you and I will keep you posted.

Robert

R Walling's picture

How do I identify the difference?  I'm not really sure how to check if a UEFI or UFI?

EdT's picture

The type of bios is a characteristic of the machine you are using. If in doubt, read the manual for the machine or contact the vendor.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

R Walling's picture

I'm using 2.5.1 (build 2266)  I'm sorry i'm new to using symantec forums, where exactly is the sticky note that you mentioned to be at the top of this forum?  I'm looking but for some reason must be missing it.

EdT's picture

Could it be this one?

https://www-secure.symantec.com/connect/forums/gho...

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

R Walling's picture

The system I'm creating the image from is an OptiPlex 390 and the system I have GSS installed on is a Inspiron 530s running windows 8.  

More information:

The client box (OptiPlex 390) seems to hang in the same spot every time..  It's on the 7 or 8th step reflected.  Seems to be stopping with sysprep engaged.  The information below is where it starts polling for the GSS server

This is what the comand line is reflecting:

Checking for sysprep Process ID.1288 \Device\Ramdisk .....ngctw32.exe....

Then I get the following repeated over and over (with fatal error note that shows up on the task bar):

9:38:17PM 127.0.0.1:1346 polling for the bound server WCI

9:38:17PM 127.0.0.1:1346 polling for the bound server WCI

9:38:17PM 127.0.0.1:1346 polling for the bound server WCI

9:38:17PM 127.0.0.1:1346 polling for the bound server WCI....

This continues until the task errors out on the GSS console.

 

 

 

EdT's picture

1. Do not use DOS with modern hardware unless you are conversant with how to change bios settings for SATA hardware to change it to IDE emulation, and your hard disks fall within the capacity that DOS can support.

2. WinPE is provided with Ghost Solution Suite - create your boot environment using WinPE and make sure you add the necessary drivers for your NIC and SATA chipsets. Since WinPE as provided in Ghost, is based on the Vista 32 bit kernel, you need to provide Vista 32 bit drivers to WinPE using Ghost Boot Wizard. The following tech note may help:

http://www.symantec.com/business/support/index?pag...

Also:

https://www-secure.symantec.com/connect/articles/d...

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

R Walling's picture

 

ok re the NIC and SATA drivers.  Do I place those in the sysprep config under the location where it indicates "other files"?  Do select those drivers there?

 

Thanks,,

still working on this and everyones suggestions are helping me waid through it.

 

R Walling's picture

The dos window is auto genterated when the client reboots to the windows pe environment.  

EdT's picture

It was not clear from your initial posting whether you were using the DOS client or WinPE (which displays a command line interface). However, as you have confirmed the use of WinPE, it remains to check with you that you have added any required drivers for NIC and SATA for your hardware, using Vista 32 bit drivers which are required by the version of WinPE you are using.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

EdT's picture

If you plan to use Multicasting once you have this running, make sure your switches have IGMP snooping enabled or you will find that your imaging will stop after a few minutes.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

R Walling's picture

Sorry to just be getting back with you. I have been tied up with another project.

To clarify I am using WinPE. What happens is that when the task begins the client machine reflects a message that a process is about to start on that machine and to close out of what the user is doing.
Then the machine reboots into WinPE. Once that happens I see a command window come open and that is where I see what is happening with the command line. It's automated and reflects the sysprep processes and when it gets to the process mentioned above that's when it starts polling for the bound server.

regarding the above reference to Vista, this is a Win 7 box with and OEM pre install. So I selected the default windows 7 sysprep config file.

EdT's picture

>regarding the above reference to Vista,

If you re-read my posting, you will see that the Vista drivers are required for WinPE and have nothing whatsoever to do with the operating system you are imaging. Please bear in mind that when WinPE boots, it becomes the operating system in charge of your hardware, and therefore any drivers you add to allow WinPE to use your hardware (eg NIC and SATA), need to be compatible with Vista, as WinPE V2 uses the Vista kernel.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

ICHCB's picture

OK so you are creating an image correct?  

This is with a task from the console correct?

The task has sysprep in it correct?

The polling for bound server does it list the correct IP that it is polling for?  

Polling for bound server with no other message is telling you it is trying to find the server.   If the only message is polling no responce from bound server then this tells you one of 2 things is happening.  

1 The client doesn't have an IP that is valid to talk to the network and find the server (This can be as Ed points out the result of not updateing the Vista 32bit drivers that the console is using for ghost tasks see http://www.symantec.com/docs/TECH110136 for adding drivers to the ghost driver data base)

2 The server is not able to be reached.  This can be because of a firewall or routing issue or DNS issues if it is polling by name not IP.    I have never tried to use ghost console on a win 8 system it may be that the built in firewall is blocking you.   Might try putting it on a supported OS or disableing all firewalls and see if you have better results.

I believe that at the polling for screen you can press ctrl + C and then will be at a command prompt.  From there do an ipconfig and see if you have a valid IP. 

If the IP isn't valid then do an IPCONFIG /Release and then IPCONFIG / Renew   if this gives an error no device in a state permissable this means that the client doesn't have the right NIC driver in use for PE see the KB above for updateing drivers. 

If you have a valid IP see if you can then ping the server. If you can consider the server's firewall or that ghost server isn't supported and may not be functional on windows 8.

 

If you find this post helpful please give it a thumbs up!
If you find that this solves your problem please mark it as the solution! 

EdT's picture

Just for the record, Win 8 is not a supported platform for Ghost Solution Suite. That does not mean it will not work, just that no one in Symantec has done any testing on Win 8 and therefore there is no record so far of any "tweaks" such as firewall settings that may be required.

Make sure that UAC is switched off on the Win 8 machine - this will remove some possible constraints to operation while you are exploring other possible issues.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Nitin's picture

Please find KB article link of Ghost Solution Suite 2.5.1 support matrix for Windows 8

http://www.symantec.com/business/support/index?pag...

Hope this helps.

Regards,
Nitin

If you feel your issue has been addressed to, please use the "Mark as Solution" link for the relevant thread