G
Greg Candido
I have an all Windows 2003 network. 4 Servers in total, 2 are domain
controllers and 2 are terminal services servers with Citrix Metaframe
installed.
I have a user called Joe Doe and it roaming profile in AD is pointing to
\\server1\profiles$\%username%. Then I also have the same user Terminal
Service profile point to another location at
\\server1\TSProfiles&\%username%.
Now the senerio is as folows:
Joe Doe logs onto the Citrix server for the first time and it creates his
new roaming profile. But it creates it under this location
\\server1\profiles$\%username%. But its suppose to goto the terminal
services profile path of \\server1\TSProfiles&\%username%.
Why is it by passing the terminal services profile path and using the
standard roaming profile path. I though the execution was in this order
TSProflile path ---> First
profile path -------> Second
Local Profile Path --> Last.
Any Ideas why I can't get these two seperate profiles to work as seperate
entities.
FYI:
-Now all users have full permissions to my tsprofiles$ share.
-When I check the event viewer on the terminal server that the user is
logging onto I get the follow event error.
Event 1218: Failed to load Terminal Server Profile path. Note that the
profile path must be less than 256 characters in length.
Lastly, I know only the TSProfile path should take in effect if is a
citrix/terminal server. And my user is logging on to a terminal server but
loads the regular roaming profile which is his non TS profile.
Any ideas
controllers and 2 are terminal services servers with Citrix Metaframe
installed.
I have a user called Joe Doe and it roaming profile in AD is pointing to
\\server1\profiles$\%username%. Then I also have the same user Terminal
Service profile point to another location at
\\server1\TSProfiles&\%username%.
Now the senerio is as folows:
Joe Doe logs onto the Citrix server for the first time and it creates his
new roaming profile. But it creates it under this location
\\server1\profiles$\%username%. But its suppose to goto the terminal
services profile path of \\server1\TSProfiles&\%username%.
Why is it by passing the terminal services profile path and using the
standard roaming profile path. I though the execution was in this order
TSProflile path ---> First
profile path -------> Second
Local Profile Path --> Last.
Any Ideas why I can't get these two seperate profiles to work as seperate
entities.
FYI:
-Now all users have full permissions to my tsprofiles$ share.
-When I check the event viewer on the terminal server that the user is
logging onto I get the follow event error.
Event 1218: Failed to load Terminal Server Profile path. Note that the
profile path must be less than 256 characters in length.
Lastly, I know only the TSProfile path should take in effect if is a
citrix/terminal server. And my user is logging on to a terminal server but
loads the regular roaming profile which is his non TS profile.
Any ideas