baturin

Oops, the problem appears to have very simple and elegant solution . Thanks to Frank Röder for his answer at http://www.microsoft.com/technet/community...91-1df618dedaca The key to success is to have some environment variable (say comptype=foo or comptype=foo2) on different machines and set profile path using ...\%comptype%\%username%\. That's all. I have tested and it works fine. Env variables can be set by OU-based group policy. I have made it through registry modification using DesktopStandard PolyciMakerRegistryExtension (free tool).

I have managed to add anvironment variable using DesktopStandard PolicyMakerRegistryExtension. I just forgot to install client side responsible for handling this extension of Group Policy on computer. Sure, the same can be done with writing custom adm template.

Hi! I have troubles to set environment variables (system level) using group policy in the AD domain. Is it possible or not? I have tried to make a startup script (bat file) for computer in group policy with "set var=value". The script itself launches, but new var didn't appears when I logon. I have also tried to set it also through registry modification CurrentControlSet->Control->SessionManager->Environment->Var=Value (using PolicyMaker Registry Extension). But with no result. I will be very glad if somebody can point me in right direction. Thanks a lot in advance!!!

Thank you for your response! Roaming profiles is needed because we don’t have two computers, but about 20 and 40/60 ratio of different computer types. So instead of 20+ local profiles I (and users) will need to manage only 2 of them. With favorites, My Documents etc redirected to server user profile itself will have mostly application settings. I agree, that modification of profile path each time can give a mess and it is not interesting in our case. The idea of modifying the same path into different for different computer is interesting. I should, at least, try it. The only contra about it is that we have just one server . Maybe, due to lack of elegant and standart solution it would be better to forget about that idea.

Thank you, just now it is clear. What you suggest is how to setup different paths for different users. Istead of this I need different profiles paths for same users logging on different computers. It seems that I should agree with RogueSpear: One possible solution I could see is to setup two domains, but this is really huge overkill in my case (for this I will need at least another one DC).

Could you give some more explanaton of this idea for beginner ? As I understand this right now: I need to place logon script to manipulate user preferences... Would it work if user will enter more than one computer at one time? Thank you!

Hi! The problem is to create, say two groups of computers (by mean AD Organization Units) and set for them different shares to store roaming user profiles. I can setup roaming profiles by usual way (create share, set permissions and write profiles path seting in user properties based on %USERNAME%). By I stuck with the following: how to make two different shares which will keep roaming profiles for different computers in domain? We have computers for different roles and different software installed on them. So, it would be ideal to setup different user profiles for them (all users are same for both types of computers). I have looked 10 times through group policy object for test OU I created (with one computer inside it), but haven't figured out anything that can help to solve the problem. I am not mature AD administrator and might be I overlooked something. I have created such thing with Samba NT domain under FreeBSD easily (share path which include machine name %m + using symbolic links). Does anyone setup similar configuration or can help me with it? A lot of thanks in advance!