villev

Hi, I did not find in the discussion the reply I got from Insight (nor did I find it in my mailbox anymore, either *blush*) but nevertheless, the answer I got was: Currently ME does not run as a Windows services and thus any actions taking place when a user is Not logged on will fail. I got a promise that this feature will be a candidate for a future Release.

Hi, will contact insight. However, the way I am deciphering the messages previously in this thread all the users have issues with ME when running ME remotely so that it is installed on the server and when disconnecting (i.e. the Terminal Services session is alive, but what takes place in the session is not displayed to the user) issues start to appear. This is the case for me, and I understand that this might be also the same case for two other persons posting in this same thread. It is a known limitation (see below the clip from the known limitations/knowledgebase/FAQ) that running macross across Client - Server has issues, which I completely understand. What I do not comprehend is the amount of issues when I am running the macros and ME on the server only. Ville ============clip from the knowledge base ==================== Does Macro Express work on a Citrix or Windows Terminal Server? We have many customers running Macro Express in a Citrix and/or Windows Terminal Services (WTS) environment. You can load Macro Express on the server, on the workstation, or both. If Macro Express is installed only on the server, macros may not be able to load and automate programs that are installed on the workstation. If Macro Express is installed only on the workstation, then some macro commands do not work the way you might expect. For example, when a program is loaded on the Citrix/WTS server, the workstation displays the window and window title. But since what is being shown on the workstation is actually an image of what is happening on the server, commands like Wait for Window Title and Activate Window do not work. If Macro Express is installed on both the Citrix/WTS server and the workstation, you have to be careful that your macros do not conflict. Further, the macros that are running on server still cannot load programs that are installed on the workstation and macros that are running on the local workstation may not use certain macro commands. There is one macro command that is specifically used for writing macros in a Citrix environment. The "Store Terminal Services Session ID" command gets the unique Session ID assigned to each Citrix/WTS session. If you are saving information on the server's hard drive, you may want to use the session ID in the file name or path to uniquely identify what session the information belongs to. The "Store Terminal Services Session ID" is available in Macro Express v 3.4 or later. - Updated: August 26, 2004 Will Macro Express run a scheduled macro if the system is logged off or locked, using Windows NT, 2000 or XP Professional? No. When the system is logged off or locked, this effectively locks or closes Macro Express. The program will not be able to activate scheduled macros in this state. - Updated: February 3, 2002

Hi, I am having similar issues with MS Terminal Services Client/Win2k - e.g. scheduling does not work even if you are logged in but not connected. I have not even tried ME locally since there is no physical access to the server I am talking about - it could be that some of the oddities (sometimes macro works and sometimes not) are due to the fact that I am using a Terminal Services connection. I would very much appreciate a solution for this, since I'd like to run Macros scheduled with a Terminal connection user logged in..