How to Schedule a RemoteInteractive Session

From iMacros
Jump to navigation Jump to search

A RemoteInteractive session is useful to combine the best of two worlds: Interactive (like direct user login) and scheduled (like batch mode with task scheduler).

Note: These instructions are intended for a Windows Server machine only. When you are running macros on your own machine, you can simply use auto-logon.


1. Create two user accounts: An administrator account (called admin in this text) and a standard user account (called iimrunner in this text). Both accounts need to have passwords.

2. As Administrator, create a RDP (Remote Desktop) shortcut

  • a) Open RDP program.
  • b) Put in iimrunner user name and password
  • c) Now set "save password".
  • d) Set IP address to
  • e) Now use SAVE AS and save it as c:\rdp\iimrunner.rdp (Admin user must have access to this folder. Of course, any other folder and file name are ok, too.)

3. Test: Double-click RDP icon: A remote desktop session starts.

4. Now we need to schedule this session to run automatically: Go to "Control Panel"-> "Task scheduler" and create a new task:

Now here we have to create a new task [1].

  • a) Use the Browse button to locate c:\rdp\rdp.bat (see code below!)
  • b) Select when to start task. Choose "When my computer starts". To clarify: The task scheduler is only used to autostart the batch file (and thus the RDP session) after a server reboot. It does not really "schedule" anything.
  • c) Enter user name and password of admin user.
  • d) Now open the detailed settings dialog. UNcheck all boxes. Very important: "Stop the task if it runs for 72h" must be unchecked.

Rdp.bat file (called by task scheduler):

 ping -n 2 -w 1000 > NUL
 ping -n 180 -w 1000 > NUL
 C:\windows\system32\mstsc.exe c:\rdp\iimrunner.rdp

The ping commands are used to create a delay after a server reboot, to make sure the server is ready to start the RDP session.

5. Last but not least, log in as iimrunner user. Create a shortcut for iimRunner.exe and drag the shortcut to iimrunner's autostart folder [2]. Important: You must autostart iimRunner from within this user account. Do not use the task scheduler, otherwise iimRunner runs in Batch mode.

6. Done! iimRunner.exe starts automatically in the RemoteInteractive Session. You can use this session to automatically start any macro or script from any user account and/or any normal scheduled task. Just use iimOpen ("-runner") inside your scripts.

The instructions are tested to work on Windows Server 2003/2008. They should also work fine with Vista/Windows 7. But if you only need to run iMacros locally on your PC, the easier Windows Autologon method will be sufficient.


This setup is much easier than it sounds and works very reliably. We have tested it with 500,000+ iMacros browser starts over months. Up to 25 instances were running at the same time on an average Win 2003 server with 2GB RAM.

The same setup is used by the award-winning AlertFox Website Monitoring service to run 1000s of iMacros tests each day.

For registered users we also have a demo server available and/or can assist you in the setup via remote login. This service is free as part of our Gold support.

Known issue with Amazon EC2 instances: The password that is encrypted on the RDP file can be decrypted only on the same machine in which it is saved. The problem is that every time you shut down and reload the Amazon image it is technically another machine and so the password is not saved. But there are workarounds:

  • Use the "Terminal Service Configuration" and specify on the "Logon Settings" that you want always to use the same credential user: iimrunner and pwd.
  • Or: Use the Autologon option (see below)

Related FAQ: How to run iMacros non-stop.

Alternative: Use Windows Autologon

If your PC or server is in a secure environment (e. g. a data center) there is an even easier method to create a RemoteInteractive session: Enable Autologon. This will start up the session right after your PC is booted up.

Note that when you want to connect to a console session (session 0) created by autologon via remote desktop you need the /admin command line switch:

 mstsc -v: /admin

As before, iimRunner must be started via a shortcut in the startup folder of the iimRunner user account [3], not via task scheduler.

Link: How to turn on automatic logon in Windows


We suggest to use the iimTakeBrowserScreenshot function to take automatic screenshots if an error occurs. This way you know exactly what is going on in your setup. It is also useful for debugging tricky setup issues.


Screenshots from a (web) server running iMacros non-stop:

Use the ADMIN user account to start the batch file at server reboot. This batch file creates our iimrunner user session.
Use the iimrunner User's Startup folder to autostart iimRunner => iimRunner.exe is always running, whether or not iMacros itself is running: iimRunner waits for connections from the iimInit command to start the iMacros instances.
Task manager snapshot of a server with the described setup. Note that in this screenshot the user account name (iimrunner) is the same as that of our iimRunner.exe file. This is simply because we created the user account to run iimRunner there. Any other name can be used, too.

Direct Login to the iimRunner user account => You can directly see the various iMacros instances running. So as a side effect, this setup allows very easy, visual trouble shooting of any problems.

See Also