Ghosting, invalid computer account on domain after workstation backup

[Inetquestion]

Ghosting results in invalid computer account on domain after
workstation backup

I've been taking backup snapshots of my laptop with ghost in the event
my harddrive were to die. The problem I'm running into is that when I
use a ghost image that is several weeks old the "computer account" in
the domain has to be removed and added by a user with sufficient
right. So in the long run this isn't working as seemlessly as I had
hoped it would. I understand the problem, but wondered if there is a
way around other than calling a sysadmin to intervene.

Would it be possible to periodically backup the .SAM files on the
machine also so that after the ghost image is loaded, I could copy the
newer .SAM files, thus preserving the computers domain account. I
wanted to pose the question before hosing my system once again hoping
someone has already found a similar work around.

Regards,

Inet

 

[David H. Lipman]

You have to use sysprep.exe to strip the SIDs and then when the Ghost Image is restored, you
can run the min-wizard and put the PC back in the domain properly.

Dave



| Ghosting results in invalid computer account on domain after
| workstation backup
|
| I've been taking backup snapshots of my laptop with ghost in the event
| my harddrive were to die. The problem I'm running into is that when I
| use a ghost image that is several weeks old the "computer account" in
| the domain has to be removed and added by a user with sufficient
| right. So in the long run this isn't working as seemlessly as I had
| hoped it would. I understand the problem, but wondered if there is a
| way around other than calling a sysadmin to intervene.
|
| Would it be possible to periodically backup the .SAM files on the
| machine also so that after the ghost image is loaded, I could copy the
| newer .SAM files, thus preserving the computers domain account. I
| wanted to pose the question before hosing my system once again hoping
| someone has already found a similar work around.
|
| Regards,
|
| Inet

 

[inetquestion]

Correct me if I misunderstood... It was my understanding that sysprep
was more often used in the case where you were ghosting one image to
multiple machines. Therefore there would be a SID issue in the domain.
In my case I'm putting the same image back on the exact same laptop,
therefore a duplicate SID would never be a problem. Either way I do
not have permissions to add my machine's account back into the domain
so this doesn't quite fit what I was looking for.

Regards,

Inet