Jump to content

Recommended Posts

Posted

We have remote sites here which are using 2X to connect back to our Windows Server 2003 R2 terminal servers.

 

We have separate issues with our TS's in that they are locking up (memory issues) which is causing the thinclients to lose connection to the farm.

 

This entails us having to go out to the remote sites and re-connect the machines.

 

Is there anything in the configuration of our thinclients that we can 'tweak' to enable automatic re-connection when our TS's go down?

 

We are still using ThinclientOS 6.0 (we can't upgrade due to hardware constraints).

 

Ideally of course, we need to sort out our TS's - an upgrade to Server 2008 R2 would be good, but the problem is, HP don't have a printer driver which a) supports all our quite old printers b) is 64bit, so we are at stalemate with that route.

 

My first priority is to find a way to auto re-connect our thinclient machines in the event the servers go down.

 

Anyone?

Posted
We was running 2003 Server on our TS box's and 2x worked perfect then I upgraded to 2008R2 and 2x just would connect correctly so ended up taking it off the system

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...