<span style=" font-size:10pt;font-family:sans-serif">Hello Henrik,</span><br><br><span style=" font-size:10pt;font-family:sans-serif">What you are seeing
has to do with whether UAC (User Access Control) is enabled/disabled on
Windows.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">On Windows 7 and
2012R2 etc, my guess is that you have disabled UAC (since that is what
GPFS required in the past). When UAC is disabled, the default owner of
a local file/dir created by a user that is member of Administrators group,
is set as Administrators (SID = S-1-5-32-544). That is mapped to autogenerated-id
15,000,000 in your case. On Windows 10 (where UAC MUST stay enabled), the
behavior changes. When UAC is not disabled (and NOT running elevated),
the default owner of a local file/dir created by a user that is member
of Administrators group, is set to that user SID. Hence, it is not S-1-5-32-544,
rather a unique SID for that local user. In absence of AD setup and RFC
2307 mappings, GPFS is auto-mapping that user SID to 15,000, 270 in your
case. As you see, the state of UAC results in different owners.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">You simply cannot
disable UAC on Windows 10 (and newer versions) since it breaks certain
OS components! Hence, to get consistent behavior (the latter semantics
where file owner = user SID), you could enable UAC on Windows 7/2012R2
to default (instead of disabling it). GPFS 4.2.3.12 works with UAC enabled.
Remember though that the old 15,000,000 is on-disk ACL structures, hence
you will have to explicitly set/change owner to yourself (to update to
15,000,270) for existing files. Any new files/dirs though should default
to 15,000,270.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">You could also
add an ACL entry for Administrators group or individual users granting
desired access instead of relying on file ownership for access rights.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">Regards, The Spectrum
Scale (GPFS) team<br><br>------------------------------------------------------------------------------------------------------------------<br>If you feel that your question can benefit other users of Spectrum
Scale (GPFS), then please post it to the public IBM developerWroks Forum
at </span><a href="https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479"><span style=" font-size:10pt;font-family:sans-serif">https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479</span></a><span style=" font-size:10pt;font-family:sans-serif">.
<br><br>If your query concerns a potential software error in Spectrum Scale (GPFS)
and you have an IBM software maintenance contract please contact 1-800-237-5511
in the United States or your local IBM Service Center in other countries.
<br><br>The forum is informally monitored as time permits and should not be used
for priority messages to the Spectrum Scale (GPFS) team.</span><br><br><br><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Henrik
Cednert (Filmlance)" <henrik.cednert@filmlance.se></span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">gpfsug
main discussion list <gpfsug-discuss@spectrumscale.org></span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">02/05/2019
11:21 AM</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[gpfsug-discuss]
Mapping GPFS v5 Windows client to same UID...?</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">gpfsug-discuss-bounces@spectrumscale.org</span><br><hr noshade><br><br><br><span style=" font-size:12pt">Hello</span><br><br><span style=" font-size:12pt">Odd. Apparently i have issues posting
to the list again. Sorry if this comes in double. </span><br><br><span style=" font-size:12pt">I’ve read a bit about this on the net
but can’t wrap my tiny little brain around it. </span><br><br><span style=" font-size:12pt">We have a bunch of windows 7 and 2012r2
clients that ran v4 previously. After a system/server upgrade of the DDN
Mediascaler to 4.2.3.12 we had to upgrade those clients to v5 so that they're
compatible. In addition to that a new v5 windows 10 client was deployed.
</span><br><br><span style=" font-size:12pt">The old windows 7 and 2012r2 clients
writes to the system with the same UID, 15000000, but unique GID. The new
client has its UID set to 12000270 and an unique GID. This cases all sorts
of painful verbal and non verblam symptoms. </span><br><br><span style=" font-size:12pt">Funny thing is that a newly added 2012r2
windows client has UID 15000000, so it’s just the windows 10 client that
messes with me. All have been installed with same installers and same procedures.
</span><br><br><span style=" font-size:12pt">Since all the others can write with same
UID this new windows 10 one for sure has to be able to do it as well. Or?
Can someone please point me in the right direction here?</span><br><br><span style=" font-size:12pt">Yes, I know an AD is best practice. But
not possible at the moment so I’d just like to restore the same functionality
that we had before upgrade. </span><br><br><span style=" font-size:12pt">Cheers and thanks. </span><br><span style=" font-size:9pt;font-family:Helvetica"><br>-- <br>Henrik Cednert <b>/ </b> + 46 704 71 89 54 <b>/</b> CTO
<b>/ </b> <b>Filmlance</b></span><span style=" font-size:6pt;color:#5f5f5f;font-family:Helvetica"><br>Disclaimer, the hideous bs disclaimer at the bottom is forced, sorry. ¯\_(ツ)_/¯
</span><br><br><span style=" font-size:10pt;color:#5f5f5f;font-family:Verdana"><b>Disclaimer</b></span><br><br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana">The
information contained in this communication from the sender is confidential.
It is intended solely for use by the recipient and others authorized to
receive it. If you are not the recipient, you are hereby notified that
any disclosure, copying, distribution or taking action in relation of the
contents of this information is strictly prohibited and may be unlawful.</span><br><tt><span style=" font-size:10pt">_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></span></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><span style=" font-size:10pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></tt></a><tt><span style=" font-size:10pt"><br></span></tt><br><br><BR>