ICE

Yes.  You can set one user up with the host list the way that you want it, then copy the ICETCPPLUS file (C:\Users\Deanna\AppData\Roaming\ICE) from that user to the other users; or, you could use a text editor in that (.ini) file.  Apparently Windows hides the .ini extension by default.

I have 22 customer systems that are all some flavor of Unix/Linux that I access through DejaVu TCP-Plus.   Is there a way that I can "rearrange" my hosts list without having to Add and Delete them all in the order that I want?

Where is the ICTCPPLUS.INI file located.  I have searched and searched on my Windows 8 PC and cannot find it.

We are looking at upgrading our Linux server from CentOS 6.2 to CentOS 7.  On the 6.2 server the output path for icelp files for iceprint1 is /usr/tmp/iceprint1/icelp_jobs.  On CentOS 7 the file path is /usr/tmp/systemd-private-2LHMv3/tmp/iceprint1/icelp_jobs.  The problem is that after a server reboot and a file sent to iceprint1 the path it now created is /usr/tmp/systemd-private-TmAVj/tmp/iceprint1/icelp_jobs.  The systemd-private-??? portion of the path is changing after a reboot and therefore the client's setting do not match.  I tried looking at the icelp file in the /usr/lib/cups/backend folder and it looks like it should write to /usr/tmp.  Any ideas as to why the extra folder level of systemd-private-???/tmp is being added. 

Thanks,
Josh

It looks like the systemd rewriting of the tmp directory needs to be either shutoff or avoided.
You could likely create a directory, say /var/spool/jriver and use that in place of the /usr/tmp in the /usr/lib/cups/backends/icelp file and also in the users configuration for ICELP on their PC.

We are looking at upgrading our Linux server from CentOS 6.2 to CentOS 7.  On the 6.2 server the output path for icelp files for iceprint1 is /usr/tmp/iceprint1/icelp_jobs.  On CentOS 7 the file path is /usr/tmp/systemd-private-2LHMv3/tmp/iceprint1/icelp_jobs.  The problem is that after a server reboot and a file sent to iceprint1 the path it now created is /usr/tmp/systemd-private-TmAVj/tmp/iceprint1/icelp_jobs.  The systemd-private-??? portion of the path is changing after a reboot and therefore the client's setting do not match.  I tried looking at the icelp file in the /usr/lib/cups/backend folder and it looks like it should write to /usr/tmp.  Any ideas as to why the extra folder level of systemd-private-???/tmp is being added. 

Thanks,
Josh

I am running ICE.TCP Plus on Windows 10. In order to get it to print, I had to check the "Raster Printing" box in the Local Print Setup then reselect the printer. After that, Print Screen worked fine.

For future reference, this is caused by a sshd_config setting that is now default on all SSH distros.

The PasswordAuthentication is set to NO but must be set to YES for Dejawin to properly change passwords.  It does not affect logging in regularly, only the challenge response interactions during password change.  Setting this from no to yes allows the password changes without issue.

Thanks for letting us know.

I installed ICE.TCP PLUS Version 1.0.30, on a computer with Windows 10. I am unable to print with the print screen function in file drop down box. Any ideas??

On behalf of a Windows 10 customer:
Turns out that Dejawin was working perfectly in SAFE MODE but when booting in normal mode it doesn't work.

Further investigation found that that was a software conflict between the Logitech keyboard application (Logitech Gaming Software 8.58 for the G15 keyboard)

Disabled the app, Dejawin lauches perfectly!

For future reference, this is caused by a sshd_config setting that is now default on all SSH distros.

The PasswordAuthentication is set to NO but must be set to YES for Dejawin to properly change passwords.  It does not affect logging in regularly, only the challenge response interactions during password change.  Setting this from no to yes allows the password changes without issue.