Set roaming profile path setting problem; is it a bug?


all,
we have set following path "set profile path users logging
onto computer" to:
\\servername\sharename\%username%.%userdomain%
(computer config\policies\windows settings\administrative
templates\system\user profiles)

the computer account object in nau-students. users can logon 2
domains nau-students or nau.
all users profile saved to:
\\servername\sharename\\%username%.nau-students, regardless of there
originating domain.
the problem have users same user name in both domains: eg
nau\plg9 & nau-students\plg9.
whoever logs on first roaming profile created, second user
profile service error , cannot logon.

if skip .%userdomain% in path same problem - profile created
first user \\servername\sharename\\%username% (no mention of domain in
path), user same username second domain cannot log on.
anyone know why doesn't work?
is design or bug? no guesses please - msft answer
helpful.

i have thought should correctly honor environment
variable?
this 2008 native domains , windows 7 rtm enterprise clients.

strangely setting works correctly, base:
windows components/terminal services/terminal server/profiles
set path ts roaming user profile
profile path \\servername\sharename
this policy setting correctly appends %username%.%userdomain%  path
without need specify.
thanks,
pete gomersall

if comes across post made, pleased hear microsoft accepted design flaw. microsoft have added new system environment variable named %userdomain_roamingprofile%. correctly evaluates user domain of user logging on. can used both rds roaming path , standard desktop roaming profile paths. details of fix can found here: http://support.microsoft.com/kb/2664408. environment variable has been included in windows 8 , server 2012.

pete



Windows Server  >  Group Policy



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group