Loopback is great for terminal servers. For example, you may have a domain policy that sets a specific screen savor to run on all systems. However, when the users logon to your terminal servers, you may want a different screen savor or none at all. What loopback does is apply the user policy settings when a user logs into a particular system that is in an OU rather than using the OU's that the user's account is in only. Loopback only replaces policies from higher OU's if the collide. -----Original Message----- From: Evan Mann [mailto:emann@xxxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, December 01, 2004 11:59 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Loopback Right, I realize you CAN override, but does it FORCE an override for an entire GPO or just specific settings? I'm a little confused as to why use loopback at all? To enable loopback on specific machines you'd need to create an OU and put those machines in it. Once you have this setup, any GPO applied on that OU will have precedence over any domain OU. So why enable loopback if you can just do your overrides natively with GPO precendence order? Or am I just missing something obvious? _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Frank Monroe Sent: Wednesday, December 01, 2004 11:47 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Loopback It depends how you do it. Loopback will override settings at a higher level if they are also set at the loopback level. -----Original Message----- From: Evan Mann [mailto:emann@xxxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, December 01, 2004 11:41 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Loopback Does loopback force override or just allow it? So to enable loopback on specific machines you have to put a TS/Citrix box in a dedicated OU with a GPO to enable loopback, correct? Now lets say I have a domain level OU to enable screen saver after 5 mins. Does this still apply to the TS/Citrix OU with loopback on? _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Bill Beckett Sent: Wednesday, December 01, 2004 11:34 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Loopback Ahhh, that just answered my Win98 question. Thanks Ron. -----Original Message----- From: Ron Oglesby [mailto:roglesby@xxxxxxxxxxxx] Sent: Wednesday December 01, 2004 11:31 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Loopback One thing in that sentence. "the client" is not the Citrix/TS client, it is the Terminal server. Ron Oglesby Senior Technical Architect Microsoft MVP, Windows Server RapidApp, Chicago Office 312.372.7188 Mobile 815.325.7618 email roglesby@xxxxxxxxxxxx <mailto:roglesby@xxxxxxxxxxxx> -----Original Message----- From: Lilley, Brian [mailto:brian.lilley@xxxxxxxx] Sent: Wednesday, December 01, 2004 10:27 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Loopback correct... -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Bill Beckett Sent: 01 December 2004 16:20 To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Loopback Just want to hear from the list and make sure that I am understanding this correctly. With loopback processing, say on a Terminal Server, the user policy inherited from the domain can be over-ridden by the policies of that on the Terminal server box. However, it does not work if the user account is in an NT domain OR if the client is not a Windows 2000 client??? Is that accurate? ============================================================================ == This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ============================================================================ ==