URL and Applications Supported by WebPager
M. Gallant 02/14/2001
WebPager supports pointing remote clients to
any valid URL (http, file, ftp etc...).
However, WebPager also supports starting almost any type of
local application on remote clients, UNC network shares,
dll function calls (to access win32 control panels, for example), to name
but a few.
The Show URL: text field of WebPager,
or any text entry in the startup "urlist.txt" file, can contain such entries.
Typical examples are:
- http://www.microsoft.com/security/
(opens Internet web page on remote machines using default browser)
- file:/C:/bootlog.txt or file:///C:/bootlog.txt
(opens local file on remote machines)
- C:/winnt/
(opens folder on remote NT/2000 machines)
- C:/windows/media/canyon.mid
(opens and plays MIDI file on remote machines)
- \\someuncshare\mycustomguitarlics
(opens win32 UNC network share on remote computers)
- RUNDLL32.EXE shell32.dll,Control_RunDLL Inetcpl.cpl,@0,1
(opens Internet Properties control panel, Security Zone pane on remote machines)
- C:\testscripts\remoteadmin.vbs
(runs vbs script on remote machines)
Essentially any application that can be "START"ed locally on a remote
win32 machine can be triggered remotely with WebPager, provided
the remote machine has WebPager running in REMOTE mode, and the
sending machine name has been granted access.
Remote (or local) juke-box functionality, with timed intervals can
very easily be implemented. Administrators can easily build
drop-down lists of common remote tasks and select to administer remotely.
There are unlimited innovative ways of using WebPager, only limited
by your imagination! WebPager has functionality which allows it to
be linked to a server for coordinated synchronized web-execution, resulting
in peer-to-peer functionality of unprecedented capability!