I’m managing ~3000 RDP Connections with several Domains and credentials within RoyalTS.
I’m extremely missing the ability to keep RoyalTS in Sync with Active Directory. For me it’s just impossible to keep track within the changes of this amount of connections.
I already found a old post in here which leads to an Powershell Script on github. Unfortunately this is for the V3 Beta and I had to modify some stuff to get it running with v4. For me it’s not a good way to workaround the problem as it gets very complex in my Environment.
As well I’would love to see the ability to set credentials on a folder an then a checkbox which applies this credential within _every_ connection inside this folder. Currently I don’t see a way to perform this without touching every single machine (no-go).
right now, the only way to build docs dynamically from a source like Active Directory, is through our powerful PowerShell cmdlets. To get started with this, go here:
If you create the structure using script, you can, of course, set up all the connections to inherit credentials already. If you want to change many objects (e.g. credential inheritance), you can use our powerful bulk-edit feature:
For new objects, use the Aplication -> Default Sertings folder to setup all the default values.
One little sneak peak: we are working on something for the next major release which will be much more helpful in your situation to dynamically pull in servers and connections from external sources, like AD. Stay tuned!
you are right, the beta is out and we introduced a very cool new feature in Royal TS V5 for Windows:
You can basically populate a folder from a script output within Royal TS. You just create a dynamic folder, choose your script interpreter (e.g. PowerShell as it is “ready to go”), put in a script which gathers your computers from AD and spits out a specific json format which represents the folder structure you want for the dynamic folder. The above link will also guide you to our github repository with sample scripts and the documentation. Right now, we don’t have a script for pulling AD objects. If you want to contribute some scripts, let us know…
We haven’t really promoted dynamic folders yet as it may still be rough on the edges. Once we have enough user feedback confirming all is working, we will publish a series of blog posts and build more sample scripts.
this is not what I’m looking for. I want to tell RoyalTS where my Domain Controller is and which OUs to synch and then I expect Royal TS to sync all Computer Accounts inside this OU on a regular basis.
I understand. In our research we found out that many users have many different use cases. In addition, Royal TS offers many different connection types. For example: you state you want all Computer Accounts inside an OU “in Royal TS”. What exactly do you mean by “Computer Account”? We have different connection types and some users may want them to show as RDP connections (which I guess is your use case) while others want them to show as SSH or Event Log connection, etc. We also have to keep in mind that we need to support multiple platforms (Windows, macOS, mobile). The scripting approach may not be the easiest way to get started but it can really do everything.
That being said, the dynamic folder investment could be used for higher level features with a simpler UI for future “pre-defined” dynamic folder features.
Ben,
The best way I have found is it have a scheduled / event triggered function rebuild the Royal TS Connection Documents.
I built mine with TeamCity and the Royal TS Powershell module. For your case, it might be good to have the build kickoff every time a server is domain joined. You also don’t have to use TeamCity, you could write the powershell script and setup a scheduled task every morning.
Ben - are you still looking for something to assist with this? I am working on something for this (as I got the same issue) let me know - I can send you an early copy of what I’m working on with the dynamic folders
as discussed in this thread, the way to integrate something like that would be dynamic folders. We think this is the best way because it’s very flexible and ensures everyone can implement exactly what’s needed for the specific use case.
