I have a situation that has been perplexing us and has caused the server farm migration to come to a halt until we can resolve it. What is happening is this:
We have a Citrix server farm of NT4.0 TSE and MetaFrame 1.8 that we are migrating to Server 2k3 and MetaFrame XPe. We have all the backend servers upgraded and interoperability enabled to emulate our old 4.0 Domain while we migrate users over to the first 2k3 XPe server. All was going well until one day our clients started getting errors when they would try to logon in the morning that said it could not find the published application. We basically point our thin clients to a published full screen desktop in this setup and never had an issue before. If you edit the properties of the published desktop connection you can browse the list of published applications on the master browser and select the one you need. In most cases if you just keep trying or play around with it enough you can get it to connect. In other cases we have had to force the users connection right to the desktop of the server and not use the published app. They never get an error anymore once that is done but obviously that wont work out to well when we want to add more servers and load balance them. This happens to several different types of thin clients as well as fat clients with various versions of the ICA client including the latest builds.
We have the ICA listener connection count set to 3 as that always worked in the past but have ruled this out anyway because the problem can happen at any time in the day even if only one person is trying to connect. It is sporadic but frequent.
Any help at all will be greatly appreciated!
Thanks in advance for any replies.
Mark
We have a Citrix server farm of NT4.0 TSE and MetaFrame 1.8 that we are migrating to Server 2k3 and MetaFrame XPe. We have all the backend servers upgraded and interoperability enabled to emulate our old 4.0 Domain while we migrate users over to the first 2k3 XPe server. All was going well until one day our clients started getting errors when they would try to logon in the morning that said it could not find the published application. We basically point our thin clients to a published full screen desktop in this setup and never had an issue before. If you edit the properties of the published desktop connection you can browse the list of published applications on the master browser and select the one you need. In most cases if you just keep trying or play around with it enough you can get it to connect. In other cases we have had to force the users connection right to the desktop of the server and not use the published app. They never get an error anymore once that is done but obviously that wont work out to well when we want to add more servers and load balance them. This happens to several different types of thin clients as well as fat clients with various versions of the ICA client including the latest builds.
We have the ICA listener connection count set to 3 as that always worked in the past but have ruled this out anyway because the problem can happen at any time in the day even if only one person is trying to connect. It is sporadic but frequent.
Any help at all will be greatly appreciated!
Thanks in advance for any replies.
Mark
