Terminals Wiki & Documentation Rss Feed

Updated Wiki: Organize favorites

jirkapok — Sat, 11 May 2013 19:58:40 GMT

How to organize favorites

Some of you are connecting to many computers. Searching for required favorite than doesn't have to be easy. In main window, Favorites pane shows only connection name and you are able only create new connection or edit existing. To provide more comfortable favorites management go to "Favorites" > "Organize favorites". In this dialog you see more information at once and additionally you can Delete, Copy, Rename or import existing connections.

Manage Groups (Tags)

When managing discussions on the internet we are used to organize our topics using labels called Tags. In Terminals this labels are also called Tags and are used in similar meaning. There is no extra tool, where you organize Tags for all connections. Simply open one selected connection settings and switch to "Tags" page. Here you will see three boxes:

"New Tag": If you need create new Tag, type its name here and click on green button close to it. New Tag will be listed in available
"Connection Tags": Here are listed all Tags associated to this connection. Button on right side removes selected Tag from this list. To add new Tags use text box above or select existing one from text box bellow.
"All available Tags": Lists all Tags defined on all connections. If you want to show more connections under the same Tag, select one from this list and click green button on right side or double click on it.

Import favorites

When reinstalling or moving from one computer to another or moving from another tool (;-)) you will probably need to backup, restore, import and export favorites. You can do this from main window "File" menu or from "Organize favorites".
Supported file formats are:

Application	File extension	Import	Export
Terminals	XML	X	X
Microsoft remote desktop	RDP	X	X
Multiple remote desktops manager	MRC	X	-
Visionapp remote desktop	VRB	X	-

Imediately after first time Terminals starts, you will be prompted, if you want to import RDP connections from Windows registry.
There are stored recently used Microsoft remote desktop connections, so don't have to import them manually.

Tip: You can also import connections using drag and drop into favorites tree.

To export favorites you have to select, which favorites you want to export. By default passwords aren't exported. Because of internal algorithms, the only supported format from where you can import passwords is Terminals file. Please note that if you select "Export passwords", passwords will be exported in human readable form into the target file!
When importing connections, you can choose, if you want to overwrite existing connections with the same name. Therefore we recommend to back up your connections before you import from unknown file.

Search for computers servicing remote control protocol

In large networks or if you don't know server name, it is comfortable to search for computers in the network automatically. In terminals you have extra options to do so, not only to import connections from a file. All choices are available in "Organize Favorites" dialog mentioned in previous chapter.

Scan Active Directory: If your computer is member of Microsoft Active Directory, you can search the active directory for computer entries. Later you can select computers in results list and create favorites for them.
Scan Network using port scanner: This feature offers you to scan all IP addresses in required range for known services. By default your IP address range is selected and all services used by Terminals are searched.
Direct connect to other Terminals

Active directory scan:

Domain: Domain name to search in. Doesn't have to be fully qualified domain name. Default domain defined Terminals Options is used as default value.
Max. results: Maximum results to obtain. Number in range 0-5000, default 1000. Used to reduce number of obtained results.
Search root: In case of large domain you can define start point of the search. Usually AD organization unit. For the ou 'servers' under the root of the domain 'mydomain.local', you have to fill in ou=servers,dc=mydomain,dc=local' to start searching from there. Leave empty to search in whole domain (default).
LDAP filter: LDAP search filter to use. Use default value to obtain all computers only. For more details how to filter see http://social.technet.microsoft.com/wiki/contents/articles/5392.active-directory-ldap-syntax-filters.aspx
Refresh button: Set search criteria (domain, search root, filter and max. results) to default values.

Note: Some properties are available since version 3.0.

On second page "Direct connection" in "Scan Network" dialog you can establish a direct connection with another machine on the network in order to share connections. In this case the server application and the client application is Terminals running on both sides. Follow the steps described in this dialog.

Grouping connections

Some people are working simultaneously on more than one remote computer. In this case you will need to group favorites and start all connections in one group at once. First you have to create groups. You can do so by selecting "Create group from active connections" from "Groups menu". This command opens dialog, where you type group name and all active connections will be added to the newly created group. Or you can select "Add current connection to" command, if you want to add the active connection to already created group. To use more custom groups management, open "Organize groups" from the same menu. The opened dialog will present two tables. In the left side you define groups and on the right side you select connections associated with selected group. Each table has its own two buttons to Add/Remove items.

Updated Wiki: Organize favorites

jirkapok — Sat, 11 May 2013 19:57:01 GMT

How to organize favorites

Manage Groups (Tags)

"New Tag": If you need create new Tag, type its name here and click on green button close to it. New Tag will be listed in available
"Connection Tags": Here are listed all Tags associated to this connection. Button on right side removes selected Tag from this list. To add new Tags use text box above or select existing one from text box bellow.
"All available Tags": Lists all Tags defined on all connections. If you want to show more connections under the same Tag, select one from this list and click green button on right side or double click on it.

Import favorites

Application	File extension	Import	Export
Terminals	XML	X	X
Microsoft remote desktop	RDP	X	X
Multiple remote desktops manager	MRC	X	-
Visionapp remote desktop	VRB	X	-

Search for computers servicing remote control protocol

Scan Active Directory: If your computer is member of Microsoft Active Directory, you can search the active directory for computer entries. Later you can select computers in results list and create favorites for them.
Scan Network using port scanner: This feature offers you to scan all IP addresses in required range for known services. By default your IP address range is selected and all services used by Terminals are searched.
Direct connect to other Terminals

Active directory scan:

Domain: Domain name to search in. Doesn't have to be fully qualified domain name. Default domain defined Terminals Options is used as default value.
Max. results: Maximum results to obtain. Number in range 0-5000, default 1000. Used to reduce number of obtained results.
Search root: In case of large domain you can define start point of the search. Usually AD organization unit. For the ou 'servers' under the root of the domain 'mydomain.local', you have to fill in ou=servers,dc=mydomain,dc=local' to start searching from there. Leave empty to search in whole domain (default).
LDAP filter: LDAP search filter to use. Use default value to obtain all computers only. For more details how to filter see http://social.technet.microsoft.com/wiki/contents/articles/5392.active-directory-ldap-syntax-filters.aspx

Note: Some properties are available since version 3.0.

On second page "Direct connection" in "Scan Network" dialog you can establish a direct connection with another machine on the network in order to share connections. In this case the server application and the client application is Terminals running on both sides. Follow the steps described in this dialog.

Grouping connections

Updated Wiki: Home

jirkapok — Sun, 28 Apr 2013 22:33:34 GMT

Terminals is a secure, multi tab terminal services/remote desktop client. It uses Terminal Services ActiveX Client (mstscax.dll).

The project started from the need of controlling multiple connections simultaneously. It is a complete replacement for the mstsc.exe (Terminal Services) client.

System Requirements

Support The Project:

and

Supported server protocols:

Windows remote desktop (RDP)
VNC
VMRC
SSH
Telnet
RAS
ICA Citrix
HTTP and HTTPs based viewers

See features list

News

April 29, 2013 - Version 3.0 Public community technical preview 2 release published
Download and test our new version here

April 15, 2013 - Version 3.0 Public community technical preview release published

October 13, 2012 - Visits milestone reached
Congratulations, our project reached first time in history 100k page views/month and about 80k visits/month (statistics).
Thank you for your support.

March 9, 2012 - Community technical preview version 2.1
The sources were updated to fit the new structure for next version. For more infos see Comming soon

March 7, 2012 - Version 2.0 Release Available
After long time we decided to publish final release of current state.. It was long run to improve as much as possible. Download Now

November 24, 2011 - Version 2, Beta 4 Available

We just pushed up Beta 4 for Version 2. Take time to upgrade and let us know what you think.

November 10, 2011 - Automatic Buids

Friends of ours have graciously allowed us to piggy back on their TeamCity installation, which allows us to start publishing frequent builds. In fact we setup TeamCity to produce a build on every code commit! For more info, check the Continuous integration chapter in developer guide in online documentation.

November 1, 2011 - Beta Release for version 2

Now that we have made some serious progress through the bug tracker the team has decided that now would be a good time to re-enter the beta/testing stage for a final version 2.0 release. Please take time to download the release and provide feedback ASAP.

History

Our Blogs

Rob Chartier ~ Contemplation... - http://weblogs.asp.net/rchartier/default.aspx
Not So Smart Builder: http://notsosmartbuilder.blogspot.com/
Eyal's Posts: http://www.epocalipse.com/blog/

Updated Wiki: Home

jirkapok — Sun, 28 Apr 2013 22:32:58 GMT

Terminals is a secure, multi tab terminal services/remote desktop client. It uses Terminal Services ActiveX Client (mstscax.dll).

The project started from the need of controlling multiple connections simultaneously. It is a complete replacement for the mstsc.exe (Terminal Services) client.

System Requirements

Support The Project:

and

Supported server protocols:

Windows remote desktop (RDP)
VNC
VMRC
SSH
Telnet
RAS
ICA Citrix
HTTP and HTTPs based viewers

See features list

News

April 29, 2013 - Version 3.0 Public community technical preview 2 release published
Download and test our new version here

April 15, 2013 - Version 3.0 Public community technical preview release published
Download and test our new version

March 9, 2012 - Community technical preview version 2.1
The sources were updated to fit the new structure for next version. For more infos see Comming soon

March 7, 2012 - Version 2.0 Release Available
After long time we decided to publish final release of current state.. It was long run to improve as much as possible. Download Now

November 24, 2011 - Version 2, Beta 4 Available

We just pushed up Beta 4 for Version 2. Take time to upgrade and let us know what you think.

November 10, 2011 - Automatic Buids

November 1, 2011 - Beta Release for version 2

History

Our Blogs

Rob Chartier ~ Contemplation... - http://weblogs.asp.net/rchartier/default.aspx
Not So Smart Builder: http://notsosmartbuilder.blogspot.com/
Eyal's Posts: http://www.epocalipse.com/blog/

Updated Wiki: Home

jirkapok — Sun, 28 Apr 2013 22:32:23 GMT

Terminals is a secure, multi tab terminal services/remote desktop client. It uses Terminal Services ActiveX Client (mstscax.dll).

The project started from the need of controlling multiple connections simultaneously. It is a complete replacement for the mstsc.exe (Terminal Services) client.

System Requirements

Support The Project:

and

Supported server protocols:

Windows remote desktop (RDP)
VNC
VMRC
SSH
Telnet
RAS
ICA Citrix
HTTP and HTTPs based viewers

See features list

News

April 29, 2013 - Version 3.0 Public community technical preview 2 release published
Download and test our new version here

April 15, 2013 - Version 3.0 Public community technical preview release published
Download and test our new version here

March 9, 2012 - Community technical preview version 2.1
The sources were updated to fit the new structure for next version. For more infos see Comming soon

March 7, 2012 - Version 2.0 Release Available
After long time we decided to publish final release of current state.. It was long run to improve as much as possible. Download Now

November 24, 2011 - Version 2, Beta 4 Available

We just pushed up Beta 4 for Version 2. Take time to upgrade and let us know what you think.

November 10, 2011 - Automatic Buids

November 1, 2011 - Beta Release for version 2

History

Our Blogs

Rob Chartier ~ Contemplation... - http://weblogs.asp.net/rchartier/default.aspx
Not So Smart Builder: http://notsosmartbuilder.blogspot.com/
Eyal's Posts: http://www.epocalipse.com/blog/

Updated Wiki: Home

jirkapok — Mon, 15 Apr 2013 16:54:03 GMT

Terminals is a secure, multi tab terminal services/remote desktop client. It uses Terminal Services ActiveX Client (mstscax.dll).

The project started from the need of controlling multiple connections simultaneously. It is a complete replacement for the mstsc.exe (Terminal Services) client.

System Requirements

Support The Project:

and

Supported server protocols:

Windows remote desktop (RDP)
VNC
VMRC
SSH
Telnet
RAS
ICA Citrix
HTTP and HTTPs based viewers

See features list

News

April 15, 2013 - Version 3.0 Public community technical preview release published
Download and test our new version here

March 9, 2012 - Community technical preview version 2.1
The sources were updated to fit the new structure for next version. For more infos see Comming soon

March 7, 2012 - Version 2.0 Release Available
After long time we decided to publish final release of current state.. It was long run to improve as much as possible. Download Now

November 24, 2011 - Version 2, Beta 4 Available

We just pushed up Beta 4 for Version 2. Take time to upgrade and let us know what you think.

November 10, 2011 - Automatic Buids

November 1, 2011 - Beta Release for version 2

History

Our Blogs

Rob Chartier ~ Contemplation... - http://weblogs.asp.net/rchartier/default.aspx
Not So Smart Builder: http://notsosmartbuilder.blogspot.com/
Eyal's Posts: http://www.epocalipse.com/blog/

Updated Wiki: Command line arguments

jirkapok — Mon, 15 Apr 2013 16:20:17 GMT

Terminals Command line arguments

To customize terminals like other applications, terminals accepts command line arguments at startup. All arguments have to start with "/" or "-". Even if you provide parameters from command line, the application will start its window. If application isn't able to parse parameters you provided, it starts like without them. Order of arguments doesn't meter, but arguments are case sensitive. Paths have to be encapsulated in quotation marks if they contain spaces.
All switches, which target file location can point to the UNC path and the file name has to respect the default file name.

NOTE: "favsfile" and "cred" switches are new in version 3.0 CTP and aren't present in previous versions.

List of available switches

Parameter	Shortcut	Description
url	-	URL to quick connect to. Only TRM protocl. The "TRM" prefix has to be provided.
config	-	Local path the the config file to use. Defaults to the standard Terminals.config.
favsfile	ff	Path to the favorites and groups file to use. Defaults to the standard favorites.xml.
cred	-	Path to the credentials file to use. Defaults to the standard Credentials.xml.
favs	-	Commma separated Favorite names to quick connect to. Spaces in favorite names aren't supported.
console	c	Connect to the console.
machine	v	Quick connect to machine via RDP on default port (this switch matches mstsc.exe's parameter).
fullscreen	f	Run terminals in Full Screen mode at startup.
AutomaticallyUpdate	au	Enable Automatic Updates. Checks for updates during application start.
reuse	r	Force single instance application, even if the option isn't set in application options.

Examples

Connect to a Single machine:

terminals /url:trm://server
terminals /v:server

Connect to machines stored in favorites named "server" and "server1" at once:

terminals /favs:server,server1

Connect to console on "server" computer:

terminals /v:server /c

Connect to Single, Console, Fullsceen on "server" computer:

terminals /v:server /c /f

When starting Terminals use file stored at \\serverShare\terminalsFiles\terminals.config:

terminals /config:\\serverShare\terminalsFiles\terminals.config

Updated Wiki: Store data in SQL database

jirkapok — Wed, 20 Mar 2013 22:52:19 GMT

How to store data in SQL database

Note: This feature is under active development and isn't present in any of published versions.

Terminals supports two possibilities how to store user data. If you don't change any application options the data are saved into local xml based files (for more details see Backup and restore settings files). Because the possibilities of sharing files are limited, we implemented the same functionality using SQL database. Currently only Microsoft SQL server is supported, tested on version 2008 Express.

How to create database

To create a terminals database use sql script stored under "Main\Resources\Database" or you can copy empty database stored also there. The database is used only as a simple store. Currently (version 3.0) it contains only a few tables, stored procedures and relations. There is no extra logic like triggers, indexes or in database stored CLR code etc.
Because the usage of data from performance point of view is not well known, there are no special indexes or other optimization. Any performance optimization proposals from database administrators are welcome.
The empty database in this case doesn't mean empty database, it means database filled with required model structure (tables, relations and stored procedures), but without any value in all tables.

How to configure the connection

To distribute the database connection in your environment, start Terminals on one of your machines, go to application options and under "Data Store" you will find relevant options. To successfully connect to the database, configure:

Connection string: Usual connection string used to connect to the MS SQL database. When the SQL storage is enabled, default connection string is offered as an example. For more details consult the MS SQL documentation.

Database password: Because we have to protect the shared content stored in the database, SQL database is simply protected by this password. The password is checked when Terminals starts. Note, that this is not the application master password, nor the connection string password. Default database password is empty.

Both values are stored as a part of application configuration and is stored like other parts in encrypted form. The "Test connection" button allows you check, if application is able to connect to the database. It doesn't check the database structure. Anyway, if the database isn't available during application startup, the data store will be switched back to file persisted.

Following image describes the configuration in more detail:

Server Name "..." button: Use Sql browser service to locate SQL instances in your network
Database "..." button: Locate all available databases attached to the selected database server instance
Database password: Provide current Terminals database master password set up by your application administrator. This is used to validate, when connecting to the database.
Set password: Configure the database with new database password. You will be prompted to provide old and new password like in other password resets. If old password doesn't match, you will be not able to apply new password. Depending on content of your database this procedure can take a while, because it requires to update all already stored passwords.
Test connection: Creates new connection string from currently configured values and tries to connect to terminals database. Result is shown, when procedure finishes. Not only connection string is checked, but also provided database master password is checked. Using this button you are able to check complete connection setup.
Advanced: If you need to provide more detail about your connection, like timeouts etc. this button shows detail properties dialog, where you are able to configure complete MS SQL connection string.

SQL store behavior

Only simple concurrent updates are implemented. E.g. In some cases the database request may fail. In this case restart the application
Simple refresh is done each 30 seconds. So wait few seconds after your colleague saves favorite changes
There are no private favorites or credentials. All team members share complete database content
The database is shared for all users, there is no possibility to isolate favorites for each user. There is no user or groups management.
Database Master password updates are done in transaction. It should be secure to update all your stored passwords, if you already have them stored by clients.
If you forget database master password, go to the options table and clear "MasterPasswordHash" row value. In this case, there is no restore. All your passwords protected by this database master password are lost.

How to migrate the data from files to the database

To switch between data store types you have to restart the application
Changing the data store doesn't copy, change or remove any data
If you use both data stored, their data are isolated, but they share application configuration
There is no possibility to combine favorites between file store and database store
To migrate the content you have to export favorites, restart the application and import the exported content

Updated Wiki: Backup and restore settings files

jirkapok — Sat, 16 Mar 2013 13:58:22 GMT

How to backup and restore settings files

Like other applications Terminals stores its data in data files on your disk. All these files are stored under application directory except files, where explicit path is mentioned. Following chapters list all files explaining their content and meaning. Terminals doesn't store any data in Windows registry, so you only have to backup the application directory. This also allows use Terminals as portable application, but require run it under elevated privileges on Windows Vista and later OS version.
Any changes are immediately confirmed into the files. Passwords saved in all files are always written in encrypted form.
To reset configuration or restore to previous state simply close Terminals and replace or remove required file.

It is strongly recommended, that you backup these files before you upgrade to new version.

Data files

When discussing application data, we are talking about values, you create using Terminals like Favorites, Credentials, Tags and history.

History.xml - Stores content visible in History pane. This content is updated whenever you connect to some favorite. Removing this file will clear the history.
Credentials.xml - contains values of stored credentials.
Terminals.config - This is the main Terminals data file. Here Tags, Favorites and application application options are saved. Removing this will clear all your favorites and next time you start terminals, first run wizard will appear.

Window layout files

Layout files hold only positions of main window and tool bars. When you encounter any problem with window position or tool bars, you can remove this files to reset the window layout.

ToolStrip.settings.config - Main window tool bar positions
user.config - stored in user profile (usually in "c:\Documents and Settings\<username>\Local Settings\Application Data\RobertChartier\<Terminals>\<Version>\"). Contains main window position and size.

Log files

Terminals.log4net.config - logging configuration. No one usually changes content of this file.
currentlog.txt - located "Logs" subdirectory in application folder. All problems are noticed in this files. If you want to report any issue, please provide this file as attachment.
LastUpdateCheck.txt - holds only date of last update. This file isn't used yet.

Version 3.0:

Has different files structure depending on installation type, which is described in Upgrade to version 3.0*
All user files of the application are stored in one "Data" directory. This make the application 100% portable.
All other rules are still valid except:
- Content of the files is not backward compatible with version 2.0 and older
- Stronger encryption is used and also additional fields in data files are encrypted (Domain and user name wasn't encrypted till version 3.0)
- New file was added: Favorites.xml - contains all groups and their favorites. This version no longer stored favorites and their groups (Tags) in config file.
- User.config file is not used. Currently window positions were moved to the Terminals.config

Updated Wiki: Backup and restore settings files

jirkapok — Sat, 16 Mar 2013 13:45:44 GMT

How to backup and restore settings files

Data files

When discussing application data, we are talking about values, you create using Terminals like Favorites, Credentials, Tags and history.

History.xml - Stores content visible in History pane. This content is updated whenever you connect to some favorite. Removing this file will clear the history.
Credentials.xml - contains values of stored credentials.
Terminals.config - This is the main Terminals data file. Here Tags, Favorites and application application options are saved. Removing this will clear all your favorites and next time you start terminals, first run wizard will appear.

Window layout files

Layout files hold only positions of main window and tool bars. When you encounter any problem with window position or tool bars, you can remove this files to reset the window layout.

ToolStrip.settings.config - Main window tool bar positions
user.config - stored in user profile (usually in "c:\Documents and Settings\<username>\Local Settings\Application Data\RobertChartier\<Terminals>\<Version>\"). Contains main window position and size.

Log files

Terminals.log4net.config - logging configuration. No one usually changes content of this file.
currentlog.txt - located "Logs" subdirectory in application folder. All problems are noticed in this files. If you want to report any issue, please provide this file as attachment.
LastUpdateCheck.txt - holds only date of last update. This file isn't used yet.

New Comment on "Store data in SQL database"

jirkapok — Sat, 16 Mar 2013 13:41:56 GMT

The database was already uploaded

Updated Wiki: Store data in SQL database

jirkapok — Sat, 16 Mar 2013 13:40:27 GMT

How to store data in SQL database

How to create database

How to configure the connection

Connection string: Usual connection string used to connect to the MS SQL database. When the SQL storage is enabled, default connection string is offered as an example. For more details consult the MS SQL documentation.

Database password: Because we have to protect the shared content stored in the database, SQL database is simply protected by this password. The password is checked when Terminals starts. Note, that this is not the application master password, nor the connection string password. Default database password is empty.

Server Name "..." button: Use Sql browser service to locate SQL instances in your network
Database "..." button: Locate all available databases attached to the selected database server instance
Database password: Provide current Terminals database master password set up by your application administrator. This is used to validate, when connecting to the database.
Set password: Configure the database with new database password. You will be prompted to provide old and new password like in other password resets. If old password doesn't match, you will be not able to apply new password. Depending on content of your database this procedure can take a while, because it requires to update all already stored passwords.
Test connection: Creates new connection string from currently configured values and tries to connect to terminals database. Result is shown, when procedure finishes. Not only connection string is checked, but also provided database master password is checked. Using this button you are able to check complete connection setup.
Advanced: If you need to provide more detail about your connection, like timeouts etc. this button shows detail properties dialog, where you are able to configure complete MS SQL connection string.

SQL store behavior

Only simple concurrent updates are implemented. E.g. In some cases the database request may fail. In this case restart the application
Simple refresh is done each 10 seconds. So wait few seconds after your colleague saves favorite changes
There are no private favorites or credentials. All team members share complete database content
The database is shared for all users, there is no possibility to isolate favorites for each user. There is no user or groups management.
Database Master password updates are done in transaction. It should be secure to update all your stored passwords, if you already have them stored by clients.
If you forget database master password, go to the options table and clear "MasterPasswordHash" row value. In this case, there is no restore. All your passwords protected by this database master password are lost.

How to migrate the data from files to the database

To switch between data store types you have to restart the application
Changing the data store doesn't copy, change or remove any data
If you use both data stored, their data are isolated, but they share application configuration
There is no possibility to combine favorites between file store and database store
To migrate the content you have to export favorites, restart the application and import the exported content

Updated Wiki: Store data in SQL database

jirkapok — Sat, 16 Mar 2013 13:38:28 GMT

How to store data in SQL database

How to create database

How to configure the connection

Connection string: Usual connection string used to connect to the MS SQL database. When the SQL storage is enabled, default connection string is offered as an example. For more details consult the MS SQL documentation.

Database password: Because we have to protect the shared content stored in the database, SQL database is simply protected by this password. The password is checked when Terminals starts. Note, that this is not the application master password, nor the connection string password. Default database password is empty.

Server Name "..." button: Use Sql browser service to locate SQL instances in your network
Database "..." button: Locate all available databases attached to the selected database server instance
Database password: Provide current Terminals database master password set up by your application administrator. This is used to validate, when connecting to the database.
Set password button: Configure the database with new database password. You will be prompted to provide old and new password like in other password resets. If old password doesn't match, you will be not able to apply new password. Depending on content of your database this procedure can take a while, because it requires to update all already stored passwords.
Test connection: Creates new connection string from currently configured values and tries to connect to terminals database. Result is shown, when procedure finishes. Not only connection string is checked, but also provided database master password is checked. Using this button you are able to check complete connection setup.
Advanced: If you need to provide more detail about your connection, like timeouts etc. this button shows detail properties dialog, where you are able to configure complete MS SQL connection string.

SQL store behavior

Only simple concurrent updates are implemented. E.g. In some cases the database request may fail. In this case restart the application
Simple refresh is done each 10 seconds. So wait few seconds after your colleague saves favorite changes
There are no private favorites or credentials. All team members share complete database content
The database is shared for all users, there is no possibility to isolate favorites for each user. There is no user or groups management.
Database Master password updates are done in transaction. It should be secure to update all your stored passwords, if you already have them stored by clients.
If you forget database master password, go to the options table and clear "MasterPasswordHash" row value. In this case, there is no restore. All your passwords protected by this database master password are lost.

How to migrate the data from files to the database

To switch between data store types you have to restart the application
Changing the data store doesn't copy, change or remove any data
If you use both data stored, their data are isolated, but they share application configuration
There is no possibility to combine favorites between file store and database store
To migrate the content you have to export favorites, restart the application and import the exported content

Updated Wiki: Documentation

jirkapok — Sat, 16 Mar 2013 13:16:50 GMT

Documentation

User documentation
Installation
- System requirements
- Upgrade to version 3.0
Features and Screen shots
Developer guide

Updated Wiki: User documentation

jirkapok — Sat, 16 Mar 2013 13:15:48 GMT

User documentation

Well, on the beginning it was a small application...
But anyway, don't search here for SSH specification, or how to enable remote desktop for your account on Windows server. Simply we have to expect, that you know, how to use required service. It is out of scope of this documentation to describe, how network protocols work or how to configure them. And because each implementation of the same service may differ, here you can find only informations, how to use and configure Terminals as a service client and what are its specifics.

Key application terms:

Connection - session between computer, which offers remote control, and your Terminals application
Terminal - text window, which can be used for not GUI remote control protocols like Telnet or SSH
Favorite - stored configuration, which allows you to connect to one service on one server using one user login
Tag - text associated with one or more favorites, which allows you to group your favorites into logical groups visible in tree
Group - set of favorites used for batch connections
Shortcut - stored configuration, which allows you to start script or application directly from Terminals application. By default Terminals comes with shortcuts to Microsoft management console and Control panel applets
Capture - stored screen picture of your running connection
Protocol - type of remote control service offered by server you want to connect to
Credentials - authentication informations (Domain, user name and password). Note, that you don't have to store your passwords. For more details check the documentation.

Note: New version 3.0 CTP doesn't distinguish between Tag and group

How to ...

Manage connections
- Create connection
- Check why i can't connect
- Move connection to the other monitor
- Configure connection share
Manipulate with connection credentials
- Define custom connection credentials
- Reuse stored credentials for more connections
- Protect my connections with master password
Organize favorites
- Manage Tags and Groups
- Import favorites
- Search for computers servicing remote control protocol
Capture connection screen
Configure application data
- Backup and restore settings files
- Store data in SQL database
Start Terminals using Command line arguments

Updated Wiki: System Requirements

jirkapok — Sat, 16 Mar 2013 13:13:58 GMT

System requirements

Operation system

First and foremost you will need a Windows machine with at least Windows XP. I have heard of people testing Terminals with Wine on non-Windows machines but most of what has been done locks us to good old Microsoft.

Version 2.0

.NET Framework:
Because this project is based on .NET framework, you will need to install .NET runtime first. At least .NET framework 3.5 is required. You can download it from Microsoft sites:
x86 Redist Package
x64 Redist Package
Select other languages then English here:
.NET Framework 3.5

Remote desktop client (RDP client)
Since Terminals 1.9, RDP connections require RDP Client 6 or higher to work correctly.
No other remote control tool has to be installed. This version doesn't support RDP 8 protocol.

The RDP6 client comes with native installations of Windows Vista and above and can be downloaded for other operating Systems from the following links:
Terminal Services Client 6.0 update for Windows Server 2003 (KB925876)
Terminal Services Client 6.0 update for Windows Server 2003, x64-based versions (KB925876)
Terminal Services Client 6.0 update for Windows XP (KB925876)
Terminal Services Client 6.0 update for Windows XP, x64-based versions (KB925876)

Version 3.0 (under development):

.NET 4.0 is required: http://www.microsoft.com/en-us/download/details.aspx?id=17718
Also RDP 8 is supported:
- Not necessary
- Not available for Windows XP
- http://blogs.msdn.com/b/rds/archive/2012/10/23/rdp-8-0-update-for-windows-7-sp1-released-to-web.aspx

Updated Wiki: System Requirements

jirkapok — Sat, 16 Mar 2013 13:13:13 GMT

System requirements

Operation system

Version 2.0

.NET Framework:

Because this project is based on .NET framework, you will need to install .NET runtime first. At least .NET framework 3.5 is required. You can download it from Microsoft sites:
x86 Redist Package
x64 Redist Package
Select other languages then English here:
.NET Framework 3.5

Remote desktop client (RDP client)

Since Terminals 1.9, RDP connections require RDP Client 6 or higher to work correctly.
No other remote control tool has to be installed. This version doesn't support RDP 8 protocol.

The RDP6 client comes with native installations of Windows Vista and above and can be downloaded for other operating Systems from the following links:
Terminal Services Client 6.0 update for Windows Server 2003 (KB925876)
Terminal Services Client 6.0 update for Windows Server 2003, x64-based versions (KB925876)
Terminal Services Client 6.0 update for Windows XP (KB925876)
Terminal Services Client 6.0 update for Windows XP, x64-based versions (KB925876)

Version 3.0 (under development):

.NET 4.0 is required: http://www.microsoft.com/en-us/download/details.aspx?id=17718
Also RDP 8 is supported:

* Not necessary
* Not available for Windows XP
* http://blogs.msdn.com/b/rds/archive/2012/10/23/rdp-8-0-update-for-windows-7-sp1-released-to-web.aspx

Updated Wiki: System Requirements

jirkapok — Sat, 16 Mar 2013 13:02:14 GMT

System requirements

Operation system

.NET Framework:

Remote destktop client (RDP client)

Since Terminals 1.9, RDP connections require RDP Client 6 or higher to work correctly.
No other remote control tool has to be installed.

The RDP6 client comes with native installations of Windows Vista and above and can be downloaded for other operating Systems from the following links:
Terminal Services Client 6.0 update for Windows Server 2003 (KB925876)
Terminal Services Client 6.0 update for Windows Server 2003, x64-based versions (KB925876)
Terminal Services Client 6.0 update for Windows XP (KB925876)
Terminal Services Client 6.0 update for Windows XP, x64-based versions (KB925876)

Updated Wiki: Upgrade to version 3.0

jirkapok — Sat, 16 Mar 2013 00:32:37 GMT

Upgrade to version 3.0

This page describes installation scenarios when upgrading from previous versions to version 3.0 using setup and by using new binaries. Purpose of this page is to allow downgrade and specially help when changing between installation types. Notes to portable setup are also relevant to previous version. Purpose of this page is to prepare for an upgrade and specially help when changing between installation types. Notes to portable setup are also relevant to previous versions.

NOTE: Always backup all your files before doing an upgrade!

Setup types

During installation there is a new page asking you to choose install scenario. In general this lets you choose, where your data files will be stored. You will have two options:

Local installation: General type of setup known from other applications. All application configuration files are stored in user profile. This is new option not present in previous versions. In this case application doesn't write any files outside user profile
Portable version: Version 3.0 is 100% portable. This is identical to previous versions setups. You may notice, that some new xml files appear in the application directory. This explains fixes in wrong file locations from previous version for portable configuration.

NOTE: Using portable version will request User account control prompt, when running from directory, which needs administrator privileges.

Replacing binaries (Installation without Windows installer)

Replace also Log4Net.config file (Path to the logs was changed)
You can remove "Thumbs" and "Logs" directories in the application directory. They will be recreated.
After first run of the new version, all your data files should be moved to the "Data" subdirectory

Switching between local install and portable version

To switch already installed version to portable or vice versa you have to:

Change the Log4Net logs directory in Log4Net.config file
Change the "Portable" flag in Terminals.exe.config
Move "Data" directory in expected location

Here are valid values for each configuration:

Property name	Portable version value	Local installation
Portable xml node in Terminals.exe.config	True	False
Log File in Log4.Net.exe.config	"\Data\logs\CurrentLog.txt""	"${USERPROFILE}\Local Settings\Application Data\Robert_Chartier\Terminals\Data\logs\CurrentLog.txt""

Upgrade behavior

If your data are protected by Master password and you are not able to provide it, application will exit without upgrading your files
There is no downgrade from version 3.0 to version 2 or earlier, because encryption algorithm of passwords is not compatible. The only options is to export favorites in import into older version. Because there is no export of Credentials, they are always lost.
There is no upgrade of connections history. After an upgrade your history will be deleted.

Updated Wiki: Upgrade to version 3.0

jirkapok — Sat, 16 Mar 2013 00:22:56 GMT

Upgrade to version 3.0

This page describes installation scenarios when upgrading from previous versions to version 3.0 using setup and by using new binaries. Purpose of this page is to allow downgrade and specially help when changing between installation types. Notes to portable setup are also relevant to previous versiThis page describes installation scenarios when upgrading from previous versions to version 3.0 using setup and by using new binaries. Purpose of this page is to allow downgrade and specially help when changing between installation types. Notes to portable setup are also relevant to previous versions.

NOTE: Always backup all your files before doing an upgrade!

Setup types

During installation there is a new page asking you to choose install scenario. In general this lets you choose, where your data files will be stored. You will have two options:

Local installation: General type of setup known from other applications. All application configuration files are stored in user profile. This is new option not present in previous versions. In this case application doesn't write any files outside user profile
Portable version: Version 3.0 is 100% portable. This is identical to previous versions setups. You may notice, that some new xml files appear in the application directory. This explains fixes in wrong file locations from previous version for portable configuration.

NOTE: Using portable version will request User account control prompt, when running from directory, which needs administrator privileges.

Replacing binaries (Installation without Windows installer)

Replace also Log4Net.config file (Path to the logs was changed)
You can remove "Thumbs" and "Logs" directories in the application directory. They will be recreated.
After first run of the new version, all your data files should be moved to the "Data" subdirectory

Switching between local install and portable version

To switch already installed version to portable or vice versa you have to:

Change the Log4Net logs directory in Log4Net.config file
Change the "Portable" flag in Terminals.exe.config
Move "Data" directory in expected location

Here are valid values for each configuration:

Property name	Portable version value	Local installation
Portable xml node in Terminals.exe.config	True	False
Log File in Log4.Net.exe.config	"\Data\logs\CurrentLog.txt""	"${USERPROFILE}\Local Settings\Application Data\Robert_Chartier\Terminals\Data\logs\CurrentLog.txt""

Upgrade behavior

If your data are protected by Master password and you are not able to provide it, application will exit without upgrading your f