Ghost Solution Suite

  • Private Community
 View Only

  • 1.  No Clients in Default Machine Group

    Posted Sep 13, 2007 09:07 AM
    We installed GSS 2.0 on an new Windows Server 2003 (incl. Service Pack 2) with no problems.
     
    After that we installed the client software on a Windows XP professional (service Pack 2). The client-software is installed like the way it should be on teh client-computer, but we can't see the client in the Symantec Ghost Console ==> Machine Groups ==> Default or any other place.
     
    Can anyone tell me what we can to solve this problem?
     
     
    Marco
     


  • 2.  RE: No Clients in Default Machine Group

    Posted Sep 14, 2007 09:15 AM
    I seem to have this same problem.  I have only the trialware version of GSS running on a Vista desktop PC (for testing purposes).  I have pushed the client out from the console to 2 other Vista computers as well as an XP computer.
     
    The client icons are showing up next to the clock, I can ping them, but they are not showing up in my Machine Groups.
    When I check the NGCTW32.log file, it shows "Polling for server name XXXXXXXXXX"....
     
    C:\Program Files\Symantec\Ghost\ngctw32.exe  11.0.1.1532
    3:38:01 PM Thursday, September 13, 2007
    Checking for Sysprep. Process id: 340, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SMSS.EXE
    Checking for Sysprep. Process id: 500, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\CSRSS.EXE
    Checking for Sysprep. Process id: 524, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\WINLOGON.EXE
    Checking for Sysprep. Process id: 568, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SERVICES.EXE
    Checking for Sysprep. Process id: 580, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\LSASS.EXE
    Checking for Sysprep. Process id: 740, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 800, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 868, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 952, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 1044, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 1164, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SPOOLSV.EXE
    Checking for Sysprep. Process id: 1308, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\DELL\OPENMANAGE\CLIENT\ACTIONAGENT.EXE
    Checking for Sysprep. Process id: 1332, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\SVCHOST.EXE
    Checking for Sysprep. Process id: 1352, name: \DEVICE\HARDDISKVOLUME1\DMI\WIN32\BIN\DELLDMI.EXE
    Checking for Sysprep. Process id: 1404, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\DELL\OPENMANAGE\CLIENT\EVENTAGT.EXE
    Checking for Sysprep. Process id: 1440, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\DELL\OPENMANAGE\CLIENT\DLT.EXE
    Checking for Sysprep. Process id: 1480, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\DELL\OPENMANAGE\CLIENT\IAP.EXE
    Checking for Sysprep. Process id: 1508, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\INETSRV\INETINFO.EXE
    Checking for Sysprep. Process id: 1548, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\COMMON FRAMEWORK\FRAMEWORKSERVICE.EXE
    Checking for Sysprep. Process id: 1660, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\VIRUSSCAN\MCSHIELD.EXE
    Checking for Sysprep. Process id: 1676, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\VIRUSSCAN\VSTSKMGR.EXE
    Checking for Sysprep. Process id: 1828, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\VS7DEBUG\MDM.EXE
    Checking for Sysprep. Process id: 1848, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\NVSVC32.EXE
    Checking for Sysprep. Process id: 1904, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\WDFMGR.EXE
    Checking for Sysprep. Process id: 1960, name: \DEVICE\HARDDISKVOLUME1\DMI\WIN32\BIN\WIN32SL.EXE
    Checking for Sysprep. Process id: 112, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\COMMON FRAMEWORK\NAPRDMGR.EXE
    Checking for Sysprep. Process id: 1840, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\ALG.EXE
    Checking for Sysprep. Process id: 5024, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\EXPLORER.EXE
    Checking for Sysprep. Process id: 7756, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT INTELLIPOINT\IPOINT.EXE
    Checking for Sysprep. Process id: 7208, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\COMMON FRAMEWORK\UDATERUI.EXE
    Checking for Sysprep. Process id: 7428, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\VIRUSSCAN\SHSTAT.EXE
    Checking for Sysprep. Process id: 7628, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\NETWORK ASSOCIATES\COMMON FRAMEWORK\MCTRAY.EXE
    Checking for Sysprep. Process id: 6084, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\QUICKTIME\QTTASK.EXE
    Checking for Sysprep. Process id: 7440, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\RUNDLL32.EXE
    Checking for Sysprep. Process id: 6300, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT INTELLITYPE PRO\TYPE32.EXE
    Checking for Sysprep. Process id: 7968, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\CTFMON.EXE
    Checking for Sysprep. Process id: 7544, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\HEWLETT-PACKARD\LASERJET ALL-IN-ONE\HPPDIRECTOR.EXE
    Checking for Sysprep. Process id: 6216, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT OFFICE\OFFICE11\OUTLOOK.EXE
    Checking for Sysprep. Process id: 6612, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\MICROSOFT OFFICE\OFFICE11\WINWORD.EXE
    Checking for Sysprep. Process id: 7116, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\HS2000\HS2000.EXE
    Checking for Sysprep. Process id: 5144, name: \DEVICE\HARDDISKVOLUME1\WINDOWS\SYSTEM32\MSIEXEC.EXE
    Checking for Sysprep. Process id: 7624, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\SYMANTEC\GHOST\NGCTW32.EXE
    Checking for Sysprep. Process id: 8248, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\SYMANTEC\GHOST\NGTRAY.EXE
    Checking for Sysprep. Process id: 8456, name: \DEVICE\HARDDISKVOLUME1\PROGRAM FILES\SYMANTEC\GHOST\NGCTW32.EXE

    3:38:06 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:38:16 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:38:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:39:16 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:40:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:42:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:44:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:46:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:48:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:50:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:52:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:54:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:56:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    3:58:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:00:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:02:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:04:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:06:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:08:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:10:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:12:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:14:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:16:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:18:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:20:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:22:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:24:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:26:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:28:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
    4:30:36 PM xxx.xxx.xxx.xxx:1346 polling for server named %servername%
     
     
    -IP is Xed out and servername is changed.  its using NetBios name, not IP for the server.


  • 3.  RE: No Clients in Default Machine Group

    Posted Sep 16, 2007 01:46 AM
    In the Default folder are there any names in it? If so try this to see if it works. Create a task and call it "client refresh" and save it. Open up the new task create and enable the check mark that says "refresh configuration". After that select the  location where the Default folder is at to refresh configurations. Wait unit it completes it and then look for the computer name that's missing. If this does fixs the issue please let me know because theres a bigger issue with your ghost image or configuration task that you for got to enable.
     
     
    Systemfire enjoy...


  • 4.  RE: No Clients in Default Machine Group

    Posted Oct 29, 2007 09:22 AM
    Hi,
     
    I've solved my problem. It had nothing to do with Windows-updates or the Ghost-console. The problem was that we're using VLAN's and the Ghost-console neets to be on the same VLAN as the ghost client-pc's. Now the clients are normaly shown in the ghost-console and i can execute all the tasks.