Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, October 4, 2018 4:45 AM | 1 vote
We use the %logonserver% for mapping the location of user roaming profiles and mapped drives. When a workstation updates to 1809 the workstation cannot find the user's roaming profile and cannot map drives. If the workstation is reverted back to 1803 everything works. If you check the workstation's variables "Logonserver" is a listed variable and the correct server is associated with that variable.
All replies (7)
Thursday, October 4, 2018 7:12 AM | 1 vote
Same problem here, but with %USERNAME%
We're using a computer GPO to map all user profiles to \DFS\SHARE\USERNAME%. When logging on, a folder %USERNAME%.v6 (literally, no variable expansion) is created on the profiles share, and the user is being logged off immediately (due to the "log off users with temp profiles" gpo). This sucks :(
Friday, October 5, 2018 9:04 AM
Hi,
Thanks for your reply.
As I know, the roaming profile is on a sharing path, when you face the issue, can the user logging on access the sharing folder? And will it log on with the temporary profile?
After you check the %logserver%, did you mean that they can map to the right server, so the variable is correct, but just cannot work fine?
And, what the error message did you get? If possible, please take some screenshots.
What's more, how about other users who don't the roaming profile?
Look forward to your reply.
Thanks for your understanding and support.
Best Regards,
Otto Wang
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, October 5, 2018 9:19 AM
As I know, the roaming profile is on a sharing path, when you face the issue, can the user logging on access the sharing folder?
Yes, Access is possible after logging in, that's what he said
And will it log on with the temporary profile
Not if using the "log off users with temporary profile" GPO ist set
After you check the %logserver%, did you mean that they can map to the right server, so the variable is correct, but just cannot work fine?
The variable %logonserver% (or %USERNAME% in my case) does get expanded just fine *after* logon is complete, but not during the logon process while GPO processing and home drive mapping is happening
What's more, how about other users who don't the roaming profile?
On a machine with the "redirect all profiles" computer gpo, there is no non-roaming-profile users!
Friday, October 26, 2018 1:37 PM
Is there more information in this matter? We have the same problem. With the 1809 version, the GPO variables %logonserver% and %username% for the Central User Profile are no longer resolved. These are written to the registry of the client and thus can no longer find the server and the correct user profile path. Is it a bug that must be fixed, or maybe wanted (to force the Windows Enterprise version ;) ). Thanks for more answers.
Thursday, November 15, 2018 12:40 PM | 1 vote
The newly released November 2018 version of 1809 seems to have this bug fixed, amongst others. We just successfully tested deployment using the new build.
Friday, November 16, 2018 1:53 AM
Hi,
Thanks for your reply.
I am glad to hear that the issue has been fixed.
If you have any questions or requirements, please feel free to contact us.
Thanks for your understanding and support.
Best Regards,
Otto
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, November 16, 2018 2:38 PM
Thank you for the information. I understand the issue wit the new release of 1809 is that mapped network drives don't work, which is an even bigger issue for us.