> Is there an error in the configuration, the methodology, or is it between the chair and keyboard?
I'd say for this case PEBKAC is the least likely :-)
This is the first time I've heard of this but I've taken a close look at the implementation and it's a little different to what I had expected; basically, one table in the database is the master one for clients, and it has a column that contains a marshalled list of all the MAC addresses of the 802.11-style network adapters in the machine (although in GSS1.1 it could sometimes be fooled into picking up a software adapter like the MS Loopback adapter in that set).
Now, when this one piece of statistical information was added to GSS the implementer added a table just for it, and made the primary key that same binary identifier column (instead of one of the simple numeric primary key for that machine table). When displaying the property sheet for the client, the console looks in that column for it.
The configuration server updates the LastImage table as part of what it does to run images through the console, so the data only applies to imaging operations done through the console, not interactive GhostSrv.exe clones.
So, some things to check:
- maybe the data is in the LastImage table, but if the different OS's you clone report different sets of network adapters, the matching-up process is going awry.
- maybe the Configuration Server isn't updating the LastImage table properly (it's empty or something).
- maybe there's some aspect of the Identifier column that means they aren't matching up correctly in the console
Depending on whether you're keen to poke around in the database yourself, you can explore the raw contents yourself using the
dbisqlc.exe tool under "c:\program files\symantec\ghost\bin" (you can use the same credentials as the console does under "Tools" "Database Password") or you can send it to me to inspect.
Because the database has the DBA account disabled and random names and passwords for the other account, if you want to send it to me you're best to use a batch file I wrote that you can get from
http://nigel.bree.googlepages.com/export.zip that exports the username/password and archives the database into a cabinet