J
Judg
Guest
I hope someone can help me on this one.
I our Environment the homefolder is set within the userobject in AD.
Now as we are an International organisation, people from all over are
connecting to our datacenter using Citrix and Terminal Services. We saw that
the mapping of the homefolder is decreasing the performance of the servers.
To stop te mapping of the Homedrive which is set in the user profile, we
created a local policy on the server to set the Terminal services home drive,
as it overrules the home directory setting in the user object. I have tested
this on one server and it is working as expected, now i was trying it on
another server and there it does not seem to work.
I can see that the local policy is applied, but when i open the explorer is
still see the home drive mapped too the server as set in the userobject.
Again according to my knowledge and supported by numerous MS articles, it
should work.
In a test environment a placed a policy with that setting on the OU lvl, and
there i get the same strange behaviour. On one it works while not on the
other (both servers residing in the OU where the policy is applied to).
--
Do Not Followe Me, I''''m also lost!
I our Environment the homefolder is set within the userobject in AD.
Now as we are an International organisation, people from all over are
connecting to our datacenter using Citrix and Terminal Services. We saw that
the mapping of the homefolder is decreasing the performance of the servers.
To stop te mapping of the Homedrive which is set in the user profile, we
created a local policy on the server to set the Terminal services home drive,
as it overrules the home directory setting in the user object. I have tested
this on one server and it is working as expected, now i was trying it on
another server and there it does not seem to work.
I can see that the local policy is applied, but when i open the explorer is
still see the home drive mapped too the server as set in the userobject.
Again according to my knowledge and supported by numerous MS articles, it
should work.
In a test environment a placed a policy with that setting on the OU lvl, and
there i get the same strange behaviour. On one it works while not on the
other (both servers residing in the OU where the policy is applied to).
--
Do Not Followe Me, I''''m also lost!