Remark: This blogpost is part of a series of blog posts explaining Royal Server and the new connection types we have introduced in Royal TS V3 for Windows and Royal TSX V2 for OS X. Here is a complete list of our blog post series:

Use Case

The Windows Processes module enables you to kill an out-of-control process from Royal TSX directly:

Screen Shot 2015-05-22 at 16.12.45 copy

Configuring a Windows Process Connection

The basic configuration only needs a Computer Name:

Screen Shot 2015-05-22 at 16.14.12

Additionally, you specify an account on the machine, on which you want to manage the Windows Services:

Screen Shot 2015-05-22 at 16.14.44

When you connect, you get all running Windows Processes:

Screen Shot 2015-05-22 at 16.15.31

Customising the Windows Process Connection

You can also show the Process Owner in the view, but since this is a CPU heavy operation, we have made this optional:

Screen Shot 2015-05-22 at 16.16.09

You may need to enable the “Process Owner” column via the context-menu of the columns:

Screen Shot 2015-05-22 at 16.18.11 copy

As a result, you get a view with the Process Owner included:

Screen Shot 2015-05-22 at 16.20.30

Additionally, as with all Connections based on Royal Server, you can configure an automatic refresh:

Screen Shot 2015-05-22 at 16.21.19

This is handy when you want to regularly check for a special running process. You can use the Toolbar filtering for this:

Screen Shot 2015-05-22 at 16.22.04

Share your Royal Documents between Royal TS (for Windows) and Royal TSX

And of course, all the mentioned features work identically on Royal TS (for Windows).

2015-05-22 16_23_15-Web Server 1 Processes

Previous Post Next Post