I believe you have a misconception about folder redirection. Folder redirection is typically used to get certain directories out of the user's profile and to a network storage. Either because it is a roaming profile and the directories tend to grow fast and increase profile load times or because it is (and has to stay) a local profile but the user needs to roam and take a subset of her files with her. In an overwhelming number of cases, this is a one-time per-user process - once the redirection has been set up and the files have been moved out of the profile to the destination directory, they stay there.
I personally know of no case where folder redirection settings are applied via a loopback policy to be valid only on a set of machines so users roaming out of this set would have the redirection settings reversed again. If I were to implement such a thing, I would raise concerns regarding stability and usability of the setup.
If you really need this however, you might to a degree simulate what group policies are doing in loopback processing mode by providing different policy files based on the host NetBIOS name:
- create different
netlogon directories for each of your domain's hosts like
/share/samba/netlogon/winws01 for the client named
winws01, use symlinks to create sets of identical policy configurations and create links to logon scripts you might be using
- place pre-created ntconfig.pol files carrying different settings for folder redirection in those directories as desired
- set up the
netlogon service in smb.conf to use a dynamic path depending on the client's NetBIOS name:
path = /share/samba/netlogon/%m
read only = yes
guest ok = yes
%m macro in the path specification would resolve to the client's NetBIOS name. This way, upon user logon, the Windows client connecting to
netlogon and looking for the policy file (ntconfig.pol), would indeed be served from
/share/samba/netlogon/<clientname>, allowing you to specify different policy files for different clients.
Note that "redirecting" by just re-setting the destinations in the registry as is being done by NT4-style policies would not move files - you would have to take care of this by yourself (typically through logon scripts). It also would not be easily reversible as previous values of the overwritten registry keys are not saved anywhere.