hello all
this problem has me absolutely stumped, hope you guys have some idea of what's going on because i've run out of ideas and have exhausted googles and EE's solutions to no avail.
Setup as follows: Parent PDC: Win2k8 x64 standard, child DC: win 2k3 x86 std. ALL clients XP sp3, fully up-to-date.
I have about 10 users logging into a child domain on my network. All users (on child and parent domain) have a roaming profile.
Nearly every morning the child DC picks one user at random on this child domain to pop the message 'windows cannot copy the file blah blah blah. Reason: Access denied' then straight away another popup 'Windows cannot locate your roaming profile and is logging you on with a temporary one.... reason: access denied'. This happens pretty much every morning to a different user, sometimes to 2 users, sometimes it doesn't happen and everyone logs in fine.
The file windows cannot copy is ALWAYS an MS Word shortcut eg. worddoc.doc.url in docs&settings>local settings that is not there when browsing through the profile folder.
The users profiles folder is a hidden share (user$) and is set so the user has full control in both the sharing and security tab, and offline file caching is OFF. In ADUC the users profile folder is set to \\profileserver\user$\prof
ile. i can get round it by getting them to logout and in ADUC change their profile folder in ADUC to \\profileserver\user$\prof
ile2 and they can login fine. this is getting a bit tedious doing it practically every morning
this is exactly how the parent domain's roaming profiles are set up and none of those users have this issue.
I have amended the GPO to make sure the PCs wait for the network before logging in and have also tried rebuilding the profiles from scratch, but that doesn't matter as it happens to new users on the domain. there is nothing in the event log on the server, not even a failure audit in the security log.
All child DC clients have a static IP and the child DC as primary dns and the parent DC as secondary dns.
the thing is - this started happening overnight a couple of weeks ago for no apparent reason so i'm thinking it could be a faulty server update.
has anyone seen this before? any ideas?