Comments in line Ron Oglesby Senior Technical Architect RapidApp Office 312.372.7188 Mobile 815.325.7618 email roglesby@xxxxxxxxxxxx -----Original Message----- From: Rob Slayden [mailto:rslayden@xxxxxxxxxxxxx] Sent: Tuesday, September 09, 2003 5:49 PM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Data Collector recommendations I have yet another design question as I am trying desperately to come up to speed on MF XP and its unique design elements. I believe I have all the elements for this small MF XP server farm determined with one exception: the data collector. I am looking through the Citrix doco and even Doug Brown's EXCELLENT MIAB 2.1 doco and I see no real hard-and-fast rules for the data collector. I see the recommendation to dedicate one DC for every 50 MF servers but at what point should this server become dedicated? RON: Way before 50, for sure is you are suing published apps and not desktops. My general rule of thumb is in the 10-15 range if using all published apps with a high app turnover. Not needed badly at that point but at 20 I would for sure have one. We dedicate a master browser to this function in our 27-server MF 1.8 farm. This is a Compaq 1850 doing nothing but functioning as the Master Browser. We also have 2 full-on production MF servers assigned to the Backup Browser funtion. Given that the new farm will be 5 servers running Windows 2003 and MF XP-FR3 with 300 users and 2 published applications, can I get away with using one of the production MF servers as the DC? Yes, 2 published apps and 5 app hosts. No problem. Also, what about a backup DC? This is set by the preference level in the zone tab in the properties of the farm node. One Most preferred, one preferred, and the rest default in a zone. Does it work the same as the old MF 1.8 where you simply click a radio button and now you have a backup DC? See answer above Thanks again for the advice! Rob Slayden 24 Hour Fitness, Inc.