Re: cloning /reseal process clonges the user priviliege



Mike,

Sorry, my bad. I meant "\Documents and Settings\<user profile>\ntuser.dat" file.

There have been some issues reported about fbreseal (SP2) on the way how it deals with security permissions on NTFS.

--
=========
Regards,
KM


"mike-ca" <bosanovav1@xxxxxxxxx> wrote in message news:1161373469.213749.49590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
KM,

i used NTFS. there is no such file as "ntdata.data" in "document and
settings", in fact, there is no such file in my system at all.

i have found another problem with cloning, i can only run the cloned
image for 2 days before license expires and no longer able to log into
the system. my another image(without cloning) has been running for
more than 2 weeks without encounter the activation problem.

thanks

KM wrote:
mike,

Quick questions to clarify the issue:
- do you use NTFS on your target device's OS partition?
- when you say you "both user can modify the files in its own "document and setting" folders", does this mean user1 have full
control over the ntdata.dat file created under his profile folder? Try to delete or modify that file being logged under the user1
after cloning. If you can do that, there is enough permissions for that file.

--
=========
Regards,
KM

i ran into a very strange problem, i am most certain it is a microsoft
bug, just wondering if anyone has encountered the similiar problem

BEFORE CLONING:
1. set "cmiResealPhase" to 0, completes FBA process
2. creates two users "user-1" and "user-2", assign them to "Users"
group
3. login as "user-1", modifies "HKEY_Current_User" reg keys
4. run "fbreseal.exe -keepdomain -keepnet -keepuser -keepmounted",
then reboots

AFTER CLONING:
1. login as "user-1", this user cannot modify the "HKEY_Current_User"
reg keys (Error "Cannot create key: Error writing to the registry)
2. login as "user-2", this user can modify the "HKEY_Current_User" reg
key

both user can modify the files in its own "document and setting"
folders, since both belong to "Users" group, they should be able to
modify their own "HKEY_Current_User" reg keys as well.


before run "fbreseal.exe" i created both users, but ONLY logged in as
"user-1", didn't log in as "user-2", that's the only difference.


thanks




.



Relevant Pages

  • Re: cloning /reseal process clonges the user priviliege
    ... is the security permissions on registry is NTFS ... There have been some issues reported about fbreseal on the way how it deals with security permissions on NTFS. ... i have found another problem with cloning, i can only run the cloned ...
    (microsoft.public.windowsxp.embedded)
  • Re: cloning /reseal process clonges the user priviliege
    ... not such file on my XPE machine, on my regular xp pro machine, this ... There have been some issues reported about fbreseal on the way how it deals with security permissions on NTFS. ... i have found another problem with cloning, i can only run the cloned ... reg keys (Error "Cannot create key: Error writing to the registry) ...
    (microsoft.public.windowsxp.embedded)
  • Re: cloning /reseal process clonges the user priviliege
    ... settings", in fact, there is no such file in my system at all. ... i have found another problem with cloning, i can only run the cloned ... do you use NTFS on your target device's OS partition? ... reg keys (Error "Cannot create key: Error writing to the registry) ...
    (microsoft.public.windowsxp.embedded)
  • Re: cloning /reseal process clonges the user priviliege
    ... file BEFORE the cloning and AFTER the cloning. ... setting has been reset back to "do not show hidden files and folders" ... There have been some issues reported about fbreseal on the way how it deals with security permissions on NTFS. ...
    (microsoft.public.windowsxp.embedded)
  • Re: cloning /reseal process clonges the user priviliege
    ... nothing suspecious as far as NTFS permission settings. ... file BEFORE the cloning and AFTER the cloning. ... setting has been reset back to "do not show hidden files and folders" ...
    (microsoft.public.windowsxp.embedded)

Loading