Hi,
I new to the product and I know this question has been asked in the past, but it has been over a year since the last related posting.
I'm trying to run compiled scripts on a terminal service that is disconnected and of course the macro's are not running. What does that mean:
I log on to the terminal service, start the macro and then disconnect. My session is active on the terminal service, I just do not have it's remote display routed to my local machine. As soon as I disconnect, the macro stops.
Help as I have made some promises to my boss based on this product and everything works fine, just not on the terminal sever.
Thanks in advance and I'm hoping for good news,
Scott
Running unattended Macros
Moderators: JRL, Dorian (MJT support)
This is probably related to the windows console not being present. I expect when you disconnect the session is effectively being locked and the console is closed. It's a bit like locking your workstation. If the macro is trying to automate a GUI and you're not logged in there is no GUI, so it can't do anything. While your session may be active, there is probably no console present. The console isn't restarted until you reconnect to your session.
Unfortunately I don't know enough about Windows Terminal Server to tell you for sure if this is the case but it certainly sounds like it. I also don't know if there is any way to set it not to do this.
I'm afraid this isn't a limitation of Macro Scheduler, it's a simple fact of life of Windows. The only way to simulate a user is to have the same access. So a process simulating a user needs a fully logged in machine. For remote solutions I would have the remote server left logged in ALL the time (and if security is an issue lock the server in a secure computer room) and then use VNC (free) or PC Anywhere (for example) to connect you to that running session to administer it. This way nothing is logged out when you disconnect (PC Anywhere can be set to leave the session logged in. VNC is simplest, very effective and free).
Unfortunately I don't know enough about Windows Terminal Server to tell you for sure if this is the case but it certainly sounds like it. I also don't know if there is any way to set it not to do this.
I'm afraid this isn't a limitation of Macro Scheduler, it's a simple fact of life of Windows. The only way to simulate a user is to have the same access. So a process simulating a user needs a fully logged in machine. For remote solutions I would have the remote server left logged in ALL the time (and if security is an issue lock the server in a secure computer room) and then use VNC (free) or PC Anywhere (for example) to connect you to that running session to administer it. This way nothing is logged out when you disconnect (PC Anywhere can be set to leave the session logged in. VNC is simplest, very effective and free).
MJT Net Support
[email protected]
[email protected]
Hi again,
I've just searched around on the net and from what I can see it does appear to be the case that disconnecting causes the console to lock. The session is logged in but the console isn't present.
If your macro does not require GUI access you could set it up as a service and it will then run all the time. For info see:
http://www.mjtnet.com/index.mv?msfaq6.html
If your macro DOES require GUI access you'll need an alternative solution such as VNC or PC Anywhere.
I've just searched around on the net and from what I can see it does appear to be the case that disconnecting causes the console to lock. The session is logged in but the console isn't present.
If your macro does not require GUI access you could set it up as a service and it will then run all the time. For info see:
http://www.mjtnet.com/index.mv?msfaq6.html
If your macro DOES require GUI access you'll need an alternative solution such as VNC or PC Anywhere.
MJT Net Support
[email protected]
[email protected]
