Ghost Solution Suite

GSS Version 1.1 on Windows XP
Ghosting to Windows XP SP2 - Full patched

When I ghost my lab computers (IBM and Dells - 2 images) I use boot disks and multicast to do a max of 25 computers at a time. I then run Ghostwalker and change the Computer name and SID.

When I reboot I logon as the local Administrator account and change the IP of the computer and the SID.

Reboot and join the computer to our Windows domain.

When I try to logon with the Domain account (part of the local Admin group and the domain admin group) The computer sits at "Loading Profile" and doesn't go any further.

When I look at the user profiles when I login as local admin there is now 2 Administrator Accounts (on folder called Administrator and one called Administrator.computername) and 2 domain accounts. I can clear all of the accounts but still I am unable to login with the domain account I had setup on the image.

I am unsure why this problem has started. Last Ghosting of the labs it was the odd machine that this happened on.... Now it is all of them.

Could it be that with the latest security patches for Windows XP has caused an incompatibility with Ghost Solution Suite 1.1?

P.S The image file verifies when check with Ghost.

Hmm. I did fix a problem in Walker a while back that sometimes produced similar issues; if you use RegEdit to look in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, you should see a list of specific account SIDs listed as subkey names under there. Walker normally renames them fine, but under some circumstances what could happen is that the change from the original to the new SID would cause the subkey names to be sorted wrong in the registry data file.

The end result was that you could see them in some APIs, but some other APIs to access those registry keys would fail; if you check all the profile registry subkeys in regedit and one of them is unreadable, that might be the reason and there's a code fix to Walker that can stop this happening.

Check with regedit, and if some of the profile subkeys are inaccessible let us know, and I ought to be able to hook you up with a Walker version that fixes that. If they all read fine the underlying reason might be something new that we have to dig deeper into.

Nigel,
It looks like you have my answer. I used Ghost Walker on my test be (that has been working fine ... but I never used Ghostwalker on it) and now I cannot access one key in the registry.

I would appreciate the updated Ghost Walker to see if this indeed solves my problem... It looks promising though.

Thanks

It does sound like the same problem then - drop me an e-mail at nigel dot bree at gmail dot dom and I'll send a download link to you.

Nigel,
I have sent you an email. If you don't recieve it please send me the file at cmckay at yukoncollege dot yk dot ca.

I am looking forward to running this Ghost Walker version and (hopefully) solving the problem.

Thanks the new version of Ghostwalker worked for this problem.

OH my this is exactly the same problem we are having. we have thought it may have had something to do with the way our image process was taking place.

Nigel is there anyway for me to also receive the updated ghost walker ?