New
#1
Is TAKEOWN of a whole User tree dangerous?
I'm waiting for delivery of physical parts to repair laptop A
The user urgently needs her data on laptop B until A is fixed (or thrown away & replaced)
What I did
I attached via USB the System disk from A to temporary system B, where it was F: drive
Then to enable explorer to show me the data I used TAKEOWN
Code:TAKEOWN /F F:\USERS\<username> /R(I should have added something to discard all the success textMy question
Unfortunately the scope included APPDATA )
WHERE are the permissions stored?In the registry of system B running TAKEOWN ?
OR
In the MFT of the the F: drive, which I hope to boot again in system A after repair ?
If A's MFT is changed, I fear I may have messed up the system disk when it is rebooted after repair. Have I?
If permissions are recorded in TEMP system B's registry, I think no harm should have been done
Can you please clarify or give other guidance for the future - e.g "a better would have been...."
Thanks in advance
Spilly
Amateur system maintainer for local friends