ruhkus
asked on
Changed permissions on network folder - How can staff access without reboot?
I've been trying to modify the permissions on various network folders (Windows Server 2003), to go from full access to everyone, to the proper restricted access. This entailed removing authenticated users permissions, and changing domain user permissions to just read&execute only. However, staff that still have full read/write permissions (as a new security group addition) are getting write errors even though the permissions are correct. If they reboot, the problem is solved.
I'm trying to figure out if there is a quicker way to resolve the permission issue without needing the user to reboot?
Thanks.
I'm trying to figure out if there is a quicker way to resolve the permission issue without needing the user to reboot?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Having them log off and then log back on as McKnife stated is generally the least amount of work for all involved. Restarting services while people are actively using a machine is not always the best suggestion, and if they are not actively using the PC then when they log on it will be available.
@Machienet remote restart of netlogon service will do the job + it doesn't require user involvement
Indeed, not arguing that point, but to accomplish a task with no interaction is better than some in the eyes of this (me) busy IT guy.
Either works, just depends on the method you want to use... Pepsi-Coke (I wouldn't dare use the MAC-PC analogy here haha).
Either works, just depends on the method you want to use... Pepsi-Coke (I wouldn't dare use the MAC-PC analogy here haha).
So you would have to tell your users to restart the computer, because you are to busy to solve the problem :)
I won't get into a p-match with you as this is not the intention of the site, but before responding directly to someone like you just did with me, you should learn to comprehend and process what they stated before sticking your foot in your mouth, as you just did - I'll let you figure that one out.. perhaps with a script?
I only provided additional information on an alternative solution as stated by someone else, which you apparently do not agree with, which is also fine.
Coke-Pepsi...
I only provided additional information on an alternative solution as stated by someone else, which you apparently do not agree with, which is also fine.
Coke-Pepsi...
Machienet apologies if I upset you - that wasn't my intention - obviously our approach in resolving it problems differs.
@ ruhkus sorry for changing your straight forward question into "p-match" - which again wasn't my intention.
I just strongly believe that telling users - "restart your pc" is just not a "good enough" approach - if you can easily fix it for them - no user intervention is the key IMHO.
but like Machienet said
Coke-Pepsi...
@ ruhkus sorry for changing your straight forward question into "p-match" - which again wasn't my intention.
I just strongly believe that telling users - "restart your pc" is just not a "good enough" approach - if you can easily fix it for them - no user intervention is the key IMHO.
but like Machienet said
Coke-Pepsi...
Jan, when would that positive effect appear?
Just tried to use it, it did not help.
--
Setup: testshare, user A has read perms on share and ntfs level. Domain group X however has write access on both. Add A to domain group X, restart the netlogon service on A's computer...nothing changes.
Needless to say that I waited some time. And of course it works after logging off and on again.
--
That said, I would be very surprised if it really works because I have seen this question so often during the last 15 years - never was restarting that netlogon service even mentioned as possible solution.
Just tried to use it, it did not help.
--
Setup: testshare, user A has read perms on share and ntfs level. Domain group X however has write access on both. Add A to domain group X, restart the netlogon service on A's computer...nothing changes.
Needless to say that I waited some time. And of course it works after logging off and on again.
--
That said, I would be very surprised if it really works because I have seen this question so often during the last 15 years - never was restarting that netlogon service even mentioned as possible solution.
Should works straight away after restart of service. - just tested it on my vms
one difference is that user a will have full write and read on share level (as authenticated user) - we enforce security on ntfs level
one difference is that user a will have full write and read on share level (as authenticated user) - we enforce security on ntfs level
I don't understand what you are saying - what's the difference?
It makes no difference if I set share perms to everyone:change and only modify the NTFS perms, by the way.
What OS' are you using? In my VMs, the server side is 2012 R2 and the client is 8.1
It makes no difference if I set share perms to everyone:change and only modify the NTFS perms, by the way.
What OS' are you using? In my VMs, the server side is 2012 R2 and the client is 8.1
2008r2 and wind 7
Have no 08R2 here. Will see at work tomorrow.
guys - It doesn't work - it seams that my testing security group was a member of other security group - so restarting netlogon service doesn't work - you still have to logon/logoff - to refresh your security token
apologies for confusion
apologies for confusion
ASKER
Yeah, I was unable to get the netlogon restart to work, as confirmed. Log on/off is fine, but at that point, I prefer they just reboot.
I'll try killing explorer.exe, but I'm also curious about using klist. I don't mind going to their PC as we're not that large a company, so if they have a lot of programs open, this is sometimes preferred.
I'll try killing explorer.exe, but I'm also curious about using klist. I don't mind going to their PC as we're not that large a company, so if they have a lot of programs open, this is sometimes preferred.
Here you go: https://www.experts-exchange.com/questions/28485742/How-to-alter-NTFS-permission-WITHOUT-asking-user-to-logoff.html inside I linked also the thread where killing+restarting explorer is described.
1 restart netlogon service on the clients using psexec
https://www.experts-exchange.com/Networking/Network_Management/A_2779-Use-PSExec-to-run-a-command-remotely.html
or easier
Restart netlogon service using scritpt
Restart-Service netlogon
(save it as netlogon restart.ps1)