David Bear wrote:
I have noted this is the past as well. I have also noticed that using
ghost without any sysprep, but using a sid changer to change the
machine sid, the AFSCache file becomes unusable and must be deleted.
It the sid changing tool I used from sysinternals mentions that it
attempt to change all the sids in file system acls and registry acls.
It looks like there are some sid burried in the afscache file as well.

As documented in the Release Notes since 1.3.80, an AFS UUID is stored
in the AFSCACHE file on Windows providing a persistent identity for the
AFS client.  If you are going to clone the machine, you must not clone
the AFSCACHE file.

Jeffrey Altman

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to