Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[console]

Hi,

I am using ICE TCP Pro on a WinXP machine set to run macros at scheduled times, no problem.

Win XP TS has been enabled since I installed ICE TCP Pro. I recently used TS to check the status of a macro and then overnight ICE TCP Pro gave a load of erros about needing a thin client license because of using Terminal Services.

I can see why you would need an extra license if more people could use the program using TS but on Windows XP only 1 person can use the computer at a time either via TS or actually in front of the pc therefore there is no license violation.

Is there a solution to this, perhaps ICE recognising that Windows XP TS is still only 1 user per pc?

any other ideas?

thanks!

[Bob]

Pro knows when it's running on a thin client. If you are running on an XP console,  you don't need a thin client license, however by our definition remote desktop is a thin client and requires a terminal server license.

[console]

I can understand why you would want people using ICE TCP on a Terminal Server to pay for an extra license as several users could be using a program with a single user license.

But with XP Pro there can only be one user using the PC at a time either by TS or as console... Therefore it seems silly to pay for an extra license when there can only ever be a single user using the program.

And in my case we're just using TS to monitor the PC to make sure its performing correctly.

Thanks

[Bob]

I can see your point however there isn't currently any way for Telnet PRO to sense that it's on a limited version of terminal services. Perhaps this could be added in the future.