[THIN] Re: OT: Applying 2003 GPO on NT4.0 Domains

  • From: Bill Beckett <Bill.beckett@xxxxxxxxxxxxxxxxx>
  • To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
  • Date: Mon, 25 Oct 2004 11:18:30 -0400

The only thing necessary to use flex profiles would be the TS profile
location reading \\server\share\%username%\%osv%
<file://\\server\share\%username%\%osv%> .?? (Assuming roaming profiles were
already being used)


-----Original Message-----
From: Rick Mack [mailto:Rick.Mack@xxxxxxxxxxxxxx] 
Sent: Friday, October 22, 2004 4:31 PM
To: thin@xxxxxxxxxxxxx
Subject: RE: [THIN] OT: Applying 2003 GPO on NT4.0 Domains


Hi Bryan,
 
The policies will appy to the users if you use loopback processing on the
group policy for the Citrix server OU.
 
This will apply the user configuration opart of the Citrix servers GP to
anyone logging on to the machines, regardless of their parent domain. 
 
Domain trust issues aside however, the one obvious thing you're going to
have to avoid is allowing ay 2003 profile mods to be written back to the
users' profiles. Things can get ugly at times when the NT 4.0 explorer sees
all those extra settings ;-)
 
Provided they don't have any TS systems of their own, simply assigning them
a TS profile location will take care of things. However if they already have
TS profile locations asigned in their parent domain things are a bit more
challenging.
 
The way we've handled NT 4.0 /2003 profile transitions is to use flex
profiles, and use a system variable (eg assign OSV=NT4 to NT 4 systems,
OSV=win2k3 to Windows server 2003 systems) so that the user's TS profile
location was \\server\share\%username%\%osv%
<file://\\server\share\%username%\%osv%> . That way the flex profile could
be used to copy relevant information between the 2 different versions of the
profiles.
 
This worked really well since it was able to conserve printers and
application settings and avoided almost all the migration issues.
 
regards,
 
Rick
 
Ulrich Mack
Volante Systems

  _____  

From: thin-bounce@xxxxxxxxxxxxx on behalf of Bergman, Bryan
Sent: Sat 23/10/2004 12:21 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] OT: Applying 2003 GPO on NT4.0 Domains




I have 4 MF XP / Windows 2003 servers located in a Windows 2003 domain.
However, the users that are going to be accessing the Citrix servers are
in an NT 40 domain.  I want to create a GPO on the CitrixServer OU that
will lock down the desktop, hide drives, etc.  I have a trust
established with the 2 domains.  However, I create the policy, run a
GPUpdate on the Citrix servers but the policy doesn't take effect.  Of
course, any accounts that are created in the 2003 domain, the policy
takes effect.  Question: Does group policy traverse to NT 40 domains?
Is what I am trying to do feasible?  If so, can someone throw me a bone?
I figured I would try to ask the knowledge of magnitude encompassed in
the Thin List rather than calling M$.  Thanks in advance

Bryan
********************************************************
This Weeks Sponsor RTO Software
Do you know which applications are abusing your CPU and memory?
Would you like to learn? --   Free for a limited time!
Get the RTO Performance Analyzer to quickly learn the applications, users,
and time of day possible problems exist.
http://www.rtosoft.com/enter.asp?id20
<http://www.rtosoft.com/enter.asp?id20> 
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm <http://thin.net/links.cfm> 
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm <http://thin.net/citrixlist.cfm> 


############################################################################
#########

This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has
been sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it
in error please notify the sender immediately by reply e-mail and destroy
all copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby
disclaimed to the extent permitted by law.

############################################################################
#########

############################################################################
#########
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has
been sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it
in error please notify the sender immediately by reply e-mail and destroy
all copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby
disclaimed to the extent permitted by law.
############################################################################
#########


Other related posts: