On Fri, Jun 3, 2022 at 6:23 AM Brent Epp wrote:
I would think so too, but that doesn't appear to be happening. If it
> makes a difference, the SID actually starts with S-1-5-21. I have to
> manually take ownership in order to even access the files at all.
>
Explained another way: According to
Brent Epp writes:
> This is essentially what happened (removable disk moved from one
> computer to another).
The server resource kit from M$ used to have a tool called SubInACL that
addresses exactly this situation (among other things). You give it a
set of old/new SID pairs and it will replace
On 2022-06-02 10:14, Bill Stewart wrote:
On Thu, Jun 2, 2022 at 6:44 AM Brent Epp wrote:
In the [Security] tab for these files or directories, under "Group or
user names", it lists the owner as "Account Unknown(S-...)". In some
cases, these files are completely inaccessible and I can't even
On Thu, Jun 2, 2022 at 6:44 AM Brent Epp wrote:
In the [Security] tab for these files or directories, under "Group or
> user names", it lists the owner as "Account Unknown(S-...)". In some
> cases, these files are completely inaccessible and I can't even take
> ownership or change the
On 2022-05-08 10:35, Andrey Repin wrote:
Greetings, Brent Epp!
I recently (finally) installed Windows 10 on my system (clean install).
All of my files are stored in on a secondary drive/partition, on which
cygwin is also installed. I expected to be able to just pick up where I
left off, but
Greetings, Brent Epp!
> I recently (finally) installed Windows 10 on my system (clean install).
> All of my files are stored in on a secondary drive/partition, on which
> cygwin is also installed. I expected to be able to just pick up where I
> left off, but I'm getting all sorts of permissions
6 matches
Mail list logo
