diff --git a/mRemoteV1/Resources/Help/CMDSwitches.htm b/mRemoteV1/Resources/Help/CMDSwitches.htm index 842deea0b..d80a326c4 100644 --- a/mRemoteV1/Resources/Help/CMDSwitches.htm +++ b/mRemoteV1/Resources/Help/CMDSwitches.htm @@ -7,7 +7,7 @@

- The following is a list of command line switches supported by mRemote.

+ The following is a list of command line switches supported by mRemoteNG.

diff --git a/mRemoteV1/Resources/Help/Configuration.htm b/mRemoteV1/Resources/Help/Configuration.htm index b7e0d1101..51b312495 100644 --- a/mRemoteV1/Resources/Help/Configuration.htm +++ b/mRemoteV1/Resources/Help/Configuration.htm @@ -9,61 +9,61 @@

First start

- Once you got mRemote installed and run it for the first time you should see a + Once you got mRemoteNG installed and run it for the first time you should see a screen like on the following screenshot.

- The first thing that catches your attention will probably be the info box + The first thing that catches your attention will probably be the info box popping up.
- Don't freak out just yet, this is not a error message and it's totally ok to + Don't freak out just yet, this is not a error message and it's totally ok to show up on the first run.
- It just tells you that the connections file could not be found at the default - location and that mRemote will create a new one for you at this location.
- If you click anywhere else in the application the panel will hide itself again. + It just tells you that the connections file could not be found at the default + location and that mRemoteNG will create a new one for you at this location.
+ If you click anywhere else in the application the panel will hide itself again. (Tip: You can also hit Escape to hide the Errors and Infos panel)

- Now that we now about the Errors and Infos panel take a deep breath and just + Now that we now about the Errors and Infos panel take a deep breath and just stare at the gorgeous about screen for a few seconds. =)
No, seriously, to create your first connection continue reading.

Creating Connections

- Right click the root item (the blue ball labeled "Connections") in the + Right click the root item (the blue ball labeled "Connections") in the Connections panel and select "Add Connection".

