According to what I have read and been told I should be able to load the 2x TS agent on a Windows 2000 server. I have already loaded everything I need on a 2008 server, but need the agent on one of our 2000 servers. The 2000 server is running TS and can be seen from the 2x 2008 server, but when I try to install the agent on the 2000 server I get 2X Application Server XG setup wizard ended prematurely. I have tried remote install from the 2008 server through 2x, fails. I have copied the msi to the 2000 server, run setup, choose installation type Custom, selected 2x TS agent, failed. Ran change user /install, failed Ran change user /execute, failed Nothing in event logs except msi failed. Any words of wisdom (besides upgrade 2000 server)?
I think contacting support might be wise so they can check the install log for you. v10.5 should still support windows 2000
I have contacted support and there seems to be a little confusion. According to email I received W2000 is not supported in 10.5; however, received another email over the weekend saying they would check. At any rate I downloaded version 10.1 (1263) over the weekend and tried that. Installed on 2008 server, all okay. Installed 2X agent on 2000 server, all okay. Set everything up, all seems okay. Installed client on XP Pro machine, all okay. Identified published application on 2008 server (app resides on 2000 server). When I access application from XP machine, connection is made to 2008 server, but I get a sign on screen for the 2000 server. If I sign on to 2000 server published app starts fine. On XP client I have for Connection properties I have entered the user name and password, auto logon is checked. On 2008 server RDP Use client provided log on information is selected, Always prompt for password is not selected. On 2000 server RDP Use client provided log on information is selected, Always prompt for password is not selected. I have Citrix Metaframe set up on the 2000 server, with a published app. When I connect from the same XP machine using the Citrix client to the 2000 server I do NOT get the sign on. So, I am pretty close to getting this all to work, but need to eliminate the 2000 sign on screen if possible.
Update, I was thinking there was a connection/security issue between the 2008 and 2000 server, so I uninstalled 2X from the 2000 server, reinstalled full 2x back on the 2000 server, removed 2x connections on the 2008 server that referenced the 2000 server, created new 2x client connection on the XP machine. Still get same results, get sign on screen for the 2000 server. So at least I can eliminate the 2008 server from the equation.
Maybe there is the server side setting enabled to always prompt for password within the terminal services configuration or within a group policy that is applied to your w2k with TS enabled?
Sorry, I have been a little remiss in posting my results. I have the problem. On the 2000 server, TS configuration, RDP-TCP properties, Use standard Windows authentication must be checked. All works fine now. Thanks for suggestions and assistance.
