REALLY Annoying Problem
For some reason us 'Administrators' now cant save any files onto our desktop, any where else is not a problem
Is there a policy setting to disable and prevent saving to the desktop? I have changed the settings for the admin policy, made a new one using 2008R2 server, so Windows 7 reads the policy
I didnt put many settings in this policy, think all I enable was the proxy setting that we have to use and start menu. desktop, network documents redirection
Is there a setting I missed?
I did also change the folder redirection settings, admins didnt have start menu redirection before and the desktop was redirected from the staff start menu (Meant we had too many iconws on the desktoip, reason for the change)
Start menu now just has a folder called Network programs with all shorcuts that the staff normally have (Made a new shared folder for the admins for this, so we dont use the same folder.
Any ideas how to sort this problem out. Not good that the head cant now save to the desktop
Please help, this is very annoying
I imagine the permissions are wrong on your redirected desktop folder - if its read only for the group accessing it then you can't save to it
nope afraid its not that, admins get all the rights for folders that we create (have checked incase)
Have you checked the share permissions? [if there are any set on the folder]
Is the folder set to Read Only?
All full rights
Even tried disabled the desktop folder redirection, and doing a gpupdate /force in cmd
This message is still coming up, so I dont think it is do with folder redirection
What other settings would affect this?
This may sound stupid but have you tried rebooting the effected machines since you disabled your redirected dektop?
We had an issue here with something different and we forced the pcs to do a GPupdate but when the command was run the change didnt take. We couldnt work out why but once the machine had been rebooted it was fine...
nope was only logging off after gpupdate was done has it requested to
ok wil try that tomorrow then, might has well just disable the whole admin policy see if that makes diffrerence
I always assumed 9 times out of ten a reboot is required, although I think this is only true for computer policies...
Did you do gpupdate /force both on the machine and the server? (how I was tought to do it)
is shouldnt need a reboot normally unless it says it needs to has it will say tupe 'y' to reboot now
Has its only a user policy it shouldnt need a reboot
i was actually testing this on the server, could not be asked to find a spare computer to test
You're not trying to apply a user policy to a computer OU without loopback processing enabled are you (or vice-versa)?
Could be a long shot, but worth checking