eldonmcguinness
New Member
- Messages
- 16
I recently updated two of my computers to W8.1 and have been in awe of the headaches that come with it. One thing that seems to be a public nuisance is having to use a Microsoft Account to have a syncing onedrive folder. This aside I have been trying to get File/Printer Sharing working between a file server and a client.
With my previous W7 setup I would create custom groups for access to certain file sets and it would all go off without a hitch, the same is true with W8.1 and local accounts. The issue comes in when I try to link a MS account to said local account, at this point it seems to ignore the group permissions. Below is a diagram of the setup and the expected/actual results.
With this setup, if I try to write a file to the share in question, I get an access denied, but if I instead explicitly give test1 Read-Write access to the share then the user can write files as expected. If I unlink the MSAccount from the localaccount then the share works as expected with out the user-explicit permissions. Finally, after I have tested the localaccount is working, if I link the accounts back to the Microsoft Account it once again stops working. It seems like MS screwed the pooch on this one and completely broke it's own group [DEL]policy[/DEL] permission compatibility.
Has anyone else seen this, or even better resolved an issue like it? Perhaps I am skipping a very simple step but I just do not see what it is.
With my previous W7 setup I would create custom groups for access to certain file sets and it would all go off without a hitch, the same is true with W8.1 and local accounts. The issue comes in when I try to link a MS account to said local account, at this point it seems to ignore the group permissions. Below is a diagram of the setup and the expected/actual results.
Code:
= W8.1 File Server =
- Added localuser test1
- Added user to administrators group
- Link test1 to MSAccount
- Verified user is still part of administrators group
- Give Administrators Read-Write permission and Security on the relevant share and files
= W8.1 Client =
- Added localuser test1
- Added user to administrators group
- Link test1 to MSAccount
- Verified user is still part of administrators group
With this setup, if I try to write a file to the share in question, I get an access denied, but if I instead explicitly give test1 Read-Write access to the share then the user can write files as expected. If I unlink the MSAccount from the localaccount then the share works as expected with out the user-explicit permissions. Finally, after I have tested the localaccount is working, if I link the accounts back to the Microsoft Account it once again stops working. It seems like MS screwed the pooch on this one and completely broke it's own group [DEL]policy[/DEL] permission compatibility.
Has anyone else seen this, or even better resolved an issue like it? Perhaps I am skipping a very simple step but I just do not see what it is.
Last edited:
My Computer
System One
-
- OS
- Windows 8.1