Program Neigborhood and Thin Client Winterms

[bcsinc]

I have some Wyse 2500T winterms that I want to connect to a citrix server, NT 4.0 TSE, MF 1.8 SP3, via Program Neighborhood. I don't want my users to have a desktop. From what I have researched, there are three ways to make this connection. 1) Through the command line of the connections properties of the winterm. 2) Through the command line in the advanced settings of the edit connection in terminal server connection configuration. 3) Through the command line on the users config tab in users properties of the user manager.

My first choice was 3, to point to the pn.exe from the users config. When I do this, after login, I get the PN to open with all my application sets visable. But, when I select an application set to open, another PN session opens. Every time I select an application set another session opens. I don't understand why this is.

My second choice was 1 because I don't want every user who connects to open a PN session as would happen in the second choice. When I point to the pn.exe from the winterm's command line the program seems to work fine but blue screens the server if I try to open more than one node at a time.

I still prefer to get this to work from my third choice above. Any thoughts or suggestions would be appreciatted.

Thanks in advance!

Jim

 

[CitrixEngineer]

Have you tried 4) Publish Program Neighborhood as an application on the Citrix server and point the Winterms to that instead of the server? Or 5) Publish a desktop which uses pn.exe as the shell instead of explorer.

...or don't these particular Winterms have Published Applications as a connection option?

In which case, you could try 6) Create a desktop especially for Winterm users, editing the profiles and policies as necessary so that when Winterm users log in, the desktop uses pn.exe in the same way I described above.

Hope this helps CitrixEngineer@yahoo.co.uk

 

[br0ck]

I'm having an issue with a 2k3 CTX XPFR3 server and winterms
i have PN.exe published as an app but when the client connects to it the application set auth fails


this happens with all user accounts including the administrator

? any ideas

 

[br0ck]

hehe me=stupid


there is an old 1.8 server that auto configs pn and it's in a diffrent domain

no wonder it fails