ICE
TCP/IP Products => TCP-PRO => Topic started by: Bob on January 29, 2004, 12:49:05 pm
-
This thread is for Citrix and Terminal Server related questions.
-
The following info is ONLY for running Pro ON the Citrix/Terminal CONSOLE. If you have a Citrix/Terminal Server version and are running from a THIN CLIENT ONLY the following DOES NOT APPLY TO YOU!
Running Pro on a Citrix/Terminal Server console is like running on any other client machine, you need a unique sequence number if there are Pro clients on other NON-Citrix/Terminal Server machines. The way to do this is to reserve sequence number 1 on the NON-Citrix/Terminal Server license admin server. That way when the Pro client on the Citrix/Terminal Server machine grabs a sequence number from the admin server ON the Citrix/Terminal Server machine it will naturally be sequence number 1 which is reserved on the rest of the network and so avoids the potential sequence number conflict.
If you have multiple Citrix/Terminal Server licenses and you want to run on each of the consoles you will need to reserve sequence number 2 on the NON-Citrix/Terminal license admin server and reserve sequence number 1 on the second Citrix/Terminal Server license admin server so it's client grabs sequence number 2 and so on up to the number of Citrix/Terminal Server licenses you have.
-
If you are going to replace an existing terminal server and you need time to transition users from the old server to the new server you can use the following steps:
Go to our website and request a new "eval key" (for the server you are phasing out). http://portage.jriver.com/tempkey.asp
Once you have this, we can issue a temporary (30-day) terminal server key (again for the server you are phasing out). Call us at 612-677-8200 with the company name that you used to get the temporary key above and request a terminal server demo key.
Install PRO on the new terminal server.
With these two temp keys in hand, you will first need to move the old licenses and company name from the old server to the new server. Run licenseadmin on the old server and print the licenses and company name out or cut and paste them into a document you can take to the new server. Move to the new server, run licenseadmin and put in the license keys and company named that you got off of the old server.
You can then enter the new eval key and temporary terminal server key on the server being phased out. Do this by first changing the company name in licenseadmin, this will delete the old licenses and allow you to enter the temporary keys. Do NOT try to add thin client users to the old server after doing this. All new thin client users should be added to the new server.
NOTE: You cannot run Telnet Pro sessions on both terminal server CONSOLES at the same time. Thin clients will work from both servers until the demo times out. After the demo times out only the new server will allow thin clients.
-
We have a unix server that we access with TCP Pro. I have a windows NT server that contains all the license info and seq numbers.
We are replacing the Unix box and all our workstations with a Terminal/application server. We will not be using TCP Pro as our main application any more but we do need to run it side-by-side with our Terminal server for the month or so it takes to deploy the new software.
My question is:
Can we put a copy of TCP Pro on the terminal server and it still grab a seq number from the NT Server since our thin clients will have the same "terminal name" as our old PC's?
We need to remove all the old PC's to have room for the new equipment and running TCP Pro on the Thin Clients in a window would be the perfect solution.
Can you give me any advise??
-
You can run PRO on the terminal server BUT you need a terminal server/citrix license for PRO to do that. Call sales at 612-677-8200 for pricing info.
-
So! even though we own 40 license for pro and are only using 22 I'll have to purchase additional license in order to phase out the old server and stop using TCP Pro? Once the migration is made to the new server we will not be using TCP Pro at all. Is there not a temporary solution. I hate to pour more money at something we are only going to use for less than a month, after that time I'll have fourty licenses for a product we will never use again. Buying more licenses makes no sense to me.
Thanks for your help,
Tony
-
Our licensing and software production are geared to helping users of our product continue to use it with new technology like terminal server/citrix. There are people moving their emulation systems to thin clients from individual PC's and want to use our product in that environment, our goal is to help them continue to use our product. We also have new users migrating from Windows based accounting solutions to Unix/Linux based solutions and feel that we can offer them part of the solution. These are our goals.
-
Bob,
I do understand you position but I hope you can understand mine. We are not leaving your product because we didn't like it nor because it didn't work well. We love TCP Pro and have been a loyal customer for more than 13 years. Our move to a windows based product was not our choice, our software vendor forced us to move to that platform. As IT manager all I want to do is make a smooth transition for our users, I had hoped you could help.
Thanks for your time,
Tony T
-
Will using a Terminal Server and connecting to it remotely improve speed as compared to the normal telnet. I understand Terminal Server brings in various other benefits like security. Does it improve speed in access ? If so, what is the improvement percentage ?
-
Using Citrix/Terminal server over a remote connection will be SLOWER than having PRO at the remote connection with a normal session. This is because the emulation is CHARACTER based so when you are runnning PRO at the remote site you are moving 8 bit characters back and forth whereas when you are running a Citrix/Terminal server session over a remote link you are moving the bitmap of the screen. No matter how efficient windows/citrix can make that it's still going to be less efficient than simply moving characters. Since you need to have a VPN to connect to Citrix/Terminal server anyway from the remote location you are better off opening up telnet through the VPN and PRO on the remote to talk directly to the Unix machine.
-
Hi, I've had an interesting question come from one of my customers. They were previously using a Tarantella environment where they could send print jobs from the Unix server back to a print spooler on the Tarantella server, then finally back to their Java client on a local web browser, wich would send the print job to what ever their current local printer was.
This customer is now using Ice TCP for Citrix, and would like to be able to do something similar in this environment. Basically, we'd like to send print jobs from a printer on our Unix system to the local printer on the end-users system. I saw the automatically-created printer that shows up in the Telnet Pro session when you sign in, is there a way to create a Unix print spooler capable of sending to that printer by default?
-
I know there is a way to tie the citrix users printer to a local printer at their end though I can't tell you how to do it.
You didn't say how your application does printing. Assuming it uses the unix spooler, you could try setting up LPR on Unix to talk to a LPD on citrix then have that printer remapped to the user OR you could setup ICELP on citrix and the Unix machine and remapping that to the user.
-
I have a issue with terminal server I need help with. I had to reinstall my ICE-Pro and now cannot get the terminal sessions to individualize. I've got the server software load on the terminal server , the licenses and have run the client install on the terminal server. The problem comes in when I go to setup the ICElp in each individuals terminal session , the setting that I setup for one are the settings for all. In other words , I setup user A with it printer . then go to User B and setup it's printer. After I setup user B , User A has B's setting.
This cannot be but is HELP HELP HELP ... Has anyone got a clue What is Wrong ?
-
First, did you install a current version?? Terminal server requires 5.1. The current version is 5.1.26
Second, IceLP puts it's settings into an icetcp.ini file in the users WINDOWS directory. If you EVER were able to get different settings for different users then the users must have had unique WINDOWS directories preserved across logins. You will need to check you terminal server settings to see how this could be done.
-
:'( Hey Bob, each user does have it's own ICETCP.ini But for some reason everyone I go to setup rewrites the ICETCP.ini in the WINNT Folder. Whats up with that? ??? This has worked great for 7 years now. Have you got any clue as to why it not working now or how to fix the issue . Thanks JGALOG .... P.S. I've got about 25 users that have not been able to print now for 3 days . HELP QUICK would be greatly helpful right now .... I know it's your day off ...sorry . BUT PLEASE RESPOND ASAP. Thanks Again
-
So you are using terminal server 2k? The WINNT folder IS the windows directory. The ONLY icetcp.ini file that will be read is the one in that directory.
This means that if you were using IceLP before you reloaded everything you MUST have had some way to preserve the users WINNT directory across sessions.
I don't know anything about where that setting is in terminal server but I can tell you that you must get the above scenario working for individual users or you will not be able to have unique printers for each user.
-
Hey Bob... The only thing I reloaded was the icelp .... Nothing else ... So my server is just like it was before the issue started ... Do you know anyone else that could help. ??? or do you have any other ideas ...thanks JOHN
-
Jim and I know more about the various ICE products than anyone. We wrote most of it. Since IceLP always has stored it's settings in the icetcp.ini file it must be that something has changed on the server.
For this to EVER have allowed different printers for different users in terminal server, the WINNT directory MUST have been unique for each user.
What version of terminal server are you using???
-
windows 2000 with terminal server .... I tried something Different ... I took the new version off and put my original 5.0 ver for terminal server and citrix on. Now it writes the proper *.ini file but when you run Icelp the configuation says it's right and is reflected in the proper ini file but When you look at the Icelp setting after open the icelp, It reflects the setting in the main ICETCP.ini file. and I get a error "can't create printer only when I send a job...... NOW WHAT HELP ..... !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :-*
-
You should NOT use 5.0 on windows 2000 or newer. If it's older than 5.0.81 you will run into registry related problems.
Since IceLP does NOT use the registry and it's always used ICETCP.INI it won't work any different with an older version.
There is only one ICETCP.INI file, the one in the users WINNT directory.
Are you SURE you are using IceLP and not passthrough printing??
-
OK for example each user on my terminal server when created has a fold that looks like this that houses it individual setting -
EX- C:\Documents and Setting\Carver\Windows - Carver is the user - Inside each windows directory at the end of the path holds a icetcp.ini file . That is where each users settings are housed. Something is going on with the registry or the license one .... HELP ! ??? ???
-
As far as the user is concerned, there is only one ICETCP.INI file, the one in their Windows or Winnt directory.
When the user gets a terminal server session, the ICETCP.INI file that is in the Windows/Winnt dir is the one IceLP uses.
If the settings for IceLP are not being preserved across sessions (which is what your problem sounds like) you need to find out how to do that on the terminal server machine. We cannot provide support for terminal server, you must call microsoft for that.
IceLP does NOTHING different for terminal server than it does for a standalone user. There are NO special IceLP settings for terminal server. It's all there in front of you. It's terminal server that you have to make do what you want.
-
Terminal Server is doing everything else just fine .... It's the ICE.TCP that not working right. Do you have a list of the registry settings for ICElp . So I can change or check my setting. JOHN
-
Ummm, PLEASE read what I said before!
There are NO registry settings for IceLP. It doesn't use the registry.
When a user logs in to terminal server and starts IceLP, it will use the settings in the ICETCP.INI file in the users WINDOWS directory. Any thing you do to change how the system acts with IceLP will have to change the ICETCP.INI file in the users WINDOWS directory. Open it with notepad! It's an easy to read text file!
Just some ideas you could mess around with:
If you have some sort of user startup script you could copy a specific ICETCP.INI file to the users WINDOWS directory when they log in and before they run ICELP. Theoretically you could have a different ICETCP.INI file for each user that way and prevent them from modifying it by coping a specific one in each time they start a session. Remember this is just a suggestion. This is totally a WINDOWS issue!
-
Hello.
We have just purchased ICE.TCP Pro for Terminal Server/Citrix. The documentation does not contain any step-by-step guide as to how to install this in a load balanced Citrix environment.
The software installation guide talks about doing a server install for this entire network and then on one server, and then performing a network user install??
We would like to have 3 identical standalone configurations of ICE.TCP so should any one of our terminal servers be offline ICE.TCP will continue to function normally. This has been the case with our older version of the software.
Please can you advise detailing step-by-step instructions on how we can achieve this.
Thanks.
-
Have you registered your licenses yet? PM me with your company name. The installation depends on what kind of terminal server licenses you have.
-
Bob, I've not registed yet as I've only just recieved the product and I'm waiting for the invoice for my supplier in the UK. How do I register? I can't seem to send you a Personal Message either?? We have purchased ICE.TCP Pro 5.1 Terminal server/Citrix, 100 user unlimited server license.
Please help?
-
PM me with your company name and who you purchased the product through and I'll do what I can to get you going....
-
If I have a license service on the network already, do I just put the Terminal Server license on that one? Or do I need to install the license server on my terminal server?
-
I would put a new copy of the license server on the terminal server machine only for use with the terminal server licenses. Note that this means you should NOT run Pro on the console itself (the actually physical keyboard and monitor attached to the terminal server) unless you reserve sequence number 1 on the license server for the standalone Pro PC's.
-
LOGON SCRIPT / PROFILES
The following link explains methods to run a logon script for terminal server users. It specifically mentions making registry entries as a task.
http://www.brianmadden.com/blogs/terminal_services_for_microsoft_windows_server_2003_advanced_technical_design_guide/pages/logon-scripts.aspx
If one sets up a single user, then exported their HKCU->Software->J River registry folder, then executed it in a .bat file using the method outlined in the article above, it seems like it would work. One would probably want to remove the script once it was done or do the runOnce registry trick (sorry, I don't have details on that; you can try to Google or Bing that).