Ghost Solution Suite

 View Only
  • 1.  Ghost console image create fails

    Posted Jun 08, 2007 10:30 AM
    Greetings everyone.
     
    I have a classroom of Dell optiplex gx745s that I'm having trouble with.  Using GSS 2.01 I have so far successfully remotely installed the client, added the machines to my console server (all machines on the same subnet) and I can get the Dells to reboot in DOS mode and get their IP from the DHCP server.  The chain of events is like this;
     
    From the console I initiate the image create task
    the console starts up the ghostcast server
    the client reboots in dos mode and gets an IP address
    ghost starts on the client machine and looks for the ghostcast server by the correct name (as near as I can tell)
    the client doesn't see the server and reboots after a couple of seconds.
    the ghostcast server stays at 'waiting for clients to connect' until the task fails.
     
    ghosterr.txt:
     
    Date   : Fri Jun  8 08:50:15 2007
    Error Number: (10030)
    Message: Unable to establish contact with session <IITM50WS1114PULL27>.
    Check that the GhostCasting Server application is ready
    to accept clients!
    Version: 11.0.1.1533 (Apr 19 2007, Build=1533)
    OS Version: DOS v7.10
    Command line arguments: -Z1 -clone,src=1,mode=create,dst=@MCIITM50WS1114pull27 -batch -igb -jm=D -sgt
    Active Switches :
     
     
    ngctw32 file from the client;
     
    C:\Program Files\Symantec\Ghost\ngctw32.exe  11.0.1.1533
    8:50:53 AM Friday, June 08, 2007
    Checking for Sysprep. Process id: 648, 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: 736, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\WINLOGON.EXE
    Checking for Sysprep. Process id: 780, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SERVICES.EXE
    Checking for Sysprep. Process id: 792, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\LSASS.EXE
    Checking for Sysprep. Process id: 956, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\ATI2EVXX.EXE
    Checking for Sysprep. Process id: 972, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 1040, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 1184, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 1268, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 1444, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 1640, name: \DEVICE\HARDDISKVOLUME2\WINDOWS\SYSTEM32\SPOOLSV.EXE
    Checking for Sysprep. Process id: 1740, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\BROADCOM\ASFIPMON\ASFIPMON.EXE
    Checking for Sysprep. Process id: 1792, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\MCAFEE\COMMON FRAMEWORK\FRAMEWORKSERVICE.EXE
    Checking for Sysprep. Process id: 1848, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\MCAFEE\VIRUSSCAN ENTERPRISE\MCSHIELD.EXE
    Checking for Sysprep. Process id: 1892, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\MCAFEE\VIRUSSCAN ENTERPRISE\VSTSKMGR.EXE
    Checking for Sysprep. Process id: 1960, name: \DEVICE\HARDDISKVOLUME2\PROGRAM FILES\SYMANTEC\GHOST\NGCTW32.EXE
    #\Locate{ Name = #[0x17 0x29 0xD5 0xE0 0xE7 0x9C 0xED 0x48 0x2E 0xF2 0x7F 0xC2 0xFB 0xE0 0x2F 0x7B 0xF5 0x67 0x7E 0x98], Certificate = (), Signature = (#[0x06 0xCA 0xAC 0x8B 0x73 0x3B 0x06 0x33 0x10 0xD9 0x4D 0xEE 0xA8 0xAC 0xF0 0x7E 0xF0 0xBC 0x61 0x59 0x8A 0x5A 0xC3 0x65 0x5C 0x15 0x2A 0xF8 0x30 0xDF 0x83 0x44 0x9E 0x8C 0x02 0x0A 0x4F 0x6F 0xAD 0x72 0x03 0xD1 0xC9 0xFC 0xB3 0x99 0xFC 0xF1 0xC7 0xB9 0xDF 0xDC 0xA1 0xDD 0x60 0xE3 0x79 0x68 0x87 0xD3 0x8B 0x25 0xE6 0xC7 0x0A 0xF8 0x05 0x2D 0x7D 0xBF 0x4F 0x5F 0x66 0x09 0xAD 0xBF 0x53 0xAA 0xA3 0xD4 0xF1 0xEE 0xA9 0xB3 0xBC 0x29 0xD5 0x3E 0x88 0x66 0x8C 0xC7 0xB5 0x16 0x01 0xF7 0xAA 0xF8 0x0A 0x7A 0x33 0x74 0xA1 0x97 0x0F 0x3B 0x62 0xAA 0xB2 0x48 0x05 0xE7 0xCF 0x3C 0xA6 0x64 0x3B 0xE9 0xFF 0x03 0xFC 0x65 0x25 0x94 0x0E 0x66 0x85 0x68] . #[0x05 0x53 0x89 0xBE 0x74 0x46 0x68 0x3B 0x3C 0xEE 0x8A 0x29 0xC0 0x33 0x18 0x32 0xCB 0x79 0x2B 0x23 0x76 0x28 0xDB 0x68 0x82 0xEA 0x04 0x6C 0x85 0x69 0x12 0xDA 0xF5 0x94 0x4E 0xB5 0x63 0x46 0x58 0xDB 0x11 0xE4 0x20 0xDA 0xD8 0x27 0x03 0x49 0x45 0xE9 0x2C 0x21 0xAE 0x95 0xC2 0xC7 0x9E 0xEE 0x9A 0xA8 0xBD 0xB8 0x3B 0xEB 0x53 0xDD 0x04 0x7D 0xBE 0xCA 0x86 0x7E 0xD0 0x35 0xE6 0x0A 0xDD 0x97 0xF9 0xD3 0xBE 0x92 0x91 0xC0 0xA2 0x51 0x95 0x45 0x33 0x30 0x57 0xA4 0xE3 0xEB 0xFA 0xFB 0xAA 0x62 0xF1 0xA5 0xD7 0x94 0x02 0x35 0x9D 0x3B 0xD7 0x41 0xF2 0xAC 0x9D 0x47 0xA9 0x51 0x1B 0xCC 0xDE 0x55 0x58 0xA6 0xD3 0x7A 0x5F 0x09 0x7B 0x15 0x14 0xD9]), Response = #[0x1A 0x25 0x36 0x40 0xFC 0xEB 0x00 0x82], IPADDRESS = 168429852, Product = Ghost, Host = iitm50ws1114, Address = 1347, Component = Config_Server, Challenge = #[0xA1 0xE7 0xCD 0x7E 0x21 0x88 0x14 0xEE] }
    8:50:54 AM 10.10.9.28:1346 sending status to  10.10.9.29:1347
    8:50:54 AM 10.10.9.28:1346 acknowledged by    10.10.9.29:1347
    8:50:54 AM 10.10.9.28:1346 TCP connecting to  10.10.9.29:1347
    Received message #\taskInProgess{ Cancel = 1 }
    Received message #\PreventLoginTask{ DisableLogin = 0 }
    Received message #\Shutdown{ Name = () }
    8:50:54 AM 10.10.9.28:1346 disconnecting from 10.10.9.29:1347
    8:51:14 AM 10.10.9.28:1346 sending status to  10.10.9.29:1347
    8:51:14 AM 10.10.9.28:1346 acknowledged by    10.10.9.29:1347
    8:51:34 AM 10.10.9.28:1346 sending status to  10.10.9.29:1347
    8:51:34 AM 10.10.9.28:1346 acknowledged by    10.10.9.29:1347
    8:51:54 AM 10.10.9.28:1346 sending status to  10.10.9.29:1347
    8:51:54 AM 10.10.9.28:1346 acknowledged by    10.10.9.29:1347
     
    So far I have made sure that all firewalls are disabled.  While the subnet I am using is quite restricted via our network firewall, should that have an impact on machines on the same switch in the same subnet? I have tried Multicast, Unicast and Directed Broadcast options all without success. I have also manually copied the security certificates from the server to the client, also without success.
     
    Any ideas would be most appreciated.

    B

    Message Edited by Barticus on 06-08-200707:32 AM



  • 2.  RE: Ghost console image create fails

    Posted Jun 11, 2007 06:42 AM
    Hi 'B',
     
    It looks like Ghost.exe cannot find the GhostCast server address. You said that the network is restricted, so multicasting is probably turned off. Ghost tries multicasting, WINS and then broadcasting to find the GC server, in that order.
     
    However, Windows client use the same methods and they are able to find the Console. This is somewhat difficult to understand. Could you see if the WINS settings are correct in Ghost Console?
     
    Could you check if you add 'jaddr=10.10.9.29' to the Ghost Command line (in the task, select Clone->advanced) if it is going to work? This will make Ghost to just use this address for the server without trying to discover it.
     
    Krish
     
     


  • 3.  RE: Ghost console image create fails

    Posted Jun 11, 2007 09:29 AM
    Thankyou for the pointer Krish;
     
    I added the -jaddr=10.10.9.29 under the advanced option in ghost console but it made no difference.  I also tried using the -ju and -jd options there with the same results.  Any more ideas?  I would really like to use the AI option for Ghost as it would really cut down my preparation time for each different class that gets taught there.
     
    Thanks for your help.

    B

    Message Edited by Barticus on 06-11-200707:10 AM



  • 4.  RE: Ghost console image create fails

    Posted Jun 12, 2007 02:38 AM
    I forgot to tell you that you need to select unicasting also. This could be selected from the Task->Network tab.

    Do not use any other switches (except jaddr) since they may conflict with the switches added by Console. If this also fails, please post the first few lines of the Ghost error file - that will help me to check what switches it is using.

    Krish


  • 5.  RE: Ghost console image create fails

    Posted Jun 12, 2007 08:28 AM
    Using the -jaddr switch with both console and client set to unicast, it still fails;
     
    Date   : Tue Jun 12 08:11:54 2007
    Error Number: (10030)
    Message: Unable to establish contact with session <IITM50WS1114PULL50>.
    Check that the GhostCasting Server application is ready
    to accept clients!
    Version: 11.0.1.1533 (Apr 19 2007, Build=1533)
    OS Version: DOS v7.10
    Command line arguments: -jaddr=10.10.9.29 -clone,src=1,mode=create,dst=@MCIITM50WS1114pull50 -batch -igb -jm=U -sgt
    Active Switches :
          AutoName
     
     


  • 6.  RE: Ghost console image create fails

    Posted Jun 12, 2007 08:54 AM
    SUCCESS!
     
    While I was searching the forums for command line switches I came across this thread;
     
     
    Apparently McAfee blocks the IRC ports that Ghost Console needs to do it's thing.  I unblocked those ports and everything seems to be working, for now at least.
     
    B