BP, WA or solution to avoid AppData redundancy across Windows versions?
in roaming environment multiple windows client versions can "benefit" profile version extensions (like v2, v3, v4, maybe v5). better breaking profiles mutual overwriting through different client versions.
anyway: not better, worse, default of maintaining ...\profile.vn\appdata\roaming\$program entries. @ least identical software versions, office others.
in linux setup, move (or user's) appdata\roaming subfolders (at least app versions identical across client os version) maybe $userpath\globalapps (or likewise) , link them profile.vn\appdata\roaming folders (all of said happen on server profile share.)
any client subsequently resolve link (at least default if server-side hard-link) , transparently sync data structure behind it, never knowing actual data not part of profile.vn version linked.
since windows' mklink whatever reasons not allow hard-linking directories files, , since junctions not followed in sync process (at least default, seems), current best practice or workaround achieve goal?
and (less important nice know) windows server equivalent providing hard-linked directories seen , treated transparently clients, appearing normal folders in way?
thanks constructive idea :)
hi,
currently cannot find solution works hard link. how using roaming profile and/or folder redirection data stored in same server?
please remember mark replies answers if , un-mark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com.
Windows Server > File Services and Storage
Comments
Post a Comment