- A new item shows up under the root item. You can give it a name now (or rename + A new item shows up under the root item. You can give it a name now (or rename it later). I just named mine "Test".

- Now have a look at the Config panel in the bottom left, just under the + Now have a look at the Config panel in the bottom left, just under the Connections panel.

- As you may notice this is where you configure all the properties of connections + As you may notice this is where you configure all the properties of connections and folders.
- There are a lot of values that can be set but for our first connection we will + There are a lot of values that can be set but for our first connection we will keep things simple.

- The most important things right now are that we tell the application which host + The most important things right now are that we tell the application which host we want to connect to and which protocol we want to use.
- In this example I will use a Windows 2003 server that has RDP (Remote Desktop + In this example I will use a Windows 2003 server that has RDP (Remote Desktop Protocol) enabled.
- As RDP is the default protocol whenever you create a new connection I don't have + As RDP is the default protocol whenever you create a new connection I don't have to change anything there.

- The next thing I'll do is to fill the Hostname/IP field with the hostname I + The next thing I'll do is to fill the Hostname/IP field with the hostname I want to connect to.

- I'll also fill the Username and Password fields so I will be automatically + I'll also fill the Username and Password fields so I will be automatically logged on to the server.

@@ -72,17 +72,17 @@

Opening and Closing Connections

- There are multiple ways to open a connection in mRemote, but the easiest is to + There are multiple ways to open a connection in mRemoteNG, but the easiest is to just double-click the connection in the Connections panel.

- If I do that now, a new panel named "General" with one tab inside named "Test" + If I do that now, a new panel named "General" with one tab inside named "Test" will show up.

- Alright, mRemote is now trying to connect to the specified host.

+ Alright, mRemoteNG is now trying to connect to the specified host.

- If it cannot connect you will see a message popping up like on the following + If it cannot connect you will see a message popping up like on the following screenshot.

@@ -93,24 +93,24 @@

- If you do not want to log off from the remote machine but just close it you can - do this by simply double-clicking the tab labeled "test" or just close the whole + If you do not want to log off from the remote machine but just close it you can + do this by simply double-clicking the tab labeled "test" or just close the whole "General" panel by clicking the small "x" in the upper right corner.

Folders and Inheritance

- Folders in mRemote cannot only be used to categorize connections but also to + Folders in mRemoteNG cannot only be used to categorize connections but also to apply properties to the underlying connections.

Example:
- You have 10 Remote Desktop enabled servers in one domain and 15 in another + You have 10 Remote Desktop enabled servers in one domain and 15 in another domain.
- Normally you would spend a lot of time creating all those connections and + Normally you would spend a lot of time creating all those connections and setting the individual properties like username, password, etc.
- In mRemote there is an easier way. You just create two folders, one for domain A + In mRemoteNG there is an easier way. You just create two folders, one for domain A and one for domain B and set all properties there.
- Then create the Connections and let them inherit every property. The only - properties left to fill on Connection basis are the Connection's name and + Then create the Connections and let them inherit every property. The only + properties left to fill on Connection basis are the Connection's name and hostname. Everything else will be inherited from the parent folder.

"Sounds cool, but how to do it?"
@@ -120,40 +120,40 @@

- Then give it a name and fill all the properties you need (just like you did with + Then give it a name and fill all the properties you need (just like you did with the test Connection).

- When you're done setting the values you can either just drag the test Connection + When you're done setting the values you can either just drag the test Connection inside the folder or create a new one.

Right now nothing has changed and nothing will be inherited.
- To enable inheritance switch to the inheritance view by clicking the dedicated + To enable inheritance switch to the inheritance view by clicking the dedicated button.

- The properties that show up now are almost the same as before, but you can only + The properties that show up now are almost the same as before, but you can only select yes or no.

- When no is selected the property will not be inherited, yes indicates an + When no is selected the property will not be inherited, yes indicates an inherited property.
For this test set "Inherit Everything" to Yes.

- Now if you switch back to the properties view (the button left of the - inheritance button) you should see that not much is left of all those + Now if you switch back to the properties view (the button left of the + inheritance button) you should see that not much is left of all those properties.

- Only the Name and Hostname/IP properties are left over, everything else will be + Only the Name and Hostname/IP properties are left over, everything else will be inherited from the parent folder.
Of course you can also only let some of the properties be inherited.

diff --git a/mRemoteV1/Resources/Help/ConfigurationSQL.htm b/mRemoteV1/Resources/Help/ConfigurationSQL.htm index 419ec236f..85577e2b0 100644 --- a/mRemoteV1/Resources/Help/ConfigurationSQL.htm +++ b/mRemoteV1/Resources/Help/ConfigurationSQL.htm @@ -9,16 +9,16 @@

Warning

- The SQL feature is in an early beta stage and not intended for use in an + The SQL feature is in an early beta stage and not intended for use in an productive environment!
- I recommend you to do a full backup of your connections and settings before + I recommend you to do a full backup of your connections and settings before switching to SQL Server.

Steps to configure your SQL Server

@@ -28,15 +28,15 @@

  • Go to Options - Connections.
  • Check the box that says "Use SQL Server to load & save connections".
  • Fill in your SQL Server hostname or ip address.
  • -
  • If you do not use your Windows logon info to authenticate against the SQL Server +
  • If you do not use your Windows logon info to authenticate against the SQL Server fill in the correct Username and Password.
  • -
  • Click OK to apply the changes. The main window title should now change to +
  • Click OK to apply the changes. The main window title should now change to "mRemoteNG | SQL Server".
  • -
  • Now click on File - Save to update the tables on your SQL Server with the data - from the loaded connections xml file. (Do not click File - New, this doesn't +
  • Now click on File - Save to update the tables on your SQL Server with the data + from the loaded connections xml file. (Do not click File - New, this doesn't work yet)
  • -
  • You should now be able to do everything you were able to do with the XML storage - plus see the changes live on another mRemoteNG instance that is connected to the +
  • You should now be able to do everything you were able to do with the XML storage + plus see the changes live on another mRemoteNG instance that is connected to the same Database.
  • @@ -44,6 +44,6 @@ SQL Table creation Script

    Click here to view the SQL script

    - + diff --git a/mRemoteV1/Resources/Help/Index.htm b/mRemoteV1/Resources/Help/Index.htm index 1f07e295a..964884f22 100644 --- a/mRemoteV1/Resources/Help/Index.htm +++ b/mRemoteV1/Resources/Help/Index.htm @@ -1,7 +1,7 @@ -mRemote Help +mRemoteNG Help diff --git a/mRemoteV1/Resources/Help/Installation.htm b/mRemoteV1/Resources/Help/Installation.htm index f9cd6feaa..c3ff9b7b6 100644 --- a/mRemoteV1/Resources/Help/Installation.htm +++ b/mRemoteV1/Resources/Help/Installation.htm @@ -7,41 +7,41 @@

    - Downloads are provided in four different packages, the setup package, binary package, - portable package and + Downloads are provided in four different packages, the setup package, binary package, + portable package and the source package. They are described below.

    Setup Package

    - The setup package is the compiled version of mRemote which comes in the form of + The setup package is the compiled version of mRemoteNG which comes in the form of a NSIS generated setup.
    - The common way to get mRemote up and running

    + The common way to get mRemoteNG up and running

    Bin Package

    - The binary package is a zip package and contains the same files as the setup + The binary package is a zip package and contains the same files as the setup package but has no automated installer.

    Portable Package

    - The portable package consists of the same files as the bin package but contains - an modified version of the executable which stores and loads all your settings + The portable package consists of the same files as the bin package but contains + an modified version of the executable which stores and loads all your settings from files in the application's directory.
    - This package can be used to run mRemote from an USB stick an preserve your + This package can be used to run mRemoteNG from an USB stick an preserve your configuration wherever you go.

    Source Package

    - The source package is a zip package and contains the source code in form of a + The source package is a zip package and contains the source code in form of a Visual Studio 2008 solution.

     

    Updating and Uninstalling

    - mRemote can be updated without uninstalling it before.
    - There are no user preferences stored in the application directory (except if you + mRemoteNG can be updated without uninstalling it before.
    + There are no user preferences stored in the application directory (except if you put them there), so uninstalling doesn't wipe your settings.

    diff --git a/mRemoteV1/Resources/Help/Introduction.htm b/mRemoteV1/Resources/Help/Introduction.htm index 8fa9f8fe2..70ad7d98c 100644 --- a/mRemoteV1/Resources/Help/Introduction.htm +++ b/mRemoteV1/Resources/Help/Introduction.htm @@ -9,7 +9,7 @@

    Introduction

    - mRemote is a multi-protocol remote connections manager.
    + mRemoteNG is a multi-protocol remote connections manager.
    As of Version 1.00 it supports the RDP, VNC, ICA, SSH, Telnet, RAW, Rlogin and HTTP/S protocols.
    The main goal is to minimize window clutter and to provide a easy gui for managing all your remote connections.