There are a number of answers depending on the question.
Hate to be picky -- but could you be more specific?
Where is your AUT? Machine A or Machine B?
Is it just a question of invoking Silk and running the scripts (e.g. would a scheduler do) or is a question of literally CONTROLLING a Silk run from another machine?
Would a pcAnywhere-alike do the trick for you (remote desktop control)?
More info about your world would help generate more options, I think ...
Yes, scheduler running on Machine B to do build and runtime checking. Then, a smoke test needs to be done. However, only Machine A have SilkTest installed. So, I need a way to call the Silk Scripts and kick off test on Machine A when the build on Machine B is ready. Then, on Machine A, the browser would activate and point and test the build on Machine B.
TonyM is correct -- you need a (licensed) copy of the Agent installed on MachineB.
You'll then need to "coordinate" a scheduled run of SilkTest -- what we typically did was figure out when the work on MachineB would complete, add a little fudge factor, then set the schedule on MachineA to kick off SilkTest.
Check the help for info on how to invoke SilkTest from the command-line.
As TonyM suggests, your scripts need to first connect to MachineB, then run. This kind of "distributed" testing has some limitations -- you'll either hit 'em or you won't depending on what you're trying to accomplish. Just be aware that some functions don't work as you'd expect them to.
you might want to run the smoke test on a clean machine and not the build machine hence. hence you can use this as an alternative:
schedule the scripts to run on A wait for some file and a specific size on machine B which will tell silk that the build is done.
Now run the installation thru silk on A
Now determine if Installation was sucessful
If install is sucessful tell machine to reboot itself put batch file to run silk scripts in startup which will kick off the tests as soon as machine gets restarted.
to restart the machine without it having to ask you for a pssword on NT,XP,2K set the following registry key: