已答复 Local Drive mapping and Roaming Profiles

  • Monday, December 10, 2007 10:56 AM
     
     

     

    Hi There Everyone,

     

    I'm experiencing an problem with my terminal servers, first i thought the problem had to do with my installation but after a reinstall the problem came back.

     

    When a user logs of from the server sometimes the local copy of the roaming profile remains locked, next time the user connects to this server he cannot map its local drives, there are some strange icons in the my computer area but i can't connect to the local disks though rdp.

     

    When i go to the my computer properties and then advanced --> user profiles i see this profile but i can't delete it. After a restart i can delete the profile. This is very strange and i don't know how to solve this problem.

     

    Hope u can help me!

All Replies

  • Monday, December 10, 2007 3:18 PM
     
     
    Hi Robin,

     

    Could you give me some more information from the event viewer please?

    There should be messages when there are problems with your roaming profiles.

    Is the NTFS security on the profile folder set in the correct way?

     

    Let me know,

    Bas.

     

  • Monday, December 10, 2007 3:40 PM
     
     

    Hi Bas,

     

    I found only one warning that is repeating and that has to do with logging of the user:

     

    Event: Userenv

    Type: Warning

    id: 1517

     

    It sais that the register was in use when the user logs off, it will be locked till the process is stopped.

    What NTFS does the profile folder need?

     

    Thanks for your time:

    Robin

  • Monday, December 10, 2007 4:02 PM
     
     Answered

    Does the user use encryption?

    Event ID: 1517 http://support.microsoft.com/kb/900613

     

    NTFS security on the profile folder:

    Administrators, System, Creator Owner: full control

    Everyone: Write, Read, Read and Execute, List folder contents

  • Tuesday, December 11, 2007 8:55 AM
     
     

    I checked the permisions, it looks like there was a problem there, there was no groep called creator owner, i added it and gave it the right permissions, but it does not solve the problem, maybe i need to reboot the system to release the profiles but therefore i have to wait till the evening!

     

    Till that time do you know what can be the problem with the error logged about the registry?

     

    Thanks Robin

     

  • Tuesday, December 11, 2007 2:45 PM
     
     

    A reboot to apply the new security will not be necessarily. To be honest I’m afraid I can’t help you here. I have no clue at all.

     

    I suggest to check every component from the start. The profiles, the TS settings, the GPO’s.

     

    Maybe this will help you to check the profile settings:
    http://www.msterminalservices.org/articles/Managing-Terminal-Services-Group-Policy.html

     

    Good luck! Hopefully somebody else steps up here…