J
Jeff
We have users on a stand-alone terminal server - Win2k3R2 Standard and their
profiles are not roaming but are local.
We are trying to move these users to a new terminal NLB farm with roaming
profiles. In the GPO for the terminal server farm the users roaming profile
is pointing to
\\ad.domain.com\central\TermProfiles\%username%
which is pointed to one location on a server that isn't part of the farm.
When we move a profile from the stand-alone server (which is a terminal
profile) to the roaming profile server (which is identical to the farm
nodes), the login of the user will create a folder username.domain under the
username folder which is there profile which of course isn't the correct
profile.
Question: if I change the roaming path to
\\ad.domain.com\central\TermProfiles and not include the %username% will it
see the profile that was copied to the location from the stand-alone? Is
there a way to migrate existing terminal server profiles to a roaming
location and have it work the same way without having to recreate the profile
from scratch?
profiles are not roaming but are local.
We are trying to move these users to a new terminal NLB farm with roaming
profiles. In the GPO for the terminal server farm the users roaming profile
is pointing to
\\ad.domain.com\central\TermProfiles\%username%
which is pointed to one location on a server that isn't part of the farm.
When we move a profile from the stand-alone server (which is a terminal
profile) to the roaming profile server (which is identical to the farm
nodes), the login of the user will create a folder username.domain under the
username folder which is there profile which of course isn't the correct
profile.
Question: if I change the roaming path to
\\ad.domain.com\central\TermProfiles and not include the %username% will it
see the profile that was copied to the location from the stand-alone? Is
there a way to migrate existing terminal server profiles to a roaming
location and have it work the same way without having to recreate the profile
from scratch?