Comments on: lock out access to communications drop down menu in client access emulator http://itknowledgeexchange.techtarget.com/itanswers/lock-out-access-to-communications-drop-down-menu-in-client-access-emulator/ Fri, 24 May 2013 01:03:22 +0000 hourly 1 By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/lock-out-access-to-communications-drop-down-menu-in-client-access-emulator/#comment-71608 tomliotta Tue, 15 Dec 2009 02:03:30 +0000 #comment-71608 Even if the menu item is removed, the .WS files can still be changed. The problem is in the design of the app — it’s designed for terminals and is being used with terminal emulators. Further, the emulators are run in PC environments that allow PC users to make changes to the environment. You can’t allow permissions to be available and then expect them not to be used. (I sympathize and expect that you don’t have much choice.)

Any chance you could control WorkstationID from the server side through the telnet device initialization exit point?

Tom

]]> By: katanabeach http://itknowledgeexchange.techtarget.com/itanswers/lock-out-access-to-communications-drop-down-menu-in-client-access-emulator/#comment-71594 katanabeach Mon, 14 Dec 2009 22:10:32 +0000 #comment-71594 Thanks for your reply. Unfortuneately we don’t have control of these values. For lack of a direct solution I have developed a batch file which will remove all ws files from the desktop and client access program folders and replace the desktop with saved ones each time the user logs on. This will lessen but not eliminate the issue. I would like a better solution. The real problem is having to tie printer devices to workstation ID’s in the 1st place!

]]>