A
armopop
Hello there;
two days ago i downloaded the 2X publishing and balancing server, installed, configured and tested it in a lab, an overall of 10 minutes and i was having the apps installed or published on my server right on my laptop running like a charm. So i decided to install it on a production server, boy o boy, no matter what i do, i'm always getting a terminal server login windowd instead of having the application running on the client. I'm totaly stumped, both the lab and the production server have the exact same setup, except that the lab server was a RDP and the production server is a full Windows 2003 terminal server. I red some posts and i found out that one of the major causes for this, is users having a program to run upon logging, well in my environment, there are no programs to run upon logon, so what is going on? Am i missing some config on the server, weirdly enough, now when i go back to my lab server, it does the same thing?
two days ago i downloaded the 2X publishing and balancing server, installed, configured and tested it in a lab, an overall of 10 minutes and i was having the apps installed or published on my server right on my laptop running like a charm. So i decided to install it on a production server, boy o boy, no matter what i do, i'm always getting a terminal server login windowd instead of having the application running on the client. I'm totaly stumped, both the lab and the production server have the exact same setup, except that the lab server was a RDP and the production server is a full Windows 2003 terminal server. I red some posts and i found out that one of the major causes for this, is users having a program to run upon logging, well in my environment, there are no programs to run upon logon, so what is going on? Am i missing some config on the server, weirdly enough, now when i go back to my lab server, it does the same thing?