Where is My Installed Ghost Agent?
Updated: 04 Jan 2012
You have successfully deployed and installed the Windows Agent for Ghost.
Local at the client the agent status in the task bar shows:
managed by <Server Name> <Server IP>:1347
But this client machine does not show up in the Ghost Console.
You could not locate any issues about the client on the GSS Server.
The server log file 'ngserver.log' shows the entry:
<time stamp> found client <Client ID> ip_<client IP address>:1346 state Idle
The client log file 'ngctw32.log' shows the entry:
<time stamp> <client IP address> sending status to <server IP address> <time stamp> <client IP address> acknowledged by <server IP address>
Possible Solution:
• Check if a client with the same network card (NIC) already exists.
- common issue with Notebooks using and sharing Docking Stations
- NIC has been replaced; but client is still in the console under former MAC address.
(Using an Inventory View, prepared View or filter necessary to search for MAC address and divert the result in to a report)
• If client has more than one NIC check for all this MAC addresses in the console.
- WiFi
- Bluetooth
- WiFi
- Bluetooth
• Check for former client entries in the console.
- specially all clients with the status: 'Disconnected'
- different Host Name; other NIC in use
- check other folders as 'Default Computers' if exist.
* Setup a task for all computers which gathering the configuration of the clients.
At this way the database will be upgraded with the latest client information.
- specially all clients with the status: 'Disconnected'
- different Host Name; other NIC in use
- check other folders as 'Default Computers' if exist.
* Setup a task for all computers which gathering the configuration of the clients.
At this way the database will be upgraded with the latest client information.
• Check the ngserver.log on the GSS Server for any duplications.
1. Any duplicate MAC address? This issue is known with virtual MAC addresses used by VPN clients.
2. Any duplicate UUID? Known reason for that could be that Network Card or Motherboard has not be supplied with unique GUID by the manufacture
1. Any duplicate MAC address? This issue is known with virtual MAC addresses used by VPN clients.
2. Any duplicate UUID? Known reason for that could be that Network Card or Motherboard has not be supplied with unique GUID by the manufacture
Article Filed Under:
Group Ownership: