<March 2012>
Author: Created: Tuesday, September 09, 2008 1:58:59 PM RssIcon
News and updates about
By Stefan Koell on Friday, March 23, 2012 3:15:03 PM

Royal TS 2.0.3 brings a couple of new things and of course bug fixes.


Remote Desktop Dashboard Changes

I should mention one bigger change in 2.0.3 upfront: Royal TS deals with credentials in the dashboard now differently!
Read the following blog post for more information:


Disable Reveal Password

In 2.0.3 you can now also set a registry value to disable the “reveal password” functionality in object dialogs (like credential or connection). We’re also including an ADMX/ADML file to help you deploy this using GPO:


You can set this policy on both, the user level or the machine level (which also overrules the user level setting). The ADMX/ADML files can be found in the Royal TS install directory under Policies.

Alternatively, you can also set the registry value manually (using regedit or using a login script, for example). Value 1 will enable the setting, value 0 or if the value doesn’t exist will turn off the setting:

Contents of the .reg file for the HKLM path:

--- .reg file starts here ---
Windows Registry Editor Version 5.00

--- .reg file ends here ---

Contents of the .reg file for the HKCU path:

--- .reg file starts here ---
Windows Registry Editor Version 5.00

--- .reg file ends here ---

More Enhancements

In addition of the above, we’ve implemented two smaller enhancements in 2.0.3:

1. Hold the SHIFT key while you perform a Connect action to open the tab(s) in the background

2. External connection windows now also show the description field (if available) in the window title (pretty much like the main window does)


Bug Fixes

Read the release notes for a list of fixed issues and bugs:



To download Royal TS 2.0.3 go to:

By Stefan Koell on Monday, March 19, 2012 7:34:10 PM

We’ve just published a brand new beta release of Royal TS which will now also support SSH terminal connections:


While you are connected, you can switch between two different selection modes: Standard or Block selection.

You can also enable/disable the right-click mouse paste feature.

The SSH connection type supports many features and is highly customizable:


Optional private key (incl. putty private keys) and passphrase support.

Credentials, connect and disconnect tasks as well the other standard features (key sequence and window mode) are working the same way as with other connection types.

Advanced Settings:


Specify which Encoding to use, choose from 3 terminal types (Ansi, Wyse 60 and Pick), configure wrap settings, etc.

In the Proxy Settings you can choose between direct connect, Socks4, Socks4a, Socks5 and HTTP connect.



Configure your favorite font and size.



Customize the input behavior of your terminal session and provide default settings for the mouse paste and selection mode.

Download link and instruction can be found here:

For feedback and bug reports, please use the Beta forums:


By Stefan Koell on Tuesday, March 13, 2012 2:32:04 PM

Due to some security considerations, we will change the default behavior of Royal TS’ Hyper-V and Sessions dashboard.

In Version 2.0.2 and earlier Royal TS has a bug which may cause account lockups. This may happen when you are using credentials without setting a password or if you’ve changed your password due to applied security policies.

The default behavior of the Hyper-V and the Sessions dashboard is to first try to gather the information with the currently logged on user (the user who is running Royal TS). If this fails, Royal TS would automatically try to gather the information using the configured credentials. In most cases this isn’t a problem but if the password has changed or if no password is set, an account can be locked out very easily by just clicking on a couple of inactive connections.

What will change in 2.0.3?

First of all, Royal TS will not try to use the configured credential if no password is set. This was clearly a bug and is fixed in 2.0.3.

Secondly we will introduce a new setting in the Dashboard configuration which allows you to control whether or not to use the configured credentials to retrieve the dashboard information.

Note: Because of the above implications, the default setting for this configuration item is OFF! You may want to re-enable the setting if needed.

If your connection(s) are configured to “Use the application default setting” (which is set by default), you just need to open the Royal TS Options on the View tab and check the “Use Credentials” check box:


If you’ve configured your connection(s) to use individual settings, you can also set this option for those connections:


Is there a workaround?

If you are experiencing account lockouts, please disable the automatic Hyper-V and Session information retrieval in the Dashboard settings.

Best regards,

By Stefan Koell on Tuesday, February 14, 2012 2:23:30 PM


Thanks to Arsimael, who  blogged about that in German here, I’m happy to translate and re-blog his content on our blog in English. If you want to make Royal TS V2 portable and start it from a USB memory stick, external drive or even from a Dropbox folder, continue to read…

What does portable mean?

Portable means, that you do not have to install Royal TS to use it. You just put in your memory stick and start Royal TS from the memory stick – without installing it.

To make a portable version of Royal TS V2 you need to download and install it once. After you’ve installed it on your computer it’s a very simple procedure to make it portable:

1. Copy Royal TS V2 to the new location (memory stick, external drive, etc.)

Copy the contents from the Royal TS V2 installation directory to the new location.

By default Royal TS V2 is installed in “%ProgramFiles(x86)%\\Royal TS V2\”.

Note: Do not move the files to the new location. After you’ve copied the files to the new location, you may uninstall Royal TS again, since you will the start it from the new location.

2. Create a configuration folder

Royal TS needs a couple of configuration files. By default they are stored in the users profile directory. Since we also want to have our settings wherever we go, we need to create a new configuration folder in the new location where we copied the Royal TS files.

In the folder where RTS2App.exe was relocated, create a subfolder called with the name config

3. Change configuration path

In the new location, open the file RTS2App.exe.config in notepad and search for the following text:


change the line above to:


4. Copy the configuration file to the new configuration folder

Go to: %APPDATA%\code4ward and copy the file code4ward.RoyalTS.UserPreferences.config to the folder you created in step 2.

Royal TS is now portable!

Things you should know

While the above works well in general, there might be the one or the other issue:

  • Royal TS V2 needs the .NET Framework 4 (Full Profile) and the setup installer makes sure that it’s installed before it proceeds. The portal version doesn’t have a check like this, so you have to take care and make sure that .NET Framework 4 is installed otherwise Royal TS will not work. Take a look at our System Requirements page for more information.
  • File associations are created by the installer. Since you do not install Royal TS when you use the portal version, double-clicking a .rtsx file may ask you to specify the application you want to open for the file. The Windows Explorer allows you to remember the setting and the next time you double-click a file it will open the application from your portable location.
  • Uninstall Royal TS using the Control Panel after you made your portable version. This avoids that the “original”/”non-portal” version is opened when you double-click a .rtsx file.
  • When you want to upgrade to a newer version of Royal TS, install it on a computer, execute step 1 from above without overwriting/deleting the config folder in the portable location.
  • When you start Royal TS the first time from the portable location you may have to re-enter your license information.

Have fun and thanks again to Arsimael for the blog post!


By Stefan Koell on Tuesday, February 14, 2012 12:23:24 PM

My last two blog posts:


showed how I installed SCSM 2012 RC in my lab with a minimum set of hardware/software.

The last bit of the self-service-portal didn’t really work. The setup finished successfully but the portal didn’t work. The links were there but the content is missing. As it turns out the setup wasn’t correct and I’m experiencing SSL certificate issues (btw. the setup didn’t really complain).

After reading that Technet piece, I began to understand the issue. And here’s how I ‘ve resolved it:

1. Create a correct certificate

The first issue is, that the self-signed certificate I used in my lab installation wasn’t matching the computer name. I used the default certificate which came with the OS installation during the setup but it turns out that is a show stopper.

The certificate needs to be issued to the exact same name (FQDN) of the web server(s), which are running SharePoint and and the Web Content Server. Since I’m running both on the same server, I just need one correct certificate.

Unfortunately I have no CA at hand and I don’t want to install one. So let’s create a “correct” self-signed certificate using IIS manager.

Open the “Server Certificates” feature in the IIS manager:


Once opened, click on “Create Self-Signed Certificate” and enter the FQDN of the server:


2. Change Portal Application Setting

Go to the “Service Manager Portal” web site and double-click on “Application Settings”:


Edit the SMPortal_WebContentServer_URL setting and ensure you also have the FQDN of the content host (which must match the SSL issued to value):


3. Assign the new certificate to the web sites

Go to the “Service Manager Portal” web site, click on “Bindings…”, edit the https binding and select the newly created certificate:


Go to the “SCSMWebContentServer”web site, click on “Bindings…", edit the https binding and select the newly created certificate:


4. Verify/Change the Content Server web.config file

Ensure that the “ContentHostAbsoluteUri” setting in web.config file also uses the FQDN:


After those changes and an iisreset, the portal worked for me:



By Stefan Koell on Tuesday, February 14, 2012 11:49:37 AM

This blog post is basically the continuation of my previous blog post which describes my installation experience of System Center Service Manager (aka SCSM) 2012 (Release Candidate). In SCSM 2012 the self-service-portal, which can be used by users to log an incident or submit a service request, is now SharePoint based.

Again, since this is a LAB environment, I install SharePoint and the Self-Service-Portal on my Service Manager management server. In a production environment you should carefully plan your deployment and place the SharePoint server somewhere near your users.

Part 1: Installing SharePoint Foundation 2010 (which is Free!)

You can download SharePoint 2010 Foundation from here:

SP1 for SharePoint 2010 can be found here:

On my Service Manager management server, I start the SharePoint installation and select “Install software prerequisites”:


The nice thing about the installer is that it takes care of all requirements (like IIS, SQL components, etc.):


Accept the license agreement:


And let the installer do its magic:


After that you might need to restart the machine before you can go ahead and install SharePoint Foundation:


Again, a license agreement:


Next screen asks us for the installation type we want:


We select “Standalone” which immediately starts the installation process:


After the installation is complete, keep the checkbox ticked to start the configuration wizard:


The wizard will start in a new window and after clicking Next, you may be asked to restart the services in order to continue:


Didn’t do much but after a while you get:


After you click on Finish, the SharePoint site should open up in your browser.

Before we go ahead and install the Service Manager components, let us apply SP1 for SharePoint Foundation. Start sp1 .exe, accept the license agreement to apply the service pack:


Part 2: Installing the Service Manager Web Portal

Once again, start the Service Manager 2012 setup.exe and select Service Manager web portal:


The first thing we get asked by the wizard is which Portal Parts we want to install:


The web content server is the “middle-tier” between your service manager installation and the SharePoint front-end server. I guess calling it Web Portal Application server would have been a better name (at least for my understanding).

The SharePoint Web Parts are the “front-end” parts you need to install on top of SharePoint. Since we are installing a very compact lab environment, we choose to install both and click on Next:


And another license agreement. We leave the installation location with the default values:


The Prerequisites checker looks fine:


The next screen allows us to configure the portal web site:


Note: I enabled SSL and used the default self-signed certificate of my windows server.

Enter the database server name and select the Service Manager database in the next screen:


Once again we get warned that we use an unsupported collation:


Configure the self-service portal user account:


The next screen will create a SharePoint portal site for the Service Manager self-service portal:


On the next screen we need to setup the user account used for the application pool:


The next two screens are about the Customer Experience Program and the summary page. After that the installation starts and once finished you should see something like this:


Ok, so everything is installed but if you’ve installed it the same way I have, you will soon find out that the Service Manager portal is blank and not working. I will publish another blog post, showing you how to resolve the issue.


By Stefan Koell on Monday, February 13, 2012 11:04:20 AM

I’m just rebuilding my lab with Royal TS V2 (which is awesome, btw. Winking smile) and thought, why not blogging about the Service Manager installation experience. I’ve blogged before about the Operations Manager and Orchestrator setup experience, so it’s kind of tradition to do that for the Service Manager (aka SCSM) as well.


First let’s “unbox” SCSM and see what’s inside the package:

  • SQL Server
    SQL server is not really part of SCSM but you need an existing installation of SQL server or you need to provide a dedicated SQL server for your SCSM installation. SCSM stores the “inventory/CMDB” data as well as the data warehouse data in SQL server. Be sure you have configured your SQL server to use the correct collation:
  • Service Manager management server
    This component is main component to run service manager. It’s the middle-tier between your SCSM console and the database and it’s also responsible to execute workflows. This component is installed first. Setup will also create the databases.
  • Service Manager data warehouse management server
    This component takes care of all workflows and data processing routines necessary to build and maintain the data warehouse. The setup will create all necessary databases for the DW data.
  • Service Manager console
    This is the SCSM UI, which is optional and will be installed on the Service Manager management server or can be installed separately on workstations.
  • Service Manager web portal
    Also optional. The web portal is now completely SharePoint based and is probably subject for a dedicated blog post.

“Special” Requirements, Oddities and Side Effects

Installation and operations of Service Manager is a bit “unconventional”. Pretty much every System Center product can be installed and operated on a single server (i.e. OS installation). Of course, this is not recommended for production but in LAB or test environments you aim for low cost and a low footprint.

From the list of components above, the SCSM management server and the SCSM data warehouse management server are both needed in order to run SCSM but they cannot be installed on the same OS. You need two instances (either virtual or physical) to install those components.

Note: For production environments it’s highly recommended to properly spread out those components to multiple servers to ensure your environment is prepared to scale appropriately:

Also note that there are several “manual” steps you may need to execute after installation, depending on your reporting setup and your data warehouse needs. I always suggest to read carefully the deployment guide and make sure to prepare yourself sufficiently before you go ahead and install SCSM!

Another thing worth mentioning is, that you cannot install a SCOM agent on a SCSM management server. Monitoring of SCSM components are only supported in an agentless way. As of today, even a server where only the SCSM portal web server components are installed, the SCOM agent installation will be blocked. If you install first the SCOM agent and then the SCSM portal web server components, setup will finish without any issues. It’s not clear yet if this is a supported scenario. I hope we get a clear answer from Microsoft by the time RTM is published.

Setup Part 1: Service Manager management server

My first (virtual) machine is a Windows 2008R2 server, fully patched with .NET 3.5 SP1 installed. My database machine is a separate machine running only SQL 2008 R2.

After running setup.exe, click on “Service Manager management server”:


We’re installing the 180 days eval. The product key can be entered afterwards when you got the license key and when you’ve upgraded RC to RTM.


… select the installation location:


The Prerequisite checker complains that I haven’t installed a couple of SQL 2008 components. The good news is, there are links to quickly download and install the missing stuff, the bad news: The links are all for SQL 2008 and I have to start over again with the setup after installation of the missing prerequisites:


Note: Since I’m using SQL 2008 R2 I went to this page: and downloaded the prerequisites for SQL 2008R2 components from there.

Ok, after installing those things, the prerequisite checker looks much better:


Next screen: Service Manager database


I’m using the (US English) default collation and I get an “unsupported” message. I will go ahead with my installation because for my lab environment I will only use English in Service Manager. If you have multi-language requirements or want to use SCSM with a non-English language, please check the collation link and make sure your SQL server is configured properly.


The management group name needs to be unique. Don’t use the same name you’ve used for any of your SCOM environments and do not use any special characters in the management group name. In the past, you ran into issues when you used dashes (-) or other characters in the name. I’m not sure if all the issues are resolved now but I tend to keep the name ASCII chars only to avoid any issues in the first place.

I’m also using the Domain Admins group in the dialog. Again, this is a lab environment and a non-production installation. In production you shouldn’t do that and use appropriate accounts and groups.

After configuring the management group name and specifying a domain group for the admins we’re asked to provide account details for the service accounts:


… and:


That’s it. The next two screens are "Customer Experience Program” and the summary page before the installation begins. Installation may take a while and when it’s finished you should see something like that:


After closing the setup wizard, I strongly recommend the encryption key in a safe place in case of a disaster recovery.

Setup Part 2: Service Manager data warehouse management server

As mentioned before, you need to install a second component on a different server (physical or virtual) in order to complete the SCSM setup. Like my first (virtual) machine, this one is again a Windows 2008R2 server, fully patched with .NET 3.5 SP1 installed.

Let’s start the setup.exe on the second server and select Service Manager data warehouse management server:


As before, accept the license agreement:


and specify the install location:


Remember that one?


Installing the prerequisites, like we did on the first server:


The next page is all about configuring the DW database and as before we are again warned about the collation settings:


Configure all three database settings and click on next:


The next steps allows you to create additional “data marts” for Operations Manager and Configuration Manager. After setup is completed you can pull in data (register the System Center DW to Operations Manager and Configuration Manager):


Now we’ve configured all our databases (quite a lot) to create, so let’s move on:


As you can read the warning on the page, a dedicated management group will be created for the DW. This means you need to provide a unique name for the management group.

Now we’re asked to configure the reporting (SSRS) instance:


The last checkbox reminds us that we need to do some manual stuff. Execute the steps as described here and you should be good.


Now the service accounts for the Service Manager service (see above) and the reporting account:


After you’ve specified the accounts, we need to setup an OLAP cube and the analysis service account:



That’s it. The next two screens are "Customer Experience Program” and the summary page before the installation begins. Installation may take a while and when it’s finished you should see something like that:


After you’ve finished both installations, you need to complete the data warehouse registration(s):

Registering with the Service Manager Data Warehouse

I had to restart the Service Manager console in order to get the Data Warehouse section.

You may also register the SCSM DW to Operations Manager and Configuration Manager:

That’s it from the installation perspective. I will probably post another blog post covering the web console part.


By Stefan Koell on Sunday, February 05, 2012 4:38:03 PM


A very popular feature request for Royal TS was the ability to save connections to a central repository and allow multiple users to access a shared set of connections. If you are working in a team, chances are that everyone in the team needs access to the same set of servers.

We’ve discussed several approaches to solve the problem. On the very top of the list was, of course, a central SQL server as a repository store. The more we thought about the implications, pros and cons, we realized that  a SQL server might not be the best way to implement a feature like this. So we chose a different route – at least for the initial release. We might extend Royal TS to additionally support SQL server as well in the future…

Royal TS V2 solves multi-user access in a simple and elegant way and offers additional advantages you may not be aware of:

  • Multiple users can open, access, edit and save a centrally shared document.
  • When a user saves a document,  it is not overwritten. It is merged (when you configure the document appropriately).
  • It’s still safe. Credentials are stored in different (personal and encrypted) documents and connections refer to them by name. So each user just needs another document containing a credential with the very same name as specified in the connection.
  • No need for SQL! Since this all works on the file system level, there’s no need to install, maintain, prepare or do anything on a SQL server. Just put the document for your team on a network share where everyone has at least read access.
  • Also works with all the cloud based file sync services! Even when you are not working in a team, you may use Royal TS from different computers. Put your document(s) in the cloud using services like DropboxSkyDrive, etc. and sync your changes to all your other machines instantly.
  • There are no licensing restrictions! This feature works with all Royal TS V2 licenses, even when you use it for free in limited shareware mode. Although, in shareware mode you cannot open multiple files and it’s only allowed to have up to 10 connections per application instance. In this case the credential(s) must be set in the Application document but in general it will work.

Have you seen our Royal TS V2 introduction video?


The video doesn’t really explain all the technical details on how to setup a shared document but it will show you the general idea and it’s fun to watch! Click the picture above or this link to watch the video.

There’s also a step-by-step guide in the Royal TS V2 help file explaining how to setup a personal credential to use in a shared document.

Pre-requisites to make this work

As mentioned before, no SQL server is necessary and we think this is a huge advantage. Still, you need to be aware of some things before you start building up a shared document:

  1. You need to define or agree on the credential name(s) which will be used on the shared connection objects. The notes section of the shared document (or of the particular folder) might be a good place to write down the needed credentials.
  2. Agree on a file location where you put your shared document(s). This might be a network file share where everyone has access to or a shared folder in cloud based sync service (like Dropbox).

That’s it.

Create and prepare the shared document


Click on New on the Home tab to create a new Royal TS document. Enter a meaningful Display Name, optionally provide a Description text and make sure you set the Save Mode to Merge file on save. This will prevent the file from being overwritten when a user saves the document. The file on disk will be synced with the contents you have in memory.

In this example I will use 3 different accounts for my connections to illustrate how this is working:
The credential to access all servers in the LAB domain must be named: code4ward LAB Account
The credential to access all my production servers must be named: code4ward PROD Account
The credential to log on to the homepage must be named: code4ward Web Account

Like I said before, it would be a great idea to put that in the document Notes to instruct new users how to setup their credentials:


That’s all what it takes to create and prepare a document to share it with a team of users. All you need to do is to save it to a location everyone has access to and create your connections. I have saved the document to a shared folder on my network and prepared the folder structure the way I want it to be.

Note: We are not encrypting and password protecting this particular document. Since we aren’t using any usernames or passwords in that document it might not really be necessary to protect the document. Anyway, if you like to password protect (and encrypt) the document, you can do that, of course. If you do that, it requires the user to enter the appropriate password in order to open and access the document.

Create connections in the shared document

First I create a new remote desktop connection for a LAB server:


On the Edit tab, click on Remote Desktop to add a new Remote Desktop connection. Enter a Computer Name (host or IP address), a Display Name and optionally provide a Description. Then change to the Credentials settings page:


Select Specify a credential name from the drop down list and enter the exact name of the credential Royal TS should look for before the connection is established. Attention: the credential name is case sensitive and needs to match exactly the name of the credential we create afterwards!

You may configure other settings of the remote desktop connection as well. I will repeat those steps and create some more lab servers using the same credential configuration.

Then I will create my production servers and configure the remote desktop connections the same way as the lab servers except that I use code4ward PROD Account as credential name.

I will also create a new Web Page connection with Auto Fill for automatic logon. The credential configuration works the same way as for remote desktop connections:


In addition you need to create mappings for your resolved credential to the HTML elements of the web page’s log in form:


So, all connections are created, configured to use a credential (which doesn’t even exist yet) and stored to a central location. If you now want to try to connect to a server or web page now, Royal TS will start the connection but it cannot find the credential with the name specified. Royal TS will just leave the credentials blank. This means that in most cases you need to manually type in username and password.

Create your personal document and the credentials needed for the shared document

Now let’s create my personal and private document where I store my credentials:


Since we are putting usernames and passwords in the document, I strongly recommend to password protect and encrypt the document:


Save your personal document to a private location (your home drive, for example). You can use your personal document(s) to store personal connections and tasks as well but in this case we just create the 3 credentials in order to successfully use the shared document.


One the Edit tab, click on Credential to create a new credential. Make sure you enter the exact same Display Name as specified in the credential settings from the shared document connections.

I will repeat this step for the other credentials as well: code4ward PROD Account and code4ward Web Account

When you click on one of the credentials, the Dashboard will show you all connections referring to this credential. This is an easy way to verify that you configured the connections and credentials correctly:


After setting up your credentials, connecting to one of the connections will now resolve your credentials. You just need to ensure that the document with your personal credential details is loaded in the same application instance.

All the other users who want to use the same shared document in Royal TS only need to create their own personal document and setup their credentials the same way as explained above. Then, open up both, the shared document and the personal document to automatically log on to systems with your personal credentials.

Here’s a little timesaver

If you have to open multiple documents every time Royal TS starts up (the shared document and your personal document, for example), you can use the Application Start setting in the Options to specify a list of documents to open automatically when you start Royal TS:



If you use a shared document in a team, you might be interested to get notified as soon as someone in your team changed something in the shared document. Royal TS offers an indicator for that in the status bar:


If you see the little disk icon in the status bar, one or more documents have changed outside your Royal TS instance. Hovering over the icon will show you which documents were changed and double-clicking on it will save and merge the changed documents with your document version.


As you can see, it’s very easy and intuitive to link credentials to connections even from different files and this makes Royal TS a perfect candidate to work in teams without compromising security.

Royal TS offers the best way to work in teams and provides great flexibility to work in most, if not all scenarios. Because Royal TS can now operate in a multi-user environment without the need of SQL database systems or any other 3rd party tools for that matter, it’s one of the easiest and most powerful remote desktop management tool available today.

By Stefan Koell on Monday, January 23, 2012 11:53:55 AM

This new build of Royal TS includes a number of minor bug fixes, some performance optimizations (especially when huge files are loaded) and one new feature:

You can now rearrange the toolbar items (in the QAT) using the mouse and drag&drop. We’ve also posted our first Royal TS V2 Screencast video which will also show this new feature:

Watch on YouTube

Exploring the User Interface

Edit: You can find the newest beta build download on our download page:


By Stefan Koell on Sunday, January 08, 2012 9:47:48 PM

This release incorporates a number of bug fixes and a couple of new things. Before I discuss the new stuff, I want to share some important information about the beta release first:


As before, the beta release is shipped as a .zip file and can be downloaded here:

Just extract the zip file in a directory, execute ngen.cmd to improve startup and general performance and start RTS2App.exe. Royal TS V2 beta has the same system requirements as V1.7:

In all the beta releases you can enter your Royal TS 1.7.x license key to “unlock” Royal TS from Shareware Mode!

What’s New?

Extended Command-Line Support

This release features some new and advanced command-line options, especially in combination with the new “Single Instance Mode” (on by default and can be changed in the RTS2App.exe.config file) this can be very useful. Here’s how it works:

Connect to an existing session using the display name (as seen in the navigation tree), optionally open a .rtsx file and optionally filter by type:
RTS2App.exe [filename.rtsx] /ConnectName:DisplayName [/FilterType:RDP|WEB]

Connect to an existing session using the URI (Hostname/IP or web page URL), optionally open a .rtsx file and optionally filter by type:
RTS2App.exe [filename.rtsx] /ConnectURI:Hostname/IP|URL [/FilterType:RDP|WEB]

Connect to a new AdHoc connection:
RTS2App.exe /ConnectAdHoc:Hostname/IP|URL /AdHocType:RDP|WEB

Executing one of the above commands in SingleInstance mode will actually invoke the session connect or ad-hoc connect in the running instance.

File Modified Indicator

The “Merge file on save” mode from the document properties makes it very easy to work with the same file in teams.


In this mode, saving a file will actually merge your contents with the content on the file system – which might have changed since you opened it. Another team member could have created or modified connections while you are working with it.


The new indicator in the status bar will show up as soon as one of your opened documents was modified outside your Royal TS instance. Hovering your mouse over the icon will show you which file(s) were changed.

Here’s the complete change log for this release:

New: Command-Line Options
New: Indicator in the status bar when a file was modified outside of Royal TS
New: Option to show/hide the status bar
Fixed: Auto Fill issues with HTML elements
Fixed: Possible exception when deleted objects are viewed
Fixed: Send message dialog for terminal sessions
Fixed: Task Context not updated when object is deleted
Fixed: Deep keyboard hook issues with key sequences
Fixed: A drag and drop issue in the navigation tree
Fixed: Possible crash if computer name is invalid in Remote Desktop connections
Fixed: Focus issues for external or full screen Remote Desktop connections
Fixed: Active connection prompt
Fixed: Application settings for web page dashboards were not used


As always, we are happy to hear your thoughts and feedback. Please join us in the beta forums to discuss features and share your feedback: