What's the best way to handle TS Profiles in a cross forest trust situation?


i have users on thin clients log on desktop session our 2008r2 rdsh farm.  each user has ts profile follows them whatever server log into.  

we're planning switch our main line of business application hosted, , intend set cross forest trust allow our users log onto desktop session on host's rdsh servers existing accounts our domain.  as understand it, roaming profiles or gpo's our side of trust blocked default being applied on side of trust, correct?

if so, can host maintain separate roaming tsprofiles on side used when our users log on terminal servers?  assuming have multiple rdsh servers , connection broker load balance between them, not want our users have local profiles on each individual server might log in to.  

thanks!

hi,

it depends on how putting trust in place, , type of application been used etc.

if go down forest trust roaming profiles accounts domain if policies setup correctly - depending on link speed , profile size may not want happen, profile synced , every time user logs in.

you possibly @ folder redirection option.

of if application web based, or able become claims aware, may find better @ putting adfs trust in place.


regards,

denis cooper

mcitp ea - mct

help keep forums tidy, if has helped please mark answer

my blog

linkedin:



Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Popular posts from this blog

2008 Windows Deployment Server Properties Error

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

How do a find data in one file, search for it in another file and if not found, write a custom message to another file