Ghost Solution Suite

 View Only

  • 1.  Ghost 11: Shuttle XPC clients not showing up

    Posted Mar 26, 2007 10:06 AM
    This sounds a little like the Dell issue I've heard about. Our Shuttle XPC machines won't show up in the console - we get one machine per model (we have two Shuttle models on the network) and if I remove that one from the console a different one appears, presumably based on which workstation manages to connect to the ghost server (actually a surplus Compaq workstation running XP Pro) first.
     
    We have rooms full of generic P4 systems that don't have this problem. The strange thing is that the very same machines all connected concurrently using Ghost 8 without a problem. We've made no changes to the network setup whatsoever.
     
    Is there a manual workaround for identifying individual machines? I rather like the virtual partition solution and the thought of booting each machine by disc is a little much for my nerves as we've been through quite a few iterations of our image recently!
     


  • 2.  RE: Ghost 11: Shuttle XPC clients not showing up

    Posted Mar 26, 2007 10:31 AM
    The strange thing is that the very same machines all connected concurrently using Ghost 8 without a problem. We've made no changes to the network setup whatsoever.
    Is there a manual workaround for identifying individual machines?

    In Ghost 8, the network service that manages the clients used the network adapter MAC addresses to identify them, but although this worked well in most cases there were a significant number of compatibility problems caused by software network adapters pretending to be physical ones.

    So, in GSS2 we tried to use the special, guaranteed-unique ID created for the use of management software like GSS. Except that, as we've discovered, manufacturers aren't making this unique ID really unique either (and as well, there was a special-case invalid UUID that I didn't filter out, which is my fault).

    It definitely sounds like it's the most likely cause of your problem, and you're welcome to try the fix I have. Unfortunately, there's no easy way to override this; you need an update to to the ngserver.exe code on your console machine, and right now to get hold of it you can get in touch with me at nigel dot bree at gmail dot com