In terminal server sessions we are ending up with the same station id (the terminal server name) in all sessions. We are running under Arev2.12 with NPP.

Because the station id's arent unique, we get problems with the rollout and sort file names because they are the same for every session. I have seen mention of a "SetName" utility which allows you to change the station id. Would this resolve the problem ?

Could someone please tell me where I can get the SetName utility from ?

Because the station id is not unique, could this cause locking problems ?

Thanks,

Michael.

In terminal server sessions we are ending up with the same station id (the terminal server name) in all sessions.

What platform/topology are you running? Does each user log in under a

different user name?

We are running under Arev2.12 with NPP. Because the station id's arent unique, we get problems with the rollout and sort file names because they are the same for every session.

Perhaps you could dynamically set, according to each session with a different @username, @sort.path and @rollout.file and some of the @environ.set variables, to differentiate users.

I have seen mention of a "SetName" utility which allows you to change the station id. Would this resolve the problem ?

This presumably sets @station, which is, in AREV 2.12, a read-only variable. Whatever it does, consider whether it may effectively violate licensing terms. If it does, I doubt anyone could respond to you here if they had such a routine.

Could someone please tell me where I can get the SetName utility from?

You may not need it. On a regular network, with AREV running with multiple users, if @rollout.file is common across workstations (ie on a network drive) you can get a problem with concurrent suspends. You would normally map the rollout path/file to a local drive, or to a unique path for each user. Local drives increase network traffic, but operate quite smoothly.

Same goes for sort files, which are usually differentiated by time/date, but live in a common network path. You could set the @rollout.file and @sort.path variables to give unique paths/files for each @username.

Because the station id is not unique, could this cause locking problems?

Assuming something like a modem session into a LAN workstation terminal running a PC Anywhere style product, logged into a LAN file server. Some records would appear to be locked by yourself, when in fact others have locked them, giving messages "record locked by this workstation". An unlock all from one user would probably unlock records held by others. Indexing and GFEs may also be a hassle.

Perhaps you should contact Revelation Software directly to discuss the best possible topology, products & techniques to use. There must be Citrix style products out there which others have used AREV with.

Steve

There is not much you can do about the station ID that is unique to the machine on the network, but the rollout file and sort files problems are not hard to correct.

You have control of the rollout file name and the sort paths in AREV. These can be set or changed with programs when a user logs in to AREV. On Terminal Server/Metaframe or Winframe you could also create drive mappings that would map to a specific user drive which would be the default rollout and sort file location. This way even if the file names are not unique the location of the files would be. This way one user would not step on another.

See the AREV doc for rollout file name and sort path variables. You might also check on creating unique AREV ini files for users. These can be included in unique autoexec.nt files for each users as they connect to Terminal Server.

Its a pain but you can make AREV stable in the thin client environment. It's just a more technical install.

View this thread on the forum...