Task Scheduler and eValid Usage Details (Compendium)

[admin2009]

NOTE: This post is made because of a recent user's technical support request concerning setup of eValid in a complex multi-machine environment.

eValid Behaviors within Windows "Task Scheduler" Environments

License checks when eValid is authorized to have (1) user(s) on the hostname - MachineA (for example)...

- In the "Security options", when running the task, to use the specified user account: MachineA/Administrator.

Please NOTE that there are differences between the Local Desktop and the Virtual Desktop selection settings.

-- (Choice 1)
Run only when user is logged in means that when an eValid task is running on the visual "Local Desktop using Administrator". You can in this setup also launch eValid manually and this will be treated as the same (1) user simultaneously.

-- (Choice 2)
Run whether user is logged on or not means that eValid will run on the "Virtual Desktop using Administrator". You cannot in this setup also launch eValid manually because the Virtual(non-visual) and Local(visual) Desktops are treated as two separate/different workspaces and thus assumes (2) users Enterprise license allowed.

Maintaining the correct eValid script playback environment requirements will assure consist results...

Here are some related tips...

- All eValid tasks containing "Desktop" dependencies, usually associated with "Absolute MouseClicks/Application Mode/Sync on Screen Rectangles/etc." will always require "Local Desktop" settings to playback properly. i.e. MachineA's visual desktop must be accessed.

- All eValid tasks containing "NON-Desktop" dependencies can be run inside the non-visual virtual desktop or (*minimized) without effecting the playback results.

- By using eValid's "-Minimize" command line switch, you can lessen interference possibilities with other task's desktop dependencies when "Run only when user is logged on" is a must and several browser windows are involved/active.

- By adding eValid's "Lock/Unlock" script commands to desktop dependent actions, you can assure focus to their corresponding task windows.

- All batch (.bat) file commands must start and end in a clean manner, i.e. "Exitnow" is not recognized by the command console and a <CR> return marks the end and separates all your input.

- Remove any/all "NAV" script command parameters within the .evs, if your event log shows that a "Navigation did not occur..." when you visually confirm that the same navigation did actually happen correctly. Otherwise this tends to make your playbacks appearing to hang when eValid is actually awaiting interal timeout defaults (i.e. clLClick ... NAV).

- Confirm that your "checksum" values are correct for all "clSyncRect" script commands. This will/may differ from display to display, as well as environments.

- It is OK to remove or comment out using "#", a Wait... instruction before any of eValid's ...Sync... script commmands.

- It is a good practice to have your Settings->Paths pointing to your own "Start Page(Enter new URL or select)" rather than being left at the out-of-box "Standard Launch Page". i.e. change to "about:blank" maybe.

- Confirm that all your enabled task's "Last Run Result" should show ideally (0x0) or atleast (0x..), after a manual trigger of your eValid run configured pieces.

[eValid]

NOTE: This post is made because of a recent user's technical support request concerning setup of eValid in a complex multi-machine environment.

eValid Behaviors within Windows "Task Scheduler" Environments

License checks when eValid is authorized to have (1) user(s) on the hostname - MachineA (for example)...

- In the "Security options", when running the task, to use the specified user account: MachineA/Administrator.

Please NOTE that there are differences between the Local Desktop and the Virtual Desktop selection settings.

-- (Choice 1)
Run only when user is logged in means that when an eValid task is running on the visual "Local Desktop using Administrator". You can in this setup also launch eValid manually and this will be treated as the same (1) user simultaneously.

-- (Choice 2)
Run whether user is logged on or not means that eValid will run on the "Virtual Desktop using Administrator". You cannot in this setup also launch eValid manually because the Virtual(non-visual) and Local(visual) Desktops are treated as two separate/different workspaces and thus assumes (2) users Enterprise license allowed.

Maintaining the correct eValid script playback environment requirements will assure consist results...

Here are some related tips...

- All eValid tasks containing "Desktop" dependencies, usually associated with "Absolute MouseClicks/Application Mode/Sync on Screen Rectangles/etc." will always require "Local Desktop" settings to playback properly. i.e. MachineA's visual desktop must be accessed.

- All eValid tasks containing "NON-Desktop" dependencies can be run inside the non-visual virtual desktop or (*minimized) without effecting the playback results.

- By using eValid's "-Minimize" command line switch, you can lessen interference possibilities with other task's desktop dependencies when "Run only when user is logged on" is a must and several browser windows are involved/active.

- By adding eValid's "Lock/Unlock" script commands to desktop dependent actions, you can assure focus to their corresponding task windows.

- All batch (.bat) file commands must start and end in a clean manner, i.e. "Exitnow" is not recognized by the command console and a <CR> return marks the end and separates all your input.

- Remove any/all "NAV" script command parameters within the .evs, if your event log shows that a "Navigation did not occur..." when you visually confirm that the same navigation did actually happen correctly. Otherwise this tends to make your playbacks appearing to hang when eValid is actually awaiting interal timeout defaults (i.e. clLClick ... NAV).

- Confirm that your "checksum" values are correct for all "clSyncRect" script commands. This will/may differ from display to display, as well as environments.

- It is OK to remove or comment out using "#", a Wait... instruction before any of eValid's ...Sync... script commmands.

- It is a good practice to have your Settings->Paths pointing to your own "Start Page(Enter new URL or select)" rather than being left at the out-of-box "Standard Launch Page". i.e. change to "about:blank" maybe.

- Confirm that all your enabled task's "Last Run Result" should show ideally (0x0) or atleast (0x..), after a manual trigger of your eValid run configured pieces.

Thanks for sharing.

The eValid Team.