Ghost Solution Suite

Hello Everyone:
I have an odd problem, but probably a simple resolution. Here's the senario:
10.211.10.x  and 10.211.50.x are located in seperate buildings.
All images were built on the 10.211.10.x network (no sysprep, just build the image and ghostwalk/rename machines through configuration).
Brought copies of the images to 10.211.50.x network
Loaded up the image in Ghost Explorer and deleted the pubkey.crt file so the image is "keyless" so they should bind themselves to the local Ghost server when it boots into Windows.

When the machines are imaged now, they want to attach to the 10.211.10.x network's console.  This is causing a problem because I am going to run out of licenses for that console. (Even though I delete them, I have yet to figure out how to purge them from the database. Those and the assets I retired and recycled, but that's a different question.)

I've been doing this for over 5 years now using the same method.  The only thing different this time is that I was using the WinPE instead of PCDOS.  Is there something in that boot partition that's pointing back to the 10.211.10.x network?   What am I missing?

Thanks for your help.
-Milnesy

There should not be. Reason is because Winpe boot partition is entirely virtual. When Winpe is booted an entire disk surface is dedicated to cloning, unlike DOS that still keeps this virtual partition around and repositions it before doing cloning.

There could be two reasons client will connect to another server: a) certificate is in the image somehow (easy to verify with ghost explorer) b) it simply finds another server first.

In either case you can just stop ghost client service, copy correct certificate and restart the service.

Try this link, where its described step by step.

www-secure.symantec.com/connect/blogs/after-installing-ghost-console-another-machine-remote-clients-do-not-target-new-ghost-console

I hope this will solve your problem.

Greetings

alexander emmer

Eugene:
That's what I thought. I even went into the image and pulled the .crt file.  

G-3... I was thinking the same thing about the DNScache.txt file.  I've always used the dos client, so I didn't know about the file. I was poking around the image on Sunday and saw that. I'm gonna give that a try.

On a side note, I have the Pre-OS on a thumbdrive.  I was able to pull the DNS cache.txt file from the images I'm using... but is there a DNScache.txt file inside the .wim file on the Pre-OS image?

I'll let you know the status...

Thanks.
Milnesy

I went into all of my images and deleted the dnscache.txt from the image and now all machines are attaching to the right console.

My only problem now is the winpeboot.gho file that i have on a thumbdrive to boot into console client.  I tried to  delete the notification for the dnscache.txt from the manifest.txt ... but that didn't work.  So I'm guessing that the dnscache.txt or a pubkey.crt is inside that .wim file for the windows PRE-OS.  anyone know of a good 3rd party tool that will let me modify the .wim files?