ICE

Please login or register.

Login with username, password and session length
Advanced search  

News:

ICETCP.PRO and ICETCP.PLUS are compatible with Windows 11!

Author Topic: Default Profile on Terminal Server  (Read 944 times)

TitleG

  • Newbie
  • *
  • Posts: 2
  • Place Personal Text Here
Default Profile on Terminal Server
« on: July 21, 2006, 02:19:44 pm »

How do I get the configured default profile to keep on a Terminal Server environment.  Terminal Server users keep reseting back to the blank default profile.  Please help.
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Default Profile on Terminal Server
« Reply #1 on: July 21, 2006, 03:40:55 pm »

The profiles are kept in the registry. There is an option on terminal server and citrix to not keep changes to the registry across sessions. You should find this and change it to allow users to keep changes to their registry entries across sessions.
Logged

TitleG

  • Newbie
  • *
  • Posts: 2
  • Place Personal Text Here
Default Profile on Terminal Server
« Reply #2 on: July 21, 2006, 06:22:57 pm »


Thank you for the info.  I really don't know where to look, do I look on the Terminal server itself or in the Telnet Pro app.  We are using Telnet pro 5.1.07 on a windows 2000 server box.

If a new user logs on they have to create their profile.  Can I create one on the Server and have all users logging on default to this one, and how do I do that?

Thank you for helping with this matter.
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Default Profile on Terminal Server
« Reply #3 on: July 24, 2006, 09:21:25 am »

The control of the registry is by terminal services, not PRO. You need to find this in your terminal services configuration settings.

You can create global profiles. See this support page:
http://www.icetcp.com/support/ice-tcp-pro-global-profile.html
and this comment on  naming:
http://yabb.jriver.com/ice/index.php?board=2;action=display;threadid=621;start=msg2162#msg2162
Logged
 

Page created in 0.012 seconds with 21 queries.