Just my best practice... BUT when I start out with a new OS and new test domain I generally have them off the production wire and isolated. Once I figure them out a little bit I may hook them into the prod network but will keep them on their own VLAN or even separate them with only a multi-homed transfer server between the two networks. (I sue the transfer server to get files back and forth between the two. This keeps any problems from happening and keeps people from blaming my test environment for their problems. Just my two cents Ron Oglesby Senior Technical Architect =20 RapidApp Office 312.372.7188 Mobile 312.961.2380 email roglesby@xxxxxxxxxxxx =20 -----Original Message----- From: Stansel, Paul [mailto:Paul.Stansel@xxxxxxxxxxxxx]=20 Sent: Wednesday, February 05, 2003 8:38 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Semi-OT: Configuring a Server 2003 test bed We're still running (and likely will be until the sun explodes and the whole earth melts) a flat NT4 domain. That being said, I want to buck the system and install a test bed for Server 2003, including creating a small AD configuration. Does anyone have any advice on whether this should be segmented in any way from the rest of the environment? Will I start causing problems for the NT domain if the AD domain is on the wire as well? Thanks, Paul ******************************************** This Week's Sponsor: triCerat Inc. Let triCerat simplify the administration=20 of your Terminal Servers. http://www.triCerat.com ******************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm ******************************************** This Week's Sponsor: triCerat Inc. Let triCerat simplify the administration of your Terminal Servers. http://www.triCerat.com ******************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm