Hi prm529,
Actually youve found your answer for this issue.
Clone system has same Security Identifier (SID) and it happens when you use clone software instead of running sysprep.exe /generalize which is also regardless of activation key. During installation of Windows, a computer SID is computed to contain a statistically unique 96-bit number. The computer SID is the prefix of the user account and group account SIDs that are created on the computer.
So Im supposing that is why Family Safety will not work with a cloned system. Each log-in has a different SID in which the username is associated with Family Safety web filtering.
Regards
D. Wu
- Edited by Deason WuMicrosoft contingent staff Wednesday, February 25, 2015 6:28 AM
- Marked as answer by Alex ZhaozxMicrosoft contingent staff, Moderator Friday, March 06, 2015 5:24 AM
- Unmarked as answer by prm529 Monday, March 09, 2015 6:48 AM
D. Wu,
Thank-you. I actually cloned by restoring from backup to a new hard drive on the original system. It seemed like a good opportunity to verify that my backups were working properly. I then did sysprep /out-of-box-experience /generalize and when that was complete I moved the hard drive to the new system where I performed the "upgrade" to new Win 7 key. Each computer has a unique SID. The only instance of the original SID on the "cloned" system in the registry is one Symantec quarantine record. So in regard to my Family Safety problem, it is something else. Still looking for ideas.
prm
Hi prm,
I did test on my environment, family safety should works fine for image backup restore machines after running sysprep /out-of-box-experience /generalize.
But please make sure that child account and Family Safety should be installed/added after cloning to ensure that each user account is monitored correctly.
Regards
D. Wu