Ghost Solution Suite

Hi guys!

My first post :) and a weird list of questions.

1. A group of Gx 270 don't show up in the console. When you go on the tray icon on client it says "Managed by the "Server Name" on "ip address" ", how ever in the console i can't see them. I took Gx 260 with the same image in to the same room and connected them to the data ports and they all showed up. This is the only groupo of 270 that are having issues, i have serverl other 270s that show up properly :).

2. The new core 2 duo HP DC 7700 won't boot in to virtual partition when i want to clone them. It goes go screen "Starting PC DOS " and quickly jumps to Restart. Can't seem to see as it goes really fast. Same thing happens with Dell D745 which are dual cores. This issue is only happenning in these new hardware types. All other gx 620 , gx 280, 270 n 260 are fine. I have also tried to change the disk mode in bios to Native mode and combination mode in dells. Still no success. Updated the NDISK drivers too still no luck. Also i installed a ghost boot partition on them, which runs fine. Compared the content of both the virtual partition and actual ghost partition and they seem to be same.


3. I have got a whole lab of Intel Macs, now they donot boot into virtual partition offcourse cause macs cannot pxe boot which is fine. Also they donot show up in the console, same as the gx 270 i mentioned above. All of them say that they are managed by the server. But the server only shows one machine at one time from the whole lab. So if i keep deleting the machine which is displayed in the console a new machine will show up but only one. I unplugged couple of them and took it to another room where normal windo boxes run and show up properly. Still the same issue.

4. Dc 7700 show up as mac addresses in the console. Was reading on the forume to replace a dll on to client side. Can some one send that file to me please :)

Thanks alot for your support guys :)

Message Edited by chonky on 07-01-200706:22 PM

Issues 1 and 3 sound like they are actually the same one, present in the initial 2.0 release and which we resolved in a LiveUpdate - using LiveUpdate will download a replacement installer for version 2.0.1 of the product.

Issue 2 sounds like one that was also reported, but I don't know the resolution of that one off the top of my head - Krish Jarayatne probably does.

With issue 4, although your reading is correct as to there being something throwing off that DLL (although it might well be on the server side rather than the client side) it's not at all certain that it's the actual same underlying problem as any other one - there is lots that can go wrong with that data in the registry. There isn't an update for it since 2.0.1 - I do have some data from another customer to look at but the first thing to do is update to 2.0.1, then if it's still happening we will have to investigate to see what the underlying cause is.

Hey,

thanks for the quick reply. Sorry to mention it before, i do have 2.0.1 patch applied :(

Any suggestions what to do :(?

Thanks

In that case, it's hard to know exactly what the cause is since those symptoms don't match anything I've heard reported in 2.0.1 - basically, let's start by getting hold of the ngserver.log file from your server, zipping it up, and emailing it to me at nigel dot bree at gmail dot com so I can take a look at what it says and see if I can identify anything unusual.

Hey Paul,

how do you change the mac addresses ? We donot use paralles, these are intel macs with standard windows installed on them.

Thanks