Tuesday, July 22, 2008

[THIN] Re: Loop back processing

hit reply before I could finish hehe...

anyways example loopback:

-Create an OU, put terminal servers within the OU. Depending on the number of servers involved, make a windows group for the terminal servers. 
- create a policy on the new OU, disable user processing within that policy, enable loopback, set any other needed computer side values within the policy, apply the policy to the terminal server security group.
- create another policy in the new OU, disable computer processing within that policy. Define all user settings required, assign the policy to your user groups that will be logging into the terminal servers.

I prefer to seperate computer and user policies, but they don't have to be.

HTH

Lan
 

On Tue, Jul 22, 2008 at 8:43 AM, TSguy92 Lan <tsguy92@gmail.com> wrote:
HI,

Loopback only applies to the "user" settings of a policy, "computer" settings still process normally.

Loopback ensures that only the User settings defined within policys on the OU where loopback is enabled will affect the users that log into machines within that OU. User settings from other policys do not apply to the OU with loopback enabled on it.

For example, here's how I typically setup a terminal server OU with loopback.





On Tue, Jul 22, 2008 at 3:54 AM, Hamilton, Ronnie <ronnie.hamilton@ltai.ie> wrote:
HI,
 
Sorry having a little bit of trouble getting my head round this loop back processing or just need clarification in my thinking.
 
I haven't used this before and am faced with the possibility because of a Vista roll out.
 
All our users currently use thin terminals and connect to 2000 servers running metaframe XP.
 
I have the servers in an OU - with computers policy running against it.
The users are in a users OU - with computers policy attached to it.
 
So when they log in they get a combination of both.
 
Issue
    200 users are now going to initially use Vista because of one app that is coming from head office.
    I still need some of these users to access a published Desktop to access some apps form the Citrix boxes.
    Obviously the profile is going to have .v2 and all other users have roaming profiles.
    I have Vista Users OU and policy created fine.
    If I use loop back processing at the Citrix Servers OU and attach the original users policy to that OU does this mean that when the user logs into Citirx it picks up the original users policy and applies this.
 
I know a lot of these settings eventually end up in the users registry of roaming profile but my concern is if this profile gets corrupted on a new user is introduced that has never logged onto the old environment.
 
sorry for the long post.
 
thanks
 
Ronnie
 
Ronnie Hamilton CCNA
Lufthansa Technik Airmotive Ireland
Naas Road
Dublin
Tel : 01 4011253
LTAI
 
 

Visit our website : www.ltai.ie

__________________________________________

Lufthansa Technik Airmotive Ireland Limited. Registered in Ireland. Reg. No. 45999. Registered Office: Naas Road, Rathcoole, Co.Dublin.

Lufthansa Technik Airmotive Ireland Leasing Limited. Registered in Ireland. Reg. No. 140891. Registered Office: Naas Road, Rathcoole, Co.Dublin.

__________________________________________

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please advise by return email and delete all copies of the message.



No comments: