|
Posted by Steven L Umbach on August 15, 2005, 5:38 pm
Please log in for more thread options I also found this reference to a registry mod that can change the default
location of user profiles for normal interactive logon. If you want to try
it I suggest that as always for best practice that you make a full backup of
your server first. You may also want to post in a Windows Terminal Server
newsgroup to see if such a registry mod has been successfully used or if
they have other advice. --- Steve
http://windows.about.com/od/tipsarchive/l/bltip212.htm
Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows NT\CurrentVersion\ProfileList
Name: ProfilesDirectory
Data Type: REG_EXPAND_SZ
Value: path
Please be sure to back up your Registry and your current Profiles before
making changes. Also note that this will only take effect for users logging
in after the change to the Registry. You may also have to copy the Default
User profile to the new location.
> Hi Mike.
>
> I think the problem is that you used d$ in the share path. D$ would be a
> hidden administrative share that only administrators can access. If you
> create a share for what you want to do just list it in the path such as
> \server-name\Terminal assuming terminal would be the name of the
> are. --- Steve
>
>
>> I'm setting up a few people with rights to access our server via Remote
>> Desktop. This is on Server 2003, which is also PDC. I don't want
>> profiles to be stored on the C:\ drive for space considerations, so I
>> have created a folder on the D: drive for Terminal Services Profiles. In
>> each users profile, I add the path to this location in the Terminal
>> Services Profile Tab
>> ex: \server-name\d$\Terminal Services Profiles\username
>>
>> Somehow, I've messed up the security on these folders. Now, when one of
>> the users that is not a member of the Domain Admin group tries to log in
>> they get a message saying:
>>
>> ---------------
>> Windows cannot locate the server copy of your roaming profile and is
>> attempting to log you on with your local profile....possible cause of
>> this error include...or insufficient security rights.
>>
>> Detail - Access is denied.
>> ---------------
>>
>> Here are the permissions on the top level folder:
>> Administrators: full
>> Creator Owner: Special- create files/write data create folders
>> Users: modify, read, execute, write, list folders, special
>>
>> Before I messed up the security, and I have no idea what I did, if I put
>> a path in the users TS Profile, a folder with their username would
>> automatically be create (I think). But now this will not happen - and if
>> I create the folder, I still get the error above.
>>
>> Any suggestions???
>>
>> Thanks,
>> Mike Bailey
>
>
| 
XML Sitemap