G
gasmonso
After deploying my initial SP2 image to the target device, I reboot and
wait for the FBA to finish. The reseal is done manually, so I can
manually configure some software before resealing. But I have noticed a
strange problem with file/directory ownership. All core Windows
directories including C:\Windows and C:\Program Files have a SID as the
owner as with all their subdirectories and files. I assume that this
was the SID of the "Administrator" before FBA ran, but that information
is lost now. Even files that were copied over as part of a component
are losing the Administrator ownership information and being replaced
by a SID.
Now I know people in the past have suggested just writing a script to
redo the ownerships, but that is nothing more than a hack. Does anyone
know the root cause of this issue and how to fix it properly? This
image is for a medical product and I need to be very careful with how I
go about modifying it.
Your timely help would be greatly appreciated!
Regards,
Another Overworked Engineer
wait for the FBA to finish. The reseal is done manually, so I can
manually configure some software before resealing. But I have noticed a
strange problem with file/directory ownership. All core Windows
directories including C:\Windows and C:\Program Files have a SID as the
owner as with all their subdirectories and files. I assume that this
was the SID of the "Administrator" before FBA ran, but that information
is lost now. Even files that were copied over as part of a component
are losing the Administrator ownership information and being replaced
by a SID.
Now I know people in the past have suggested just writing a script to
redo the ownerships, but that is nothing more than a hack. Does anyone
know the root cause of this issue and how to fix it properly? This
image is for a medical product and I need to be very careful with how I
go about modifying it.
Your timely help would be greatly appreciated!
Regards,
Another Overworked Engineer