While we are doing something similar in production our system is MUCH smaller that yours. Having said that - are you not currently using UDP in your existing setup? If this is working OK it should be fine with your proposed migration. Yes it is true that using pure TCP+HTTP would be a better option than having to use UDP broadcasts but so what - sometimes we just have to use what we have got! The only issue I have seen on our system (MFXPe+FR2 on W2k+SP3) is that the farm setting for Data collectors respond to ICA Client broadcasts regularly turns itself off (we do not have any 1.8 servers) - this did catch me out untill I turned on the setting on some of our production servers - since then no problems. You will still have to deal with things like UDP across different subnets - but it is not like you are new to all this. -Ec -----Original Message----- From: Rob Slayden [mailto:rslayden@xxxxxxxxxxxxx] Sent: Thursday, 25 March 2004 9:37 a.m. To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Ramifications of UDP in MFXP farm What I am testing now is the scenario after all MF 1.8 servers have been updated (rebuilt actually). So, no MF 1.8 servers. Are you saying then that what I have implemented (in the test lab) is the correct configuration for my client environment and I can expect this to work in a satisfactory manner from an MF infrastructure and user experience perspective, or is there a downside to maintaining my MF infrastucture with UDP Browse Listeners? Is anyone running a good-sized environment in this configuration now without any issues (25+ servers, 4000+ users, single app)? I realize that a pure TCP+HTTP browser configuration would be the most optimal, but we are a long way from updating 2000+ clients to an ICA version that supports that protocol. What I am hoping to find out is what are the negative aspects I can expect to experience in this configuration, if any, and what I might be able to do to lessen them. Once I pull the trigger on the production MF farm, there literally will be no turning back without a tremendous amount of pain. I don't want to find out 6 weeks down the road that this is a bad, bad thing. Anyone doing this in production now without issues? Thanks! rob -----Original Message----- From: Shonk, Joe - Perot [mailto:JShonk@xxxxxxx] Sent: Wednesday, March 24, 2004 1:14 PM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Ramifications of UDP in MFXP farm You also have to set the Farm/Server to respond to ICA Client broadcast messages. If you are running MF 1.8 on the same broadcast domain, the Farm setting will be disabled this settings and you wil have to resort to Interoperability mode. In addition you will want to enable the UPD Listener (assuming your running TCP/IP and not IPX, Netbios) Joe -----Original Message----- From: Rob Slayden [mailto:rslayden@xxxxxxxxxxxxx] Sent: Wednesday, March 24, 2004 12:12 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Ramifications of UDP in MFXP farm Steve, We do have Wyse Management software, both Remote Administrator 3000 and Rapport, but you cannot push configurations to terminals with Rapport unless they are on firmware version 369.20 or above and you cannot manage multiple subnets simultaneously with RA3K. At least half or more of our 4000 terminals are 289.14 so they would have to have firmware upgrades to be Rapport-manageable. The terminals are currently configured for TCP and 3 IP addresses (MB and 2 BBs), but unless the ZDC or the MF servers being "hit" by the terminal has UDP Browser Listener enabled, the MF server does not respond to directed TCP access by the terminals. At least, that is the behaviour I am observing in the lab in testing Interoperability mode and then converting to "native" MFXP mode. If I access the ZDC from the termial in TCP mode and it does NOT have UDP Browser Listener enabled, it does not seem to respond. If you are saying it is supposed to respond to that, then maybe there is some other configuration parameter that is not correctly configured. I have Interoperability Off, UDP Browse Listener enabled ONLY on the ZDCs, MFXP servers only (MF 1.8 servers are powered off). I tested from multiple versions of firmware (i.e., mutiple client versions) and even in ICA 7.1, it did not find the pub apps in TCP mode without UDP enabled. Am I doing something wrong here? Thanks! rob -----Original Message----- From: Steve Greenberg [mailto:steveg@xxxxxxxxxxxxxx] Sent: Wednesday, March 24, 2004 10:50 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Ramifications of UDP in MFXP farm Do you have WYSE management software? Can you add an IP address or = Server name for polling the farm (i.e. in ICA syntax TCPBrowser=3DZDC)? I think = this will work without needing UDP available since it won't try to broadcast, rather, it will ask the ZDC directly for it's list of published apps.... Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax=20 steveg@xxxxxxxxxxxxxx -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On = Behalf Of Rob Slayden Sent: Wednesday, March 24, 2004 11:13 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Ramifications of UDP in MFXP farm I am upgrading a 27-server NT 4.0-TSE/MF 1.8 farm to W2K3/MFXPe and I = have been testing the migration in the lab. It appears that I will still = require the ZDCs (farm will have 2 zones) to maintain UDP (Server-->MF XP = Settings -->ICA Browser - Create browser listener on UDP network). In testing,=20 -->when in "native" mode (interoperability off), if this setting is unchecked, = my terminals doing directed TCP access for published applications fail to = find the master browser (ZDC). As long as the box is checked on the ZDCs, the terminals can not only get the list of pub apps, but they can also be routed to MF servers that are not configured as UDP browser listeners. As I do not want to change the configuration on 4000 Wyse terminals to update the Server Location and Protocol from TCP to TCP+HTTP, = particularly since it would require firmware upgrades to half of them, what are the ramifications to running my farm with the UDP browser listeners = configured on the ZDCs? How will this affect performance and session initiation response time? I do not know how many users are connecting/disconnecting = at any given moment, but I know a typical user load ranges anywhere from = 2100 to 2800 users, though the potential user base is closer to 4000. Any thoughts or suggestions for ensuring optimal performance in my environment would be greatly appreciated. Thanks, Rob 24 Hour Fitness ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting = integration firm in the nation. Emergent OnLine delivers expert=20 consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: 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 ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: 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 ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: 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 ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: 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 ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: 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