Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Ghost Client doesnt respond or load after ghosting/sysprep..

Updated: 21 May 2010 | 18 comments
sckoolz's picture
0 0 Votes
Login to vote
We are using Symantec Ghost Console 11.0.1.1533--which i believe is GSS2.0 but could be wrong.
  I just implemented this at a school district and I'm having issue with the clients not responding after a ghost session...for example.
I create the image (winxp) with the client installed and operational.  I ghost a lab of 30 machines that already had the client installed on them.  They are syspreped after ghosting and named exactly the same as before.  They show up in the console as disconnected and are unresponsive to remote commands in the console.  I end up having to uninstall the client then reinstall the client after the session.  What am I doing wrong?  I'm still trying to figure everything out and any help is greatly appreciated...
Thanks, 
discussion Filed Under:

Comments

Krish Jayaratne's picture
14
Oct
2007
0 Votes 0
Login to vote

Hi,

Could you check the ngctw32.log file in Ghost folder? Does it says 'polling for bound server' or go through a loop 'sending and acknowledging'?

Could you check if the Ghost client service is running in the client?

Krish

sckoolz's picture
17
Oct
2007
0 Votes 0
Login to vote

Hey there, thanks for the help...Im in that folder now looking at the txt and it hasn't done anything for a week...its the 17th today and last time it was updated was the 10th.  However in that document it was, in a 35 second timeline, disconnecting, sending status, acknowledged, tcp connecting, disconnecting, sending status then polling for bound.
Just logged on the machine next to me and checked that one as well with the same results.
 
As far as the second question...on the two pc's i dont even see a ghost service listed at all.
Krish Jayaratne's picture
17
Oct
2007
0 Votes 0
Login to vote

Hi,

If the Ghost service is not there, it explains why the log file is not updated and why the client not showing up in Console.

How did you install the Ghost client? By any chance was it a upgrade installation?

Could you give the command

ngctw32 -install


from the cmd window(change the directory to Ghost folder before giving the command) and starting the service would start the client and continue to work?

Krish

Message Edited by Krish Jayaratne on 10-18-2007 07:56 PM

sckoolz's picture
18
Oct
2007
0 Votes 0
Login to vote

Hello Krish,  I'll check on the cmd you told me to do later in the day when the classrooms aren' t in use.
 
However I installed the clients via a shared folder on the server through the .msi
It worked originally when i created the image bacause i used the console to create the image.
When I ghost the image down to the lab the client is unresponsive as previously noted.
Any work, so far, that has had to be done in those classrooms I have had to uninstall the client (even though its not running) and reinstall the client in order to have the console pick up the clients.
sckoolz's picture
18
Oct
2007
0 Votes 0
Login to vote

I needed to add that I have ghosted the entire district in this manner ( about 1073 pc's) and have only pockets of pc's that dont play fairly.  It seems to happen in these two labs every time though...
Krish Jayaratne's picture
18
Oct
2007
0 Votes 0
Login to vote

Hi,

Yes, in that case it is unlikely to be a generic issue. However, not having the client service is strange and certainly it would not communicate with Console.

Do you have any specific applications in these two labs? Do you use the same image for all the machines?

It's unlikely to be a hardware problem, but it's worth checking the client service again. Out of 30 machines, how many failed to connect to the Console?

Krish

sckoolz's picture
19
Oct
2007
0 Votes 0
Login to vote

Didnt find time to get over there yesterday.
 
As far as machines, they are high end workstation for autocad and corel draw and Adobe CS2.
If i uninstall the client and reinstall them they stay connected.  Something between creating the image and deploying on these machines is getting corrupt I imagine.  I have had this happen on other smaller clients here and there but this is everytime on these labs.
Krish Jayaratne's picture
22
Oct
2007
0 Votes 0
Login to vote

Hi,

It should not corrupt the files in the process.

I presume that you have a different image for these high end workstations. Could you get the ngctw32.log file when it happens next time? Even if there is no service, still it should have the old file. It may have some clues.

Krish

Message Edited by Krish Jayaratne on 10-23-2007 06:13 PM

sckoolz's picture
23
Oct
2007
0 Votes 0
Login to vote

From one of the machines in the lab...No service running or available...
 

----------------------------------------
C:\Program Files\Symantec\Ghost\ngctw32.exe  11.0.1.1533
2:19:36 PM Wednesday, October 10, 2007
Checking for Sysprep. Process id: 656, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SMSS.EXE
Checking for Sysprep. Process id: 708, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\CSRSS.EXE
Checking for Sysprep. Process id: 732, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\WINLOGON.EXE
Checking for Sysprep. Process id: 776, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SERVICES.EXE
Checking for Sysprep. Process id: 788, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\LSASS.EXE
Checking for Sysprep. Process id: 996, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 1064, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 1164, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 1244, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 1344, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 1452, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\COMMON FILES\SYMANTEC SHARED\CCSETMGR.EXE
Checking for Sysprep. Process id: 1480, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\COMMON FILES\SYMANTEC SHARED\CCEVTMGR.EXE
Checking for Sysprep. Process id: 1584, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\COMMON FILES\SYMANTEC SHARED\SPBBC\SPBBCSVC.EXE
Checking for Sysprep. Process id: 1652, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SPOOLSV.EXE
Checking for Sysprep. Process id: 444, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\AUTODESK\DATA MANAGEMENT SERVER 2008\SERVER\DISPATCH\CONNECTIVITY.WINDOWSSERVICE.JOBDISPATCH.EXE
Checking for Sysprep. Process id: 588, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\AUTODESK\DATA MANAGEMENT SERVER 2008\SERVER\WEBSERVER\CONNECTIVITY.EDMWS.SERVER.EXE
Checking for Sysprep. Process id: 640, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\COMMON FILES\AUTODESK SHARED\SERVICE\ADSKSCSRV.EXE
Checking for Sysprep. Process id: 684, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\WIDCOMM\BLUETOOTH SOFTWARE\BIN\BTWDINS.EXE
Checking for Sysprep. Process id: 840, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SYMANTEC ANTIVIRUS\DEFWATCH.EXE
Checking for Sysprep. Process id: 1016, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\VS7DEBUG\MDM.EXE
Checking for Sysprep. Process id: 1104, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\AUTODESK\VIZ2008\MENTALRAY\SATELLITE\RAYSAT_VIZ2008_32SERVER.EXE
Checking for Sysprep. Process id: 1144, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL$AUTODESKVAULT\BINN\SQLSERVR.EXE
Checking for Sysprep. Process id: 1412, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\NVSVC32.EXE
Checking for Sysprep. Process id: 1684, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SYMANTEC ANTIVIRUS\SAVROAM.EXE
Checking for Sysprep. Process id: 1904, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SMART TECHNOLOGIES INC\SMART BOARD SOFTWARE\SMARTBOARDSERVICE.EXE
Checking for Sysprep. Process id: 1972, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SMART TECHNOLOGIES INC\SMART BOARD SOFTWARE\WEBSERVER.EXE
Checking for Sysprep. Process id: 2008, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
Checking for Sysprep. Process id: 120, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SYMANTEC ANTIVIRUS\RTVSCAN.EXE
Checking for Sysprep. Process id: 2552, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\ALG.EXE
Checking for Sysprep. Process id: 880, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\EXPLORER.EXE
Checking for Sysprep. Process id: 496, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\CTFMON.EXE
Checking for Sysprep. Process id: 504, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\DLA\DLACTRLW.EXE
Checking for Sysprep. Process id: 1276, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\COMMON FILES\SYMANTEC SHARED\CCAPP.EXE
Checking for Sysprep. Process id: 1824, name: \DEVICE\HARDDISKVOLUME2\PROGRA~1\SYMANT~1\VPTRAY.EXE
Checking for Sysprep. Process id: 2856, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\WIDCOMM\BLUETOOTH SOFTWARE\BTTRAY.EXE
Checking for Sysprep. Process id: 1280, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\MSIEXEC.EXE
Checking for Sysprep. Process id: 3656, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SYMANTEC\GHOST\NGCTW32.EXE
Checking for Sysprep. Process id: 3436, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SYMANTEC\GHOST\NGTRAY.EXE
Checking for Sysprep. Process id: 3592, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SYMANTEC\GHOST\NGCTW32.EXE
#\Locate{ Name = mp\-dc3, Signature = (#[0x02 0xD9 0x16 0x6A 0xD3 0x28 0xF1 0x0D 0xB4 0x6A 0x88 0xE0 0x52 0x9C 0x3E 0x99 0x7E 0x0E 0xD9 0x79 0xF4 0x6E 0x66 0x9A 0x8D 0x49 0x25 0x21 0xD0 0x5A 0x89 0xB0 0x81 0x7C 0xEB 0x5A 0xE4 0x8F 0x3E 0x2D 0x90 0x75 0x80 0xA6 0x1D 0xA2 0xD8 0x6F 0x55 0xED 0x93 0x53 0xF9 0xFA 0xC8 0xCD 0x61 0xA2 0x92 0x1A 0xF4 0x53 0x40 0x71 0x80 0x94 0x2C 0xD1 0x85 0xF4 0x19 0x53 0xA2 0xF0 0xB3 0x25 0x8F 0xC0 0x08 0x4A 0x2F 0xD5 0x6D 0x9F 0xC1 0x5F 0x19 0x29 0x58 0x64 0xE0 0xAA 0xB5 0xFE 0x97 0x4E 0x18 0x45 0x09 0xE3 0x16 0xAF 0x70 0x34 0xA8 0x5F 0x88 0x98 0xB9 0xF0 0x73 0xDA 0x11 0x67 0x6E 0x8C 0x98 0x22 0x12 0x9B 0x75 0x29 0xDD 0x46 0xC4 0x8A 0x4E 0xC5] . #[0x02 0x1A 0x19 0xB4 0x73 0x8E 0xB0 0xD6 0xDF 0x43 0x12 0x32 0x8E 0x8E 0x4C 0x9A 0xEC 0x21 0x50 0x1F 0xEB 0xE5 0x8C 0xAF 0xB7 0x04 0x90 0x02 0xA4 0xD0 0x45 0xB8 0x3E 0x9D 0x37 0xC6 0x20 0x0B 0x84 0xD0 0xE9 0xC5 0xF3 0xC6 0x3E 0x4D 0xBF 0x86 0x98 0xF8 0x7E 0xCB 0x00 0x59 0xF4 0x4F 0x30 0x23 0xE2 0xC8 0xE7 0x4D 0x32 0x76 0xD6 0xA2 0x90 0x03 0x4A 0xB3 0x68 0xE2 0x14 0xFC 0xAA 0xBA 0x39 0x65 0x25 0xBF 0x02 0x85 0xC0 0x19 0x23 0x44 0xAB 0xCD 0x8E 0x96 0xD1 0x0B 0xF4 0xE5 0x88 0x59 0x3D 0x90 0xD7 0x82 0x18 0xCD 0x78 0x28 0xA4 0x5B 0x9E 0x92 0x66 0x1F 0xEC 0xBF 0xCF 0xC6 0xC3 0x77 0x33 0x0B 0x32 0x08 0xC7 0xD8 0x51 0x9C 0x44 0x05 0x12 0xE4]), Certificate = (#[0x05 0x18 0x67 0xB2 0xB4 0xCF 0xD5 0x9E 0x3D 0xA9 0xE7 0x96 0x78 0xD4 0x35 0xAE 0xF2 0x7F 0x38 0x3B 0x95 0xC3 0x28 0xC5 0x7C 0x43 0xAE 0x1B 0x45 0xC3 0xBB 0x26 0x31 0x83 0x29 0xEC 0x7C 0x91 0x7B 0x39 0x7D 0xDE 0xA8 0x44 0x9B 0xBD 0xD2 0x9B 0x51 0xCC 0x4B 0x3B 0xC4 0x95 0x88 0xC7 0xDF 0x8C 0x2E 0x23 0xD5 0x5C 0x13 0x5C 0xC3 0xD6 0xFE 0x71 0xA9 0x1A 0x65 0xDE 0xE1 0x5B 0xF2 0x99 0xE3 0xFA 0xA0 0xA5 0xFD 0x27 0x92 0x8C 0x05 0x04 0x6B 0xC2 0x6E 0x5E 0x45 0xF0 0x5B 0x80 0x69 0x38 0xD6 0xA0 0x84 0x8F 0x80 0x75 0x36 0xF3 0xC8 0xF7 0x9D 0x9A 0xB5 0x25 0x6B 0xA3 0x41 0xC2 0xB5 0x07 0x0C 0x3E 0x55 0x80 0x3F 0xF8 0x8D 0xAE 0x8C 0xFF 0x36 0xF2] . #[0x05 0xFA 0xFD 0x9E 0x6F 0x73 0x2E 0xE8 0xD6 0x96 0x04 0x62 0x79 0x0B 0x57 0xFC 0x7E 0xEC 0xD7 0x46 0xA6 0xB9 0xDA 0xFB 0xA5 0xB7 0x83 0x84 0xE0 0x7E 0xD7 0x44 0xC9 0xCB 0xD5 0x45 0x5F 0x1D 0x3D 0xEB 0x3C 0x77 0xE0 0x58 0xA9 0xFB 0x4D 0x75 0x2E 0x21 0x57 0x27 0xB8 0x96 0x09 0x61 0xB1 0xD7 0x5A 0x4E 0xC4 0x1D 0xBC 0xC0 0x48 0xA3 0x29 0x73 0x13 0xEF 0x57 0x68 0x4F 0x40 0x5F 0x54 0x06 0x1E 0xE0 0xB5 0x97 0xE6 0xDC 0x15 0xF4 0x14 0x9F 0x6D 0x82 0x35 0x32 0x61 0xE7 0x89 0xF4 0xCC 0x55 0xF2 0x5C 0x64 0x59 0x41 0xC9 0x87 0xC0 0xCD 0xF3 0x9F 0x5F 0x8D 0x5B 0x50 0x01 0x8B 0x96 0xE9 0x06 0x96 0x8F 0x49 0xC5 0xD9 0x00 0x3D 0x45 0xD5 0x60 0xBC]), Response = #[0x64 0x75 0xC0 0xA4 0xC6 0xD8 0x56 0xAD], Public = #[0x11 0xF9 0xC2 0x10 0x5F 0xFA 0x3D 0xFB 0x0B 0xEB 0xC3 0x70 0x71 0x71 0x04 0xC9 0xE7 0x50 0x1E 0xAC 0x31 0xA2 0x0F 0x8B 0x6E 0xDD 0x42 0xA2 0xF6 0x1F 0xC7 0xA7 0x12 0x26 0xC9 0xF8 0x7C 0x93 0xC3 0x76 0x8A 0xC3 0x59 0x42 0x42 0x5A 0x6A 0x54 0x4F 0x96 0xD3 0x5A 0xEC 0xD6 0x8C 0x9E 0x81 0x45 0xD4 0xFE 0x4D 0x31 0xDB 0xC4 0x50 0xA6 0xB6 0xC8 0x0E 0xD8 0x4F 0xD4 0xDB 0x45 0x70 0x6C 0xAA 0x8F 0x54 0x6F 0xE2 0x17 0x90 0xD9 0x43 0x9A 0x66 0xAE 0xB8 0x68 0x3F 0xDC 0x91 0x5A 0x15 0x99 0xE0 0x3E 0x29 0x13 0x91 0x04 0x7F 0xAC 0x9E 0x66 0x41 0x78 0xBA 0xBF 0x84 0x1C 0x65 0x85 0x71 0x89 0xB8 0xB2 0x5F 0x2B 0x11 0xD3 0xD8 0xED 0xBC 0x6B 0xD7 0x8E], IPADDRESS = 169413313, Product = Ghost, Host = mp\-dc3, Address = 1347, Component = Config_Server, Generator = #[0x12 0x80 0x1E 0x2C 0x45 0x21 0x3A 0xF0 0x53 0x66 0x3C 0x64 0x66 0xB5 0xEE 0x70 0xA7 0x0E 0x78 0xD1 0x99 0x07 0xA5 0xD3 0x69 0x03 0xC5 0x51 0x56 0x76 0xBB 0x84 0x31 0xF8 0xDC 0x6F 0x96 0x02 0x53 0x4D 0x9C 0xB4 0x12 0x53 0xA4 0x0B 0xBC 0x7E 0x1C 0x57 0xE7 0xF7 0x4A 0x4B 0x08 0xC6 0x99 0xCB 0xD4 0xC4 0x8D 0x35 0x0D 0xE8 0x3C 0xCF 0x7B 0x81 0xF4 0x27 0xF3 0x3A 0x3F 0x03 0x59 0x6E 0xEA 0x2B 0xAE 0x1C 0x57 0x2B 0x48 0x45 0x27 0x81 0x41 0xCF 0xDA 0x49 0xE0 0xE0 0x51 0x2A 0x6D 0x34 0xD4 0x75 0xA6 0x7F 0xB0 0xEE 0x70 0x75 0xE2 0x07 0x2A 0x79 0x17 0xE1 0x97 0xF8 0xA1 0x1E 0xEB 0x6A 0x77 0xF7 0x2F 0x1E 0xB4 0x2B 0x2B 0xF7 0x40 0x6C 0xF1 0x6D], Challenge = #[0xE7 0x0F 0xEA 0x11 0x5F 0xAD 0x96 0xFD], Modulus = #[0x19 0x44 0x46 0x91 0x38 0x87 0x83 0x50 0x24 0xD9 0x92 0xAE 0x0E 0xF7 0x16 0x37 0xF0 0xF7 0xAD 0xDD 0x0E 0xD3 0x9F 0x8C 0xB5 0xCE 0x84 0x79 0xB8 0xE0 0x17 0x05 0x09 0x29 0x7D 0x38 0x32 0xD5 0x62 0xA1 0xBD 0x9A 0xE4 0x8E 0x31 0x4A 0xEA 0xB9 0xAD 0xD3 0x65 0xD9 0xE1 0x10 0xD7 0x9F 0x3F 0xDC 0x52 0xB8 0xB5 0x00 0x83 0xAF 0xC1 0xB0 0xA7 0x58 0xAD 0xAB 0x0A 0x4A 0xA3 0xBE 0xCE 0x57 0x67 0xBC 0x91 0x9D 0x3B 0xE8 0xC1 0x8C 0x77 0xE1 0x77 0x0D 0x8A 0xD3 0x30 0x86 0x0E 0x85 0x51 0x96 0xFF 0x84 0x6B 0x01 0xF1 0x95 0x72 0x4C 0xAA 0xC9 0x75 0x0A 0xBA 0x45 0x66 0x51 0x86 0x40 0x16 0x3B 0x97 0x38 0x51 0xE8 0xD3 0x58 0x82 0x71 0xB0 0xE2 0xE7 0xC3] }
2:19:37 PM 10.25.10.193:1346 sending status to  10.2.2.7:1347
2:19:37 PM 10.25.10.193:1346 acknowledged by    10.2.2.7:1347
2:19:37 PM 10.25.10.193:1346 TCP connecting to  10.2.2.7:1347
Received message #\HasGhostBootPartition{ }
Received message #\WarnShutdown{ Shutdown = 1, Timeout = 1, Platform = DOS, Cancel = 0 }
2:19:37 PM 10.25.10.193:1346 disconnecting from 10.2.2.7:1347
2:19:57 PM 10.25.10.193:1346 sending status to  10.2.2.7:1347
2:19:57 PM 10.25.10.193:1346 acknowledged by    10.2.2.7:1347
2:19:57 PM 10.25.10.193:1346 TCP connecting to  10.2.2.7:1347
Received message #\WarnShutdown{ Shutdown = 1, Timeout = 1, Platform = DOS, Cancel = 0 }
Received message #\DoesClientFileExist{ Name = "GHCONFIG.EXE" }
Received message #\DoesClientFileExist{ Name = "GHSTWALK.EXE" }
Received message #\Open{ Name = "GHSTWALK.EXE", What = File, Mode = Write }
Received message #\DoesClientFileExist{ Name = "GHOST.EXE" }
Received message #\Open{ Name = "GHOST.EXE", What = File, Mode = Write }
Received message #\GetNetworkDriverCRC{ Name = "incoming\\dos" }
Received message #\DeleteClientDirectory{ Name = "incoming\\dos" }
Received message #\GetNetworkDriverCRC{ Name = "incoming\\dos" }
Received message #\Open{ Name = "incoming\\dos\\IBMDOS.COM", What = File, Mode = Write }
Received message #\Open{ Name = "incoming\\dos\\IBMBIO.COM", What = File, Mode = Write }
Received message #\Open{ Name = "incoming\\dos\\command.com", What = File, Mode = Write }
Received message #\Open{ Name = "incoming\\dos\\bootsect.dat", What = File, Mode = Write }
Received message #\Open{ Name = "incoming\\dos\\bootsect-floppy.dat", What = File, Mode = Write }
Received message #\GetNetworkDriverCRC{ Name = "incoming\\template" }
Received message #\DeleteClientDirectory{ Name = "incoming\\template" }
Received message #\GetNetworkDriverCRC{ Name = "incoming\\template" }
Received message #\Open{ Name = "incoming\\template\\protocol.ini", What = File, Mode = Write }
Received message #\Open{ Name = "incoming\\template\\mcassist.cfg", What = File, Mode = Write }
Received message #\Open{ Name = "incoming\\template\\B57.dos", What = File, Mode = Write }
Received message #\UpdateProtocolIni{ Name = "incoming\\template/protocol.ini", ServerConnectionDeviceId = "{0AD2722F-3D11-4A23-924C-1F2D94B45FB0}" }
Received message #\QueryAttributes{ }
Received message #\Open{ Name = "%systemdrive%\\sysprep\\WindowsXP-KB887816-x86-enu.exe", What = File, Mode = Write }
Received message #\Open{ Name = "%systemdrive%\\sysprep\\sysprep.txt", What = File, Mode = Write }
Received message #\Open{ Name = "%systemdrive%\\sysprep\\sysprep.inf", What = File, Mode = Write }
Received message #\Open{ Name = "%systemdrive%\\sysprep\\sysprep.exe", What = File, Mode = Write }
Received message #\Open{ Name = "%systemdrive%\\sysprep\\setupmgr.exe", What = File, Mode = Write }
Received message #\Open{ Name = "%systemdrive%\\sysprep\\setupcl.exe", What = File, Mode = Write }
Received message #\Open{ Name = "%systemdrive%\\Sysprep\\sysprep.inf", What = File, Mode = Write }
Received message #\SetGhostBoot{ VirtualPartitionSize = 15 }
Received message #\Command{ Name = "%systemdrive%\\Sysprep\\sysprep.exe -reboot  -mini  -quiet  -reseal " }
2:20:04 PM 10.25.10.193:1346 disconnecting from 10.2.2.7:1347
2:20:17 PM 10.25.10.193:1346 sending status to  10.2.2.7:1347
2:20:17 PM 10.25.10.193:1346 acknowledged by    10.2.2.7:1347
2:20:17 PM 10.25.10.193:1346 TCP connecting to  10.2.2.7:1347
2:20:17 PM 10.25.10.193:1346 disconnecting from 10.2.2.7:1347
2:20:37 PM 127.0.0.1:1346 sending status to  10.2.2.7:1347
2:20:49 PM 127.0.0.1:1346 polling for bound server mp-dc3
Krish Jayaratne's picture
23
Oct
2007
0 Votes 0
Login to vote

Hi,

The log file shows that client never started after the restore since the last lines indicate that it had run sysprep.

Instead of re-installing the client, If you run the commands I suggested before, does it work? In this way we can identify if it is just service not getting registered or some kind of a problem with installation.

Krish

sckoolz's picture
25
Oct
2007
0 Votes 0
Login to vote

I tested the Command that you told me to try.  It worked and they are showing up in the console.  What next?
Krish Jayaratne's picture
29
Oct
2007
0 Votes 0
Login to vote

Hi,

This indicates that the issue is not registering the service rather than a file corruption.

Did you do an upgrade or fresh installation of Ghost client in the source machine?

Krish

sckoolz's picture
30
Oct
2007
0 Votes 0
Login to vote

Hey Krish,
If I were to uninstall and then reinstall the client AFTER ghosting then the client would work fine, however defeats the purpose of having a managed network solution.
When the image was created the ghost client was working,  I pushed the image up to the server then multi'd down to the two labs, as the entire district.  When the lab machines came online after sysprep the clients never connected. This same method was used in over 1000 machines and we are only having issues with about 100 at the very most.  Now like I said in previous posts, If I had to do anything in those labs in order to get the client to work (before your cmd line fix) I would have to uninstall and reinstall the client in order for the system to connect with the server.  I dont think I should have to run a cmd line every time we ghost to get the solution to work, it should just work right?  or uninstall and reinstall everytime we ghost a few or more machines right?  I've asked around and dont seem to thing others have had similar experiences.
Krish Jayaratne's picture
30
Oct
2007
0 Votes 0
Login to vote

Hi 'sckoolz',

Certainly, this is not the expected behaviour and it is not a common situation either. I gave you the commands not as a workaround, but to understand the issue. For whatever reason, the service is not registered after restoration and sysprep.

It is difficult to think what the reason is. However, I believe it is in the source image.

When you restore this image, do the machines behave in this way all the time - 100% ?

In the source machine, did you do an upgrade or a fresh installation of Ghost client?

Krish

sckoolz's picture
31
Oct
2007
0 Votes 0
Login to vote

Sorry, I thought I answered that but reading back I certainly did not.
 
On the machine I used to create the image it was a fresh install, not an upgrade.
 
On those lab machines it happens 100% of the time.
 
I've remade the image multiple times and uninstalled and reinstalled client to fix any issues then reghosted lab and it still occurs.
jayrodau's picture
31
Oct
2007
0 Votes 0
Login to vote

Sounds like you need to add each machine there in your lab back to the Domain after you image them.
We have the same issue here, once we ghost a machine we have to go into computer properties and add it back to the domain. After a ghost push has been performed then it reboots. The machine is only part of the "workgroup".
Change "workgroup" to your prefered domain. hope this helps

sckoolz's picture
31
Oct
2007
0 Votes 0
Login to vote

Hey Jay, I hear ya but nope.
 
The machines are in the domain.  sysprep auto joins them.  The problem is not communication between the  machine and the servers it the communication of the ghost client and the ghost server..everything else works great.
If you have having the issue you say you are, then i suggest using sysprep to automate that process. 
This problem is only occuring on 1/8th of all of our machines using the same process.
Krish Jayaratne's picture
31
Oct
2007
0 Votes 0
Login to vote

Hi,

You mention uninstall and re-install. All the images you created with this machines had an uninstall too?

The reason is, we are aware of such a situation. When the service is deleted during uninstallation, if the service database is locked by any other product for some reason, system marks it for deletion at restart instead of deleting it. Some times, if you install it again, marked for deletion take effect at restart and the service is deleted. Could that happened in your case?

If it is a possibility, could you uninstall and restart the machine before installing Ghost client, when you try next time?

Krish