local vs romaing clarification.
i have a user who has an office in england and an offiice in loas angeles. this user is coming over here to lat and needs to have access to temp system here.
network drives are mapping normally all logon scripts are running.
here is my question:
when the user logged onto his (test) laptop here windows slow link detection came up and said "youre are running slow" do you want to doanload your profile or do you want to use local?
I chose to use local, if that same user logs on to a faster conection, will windows re-prompt him to download his profile? or is this a set it once and forget it?
assuming that windows would ask him again, i set the profile to "type - local" and "status = local, was already set by winodws"
and lastely, if i use a local profile as described in this scenario, will that profile ever be able to sync changes to the servers copy of the users profile?
Please advise...
Robert
network drives are mapping normally all logon scripts are running.
here is my question:
when the user logged onto his (test) laptop here windows slow link detection came up and said "youre are running slow" do you want to doanload your profile or do you want to use local?
I chose to use local, if that same user logs on to a faster conection, will windows re-prompt him to download his profile? or is this a set it once and forget it?
assuming that windows would ask him again, i set the profile to "type - local" and "status = local, was already set by winodws"
and lastely, if i use a local profile as described in this scenario, will that profile ever be able to sync changes to the servers copy of the users profile?
Please advise...
Robert
Also, if you try to hook the user up to a faster connection, make sure to save all the documents/files that the user worked on to the network drives that are mapped, because those temp local profiles are sometimes wiped and you would lose that data. After doing that, reboot the machine and you should either get the profile downloaded like normal or at least re-prompted again to use the local one.
ASKER
wait i thought you said that it was a cached answer and that the user would not be re-prompted to use the local profile again?
your fist post was clear your second is confusing...
please clarify...
Robert
your fist post was clear your second is confusing...
please clarify...
Robert
ASKER
also, if you mentioned that the local profile will never be copied up over the server profile, is this by default or does it require a gpo setting. there is a gpo setting which describes this in this (or something like it) microsoft document:
http://technet2.microsoft.com/windowsserver/en/library/9fa19668-626c-463e-9812-fa46e85c787b1033.mspx?mfr=true
http://technet2.microsoft.com/windowsserver/en/library/9fa19668-626c-463e-9812-fa46e85c787b1033.mspx?mfr=true
I'm sorry that my answers were confusing, seems there's much more to the subject than just my experience so I went out and looked some stuff up.
In your situation, you are correct that the group policy of your domain allows the user to be prompted about the downloading of the local profile and that it also determines other settings in the way it functions. I'm not sure what systems you are running, but make sure that "Delete cached copies of roaming profiles" is not enabled in GP. This is what I was referring to when it came to local copies "disappearing", because with this setting, all the files that were saved are deleted on logoff. It is a way to save space on machines, but if you are using a temporary local profile, it will get deleted before getting a chance to update the roaming one.
From the research I did, it appears that if the user re-establishes the connection to the server holding the profile information, the roaming profile and any locally stored profile will merge.
The reason I said to backup any newly saved files in my second post was because in my experience it is very easy for this "merge" to yield unexpected results. Always better to be safe than sorry! Also, I am sorry for seemingly contradicting myself with this latest comment, but my previous answers were assuming it was using a temporary local profile that was erased upon log off, which should not be the case but I would still be careful.
In your situation, you are correct that the group policy of your domain allows the user to be prompted about the downloading of the local profile and that it also determines other settings in the way it functions. I'm not sure what systems you are running, but make sure that "Delete cached copies of roaming profiles" is not enabled in GP. This is what I was referring to when it came to local copies "disappearing", because with this setting, all the files that were saved are deleted on logoff. It is a way to save space on machines, but if you are using a temporary local profile, it will get deleted before getting a chance to update the roaming one.
From the research I did, it appears that if the user re-establishes the connection to the server holding the profile information, the roaming profile and any locally stored profile will merge.
The reason I said to backup any newly saved files in my second post was because in my experience it is very easy for this "merge" to yield unexpected results. Always better to be safe than sorry! Also, I am sorry for seemingly contradicting myself with this latest comment, but my previous answers were assuming it was using a temporary local profile that was erased upon log off, which should not be the case but I would still be careful.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
However, changes made to the temp local profile will NOT synchronize over to the roaming profile.
Also be aware that if he tries to login to the same computer that they chose to use a temp local profile, it often caches that decision and will continue to log them into that temp local profile, without even prompting to use the roaming. That is only on that same machine though.