Jump to content

Recommended Posts

Posted

Hi all

 

We have recently put some Windows 7 PC's on network and having an odd issue.

 

When a pupil logs onto a computer, they sometimes can't access there documents. The drive is mapped, but it says doesn't have access to it (screen shot attached). Its happening more often on 1 PC, but when staff logon its fine.

 

I've also found that when it does it, they have permission to save to a shared drive, which they don't if it logs them on properly.

 

Any ideas? I've re-added PC to domain but still does the same.

 

Thanks

 

error.jpg

Posted

Is it machine specific or user specific?

 

If it is an issue with a certain user, open their account properties in AD, got to their home path, add a space at the end and then delete it and apply changes it. AD will then warn about grating access to a folder which already exists, should be perfect.

Posted
The sync icon in the notification bar may have somehting to do with it ;)

 

They've all got that on though and the others work fine. Thats just syncing the desktop and start menu to the redirected folder

Posted

OK, after a bit of research its seems to be specific to the "secondary" AD OU.

 

The error in event log is :1085 Windows failed to apply the Folder Redirection settings. Folder Redirection settings might have its own log file. Please click on the "More information" link.

  • 1 month later...
Posted
I've had a similar problem with new windows 7 machines desktops and laptops but its not user specific it tends to be machine specific. The only way I have got around it is to re image that specific machine
  • 2 weeks later...
Posted

Karl, can they access the drive if they then type in the FQDN of the server path?

 

For example, my fileshare is at \\depot\students\username . But when I get this error, if they type in manually: \\depot.alton.school.com\students\username , then they can get there.

 

If this is the case, it is related to this thread. I know the title is regarding home folders being deleted, but this permission issue is a symptom of the problem, as well. As far as I know, Microsoft has never fixed it. There is also a discussion on Microsoft TechNet here.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...