Anyone know what would cause a ghost client to not connect to the console server, but instead read 'polling for bound server' in the debug window? Everything google throws up is to do with the publey.crt file, however, were only getting the error on 10 out of 25 machines all cloned with the same image (the clone works fine, they just dont reconnect to the console after.)
I know its a bit of a longshot, but symantec tech support are like my backside.
The clients that won't connect aren't going via a router are they, if they are then you'll have to enable the transmission of broadcasts as that's what the ghost client does to locate a server.
Nope, exactly the same configuration, in the same room. even tried swapping ports on the switch. The current cludge fix is to remove teh ghost client from the image, then use remote install to do it. However that means joining the machines to the domain in the windows minisetup (the image is created with ms sysprep) which means arsing around moving things in Active directory manually. Oh well, should hopefully only have to do it once per room.
How did you install the client software, when producing an image I normally install the client with the servername as DUMMY so that the pubkey.crt file is a text file with the text DUMMY inside it. When the PC then boots the client then auto-discovers the local ghost server and fetches a valid pubkey.crt from that ghost server and registers with the ghost console.
that was the plan, but it dont work
Can't help in that case. It's not a licensing problem on the Ghost server is it?
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote