Disabling logins to a specific 2x terminal server

Hi guys, great product, love it. Question:

We have a dedicated gateway and three terminal servers. One of the terminal servers has some misbehaving software which needs to be fixed. Clearly we don't want people running the software while we're fixing it.

How do we disable logins to a specific terminal server for the problem application?

I went into publishing on the gateway machine and changed the publishing for that app from 'all servers in the farm' to 'individual servers' and excluded the problem server from publishing. However this server still received an incoming connection for that application.

Any ideas?

Kind regards, Jules

 

Hi there,

I suggest that the best thing to do is to delete the published application.

In the future one will be able to disable applications from being published.

Nixu

 

We have three terminal servers, one of which has a problem. this solution would mean taking the entire application offline across all three servers. This is the shotgun approach; what i am looking for is the sniper approach

When i changed the publishing for the application from all servers to only 2 selected servers, users were still being sent to the 3rd server. Why is this the case? do i need to restart some 2x services for it to realise i've changed where the applications are being published from?

What is the effect of stopping the 2x terminal server agent on a terminal server?

 

Hi there,
Sorry i misunderstood your question... I thought you wanted to remove the application completely.

Well for the application server to make use of the new settings all you have to do is to press the apply settings from the console.

If you remove the Agent from the terminal server then this server would not be used for publishing and Loadbalancing

I will take a look at the issue you are mentioning and let you know.

Nixu

 

OK matey, thanks; i look forward to your reply

Kind regards, Jules

 

Hi Julius.Roberts,

I tried it out and I did not manage to reproduce your issue...
I guess it is some miss configuration..

What i can suggest is to enable the log file & debug information, run the some tests where application X is being executed on server that should not be executing from, and send a support request from the console.

Nixu

 

ok, no worries, will do. Thanks for your assistance, i appreciate it

Kind regards, Jules