sinclaj1

My workplace has added several layers of digital security for third-party apps. Most are blocked unless they are digitally signed, by which I can submit the digital signature info to them and they can whitelist the app to allow all versions of it work.

Is RDM digitially signed?

If so, what information can I provide them (wording of Vendor name, etc)?

If not signed, is that something that can be accomplished (Verisign, etc) soon?

Right now, we can only whitelist by application hash, which means each new version/update gets blocked.

Sure. Where can I download it?

Where are the new beta forums? I usually try to test the betas and follow along with the discussions on the forum.

Can you add DB Visualizer (free edition is fine, though would probably work with all versions) type connections to RDM?

Here's a webpage with the command line items:

http://www.dbvis.com/products/dbvis/doc/7.1/doc/ug/gettingStarted/gettingStarted.html#mozTocId693773

Also... I cannot seem to find the "new 6.0" beta forums. I usually run betas at work to see if I can find things for you guys.

Thanks!!

edited by sinclaj1 on 6/20/2011

Win7 Enterprise, 32-bit

.Net Runtime: V2.0.50727

Remote Desktop 6.1.7600.16385

RDM Version 5.8.3.0

When I go to the "About" page, it reports memory usage at a different value than what is reported by the task manager.

For example, right now, the About page says RDM is using 11MB of RAM, whereas task manager shows 31,400k (31.4MB) being used.

Also, I'm not sure the manual garbage collection is working either. How can I verify it is?

Hi,

Do you know how to make it works from command line ? Maybe it's a bug in WinSCP ?

Found the problem, but this is how you run a stored session from command line:

For GUI --- winscp.exe <storedsessionname>

For no GUI --- winscp.com <storedsessionname>

The problem I ran into...my stored session had a "+" in the name. It didn't work from command line or RDM...so that was due to a limitation in WinSCP's command line interpreter.

Sorry to pin that on you as a bug.

Would still love to be able to designate a file location (central location) for a private key that could be used instead of having to use saved sessions stored within WinSCP.

I think the command line for that would be something like

winscp.exe [mysession] [/privatekey=<key_file>] [/hostkey=<fingerprint>]

Update -

Using version 5.8.2.1. Putting the session in quotes only works when the session name is just an IP address or Host Name. Sessions like "Test Server + key" does not work (with or without quotes).

Awesome start!

Version: 5.8.1.1 Beta

Yesterday I had to rearrange about 100 sessions into PROD and TEST categories. After creating new groups, I decided that it would be faster to just drag and drop them into their new groups. I highlighted several at a time and dragged them into either PROD or TEST as needed.

Today, I noticed that in the tray icon menu, when it comes up there are phantom links in some of the groups called either PROD or TEST (these are listed inside the actual PROD or TEST groups as another link that goes nowhere). These phantom links only show up in the tray icon menu, they do not show up in the full RDM window when restored. I cannot remove these phantom links. Any ideas?

Also - possible feature request - when dragging and dropping, it currently does not highlight where your mouse cursor is. Adding that highlight would be quite helpful, as I missed the mark a few times.

Thanks!

FWIW, I'm running 5.8.1.1 beta, Win7 32-bit with the version of MSTSC.exe that comes with it, and I'm not having an issue.

I verified for the bug about the session, can you do a test for me (I don't have WinSCP anymore installed). Try to put the session name in quote and let me know if it fixing the problem.

That works, yes (using double quotes).

I'm running 5.8.1.1 (beta) right now, but I believe this is in the 5.8.1.0 final as well.

If you choose "Session" (ie: stored session) for a WinSCP connection, the stored session will not connect through RDM -- UNLESS -- the stored session name is the same as the host.

For example: Session name "Server 1 FTP" will not connect and gives "Host does not exist" error....whereas using a stored session name of "10.1.2.3" will connect to that server.

It looks like RDM is treating the stored session name as the actual host name, instead of reading that host information from the stored session.

TEMPORARY WORKAROUND #1 - Put the stored session name in double quotes (")

-or-

TEMPORARY WORKAROUND #2 - Make sure stored session name in WinSCP is the same as the Host you're trying to connect to (IP works, haven't tried DNS or FQDN).

Thanks!

P.S. - Would really love to see the ability to designate a private key from within RDM for WinSCP, instead of using stored sessions. That way I can share the connection, but other people can use their own keys.

edited by sinclaj1 on 7/27/2010

Would it be possible to set up a configuration item inside RDM to point to a path (could be a directory with keys, or to a specific .ppk private key file) for use in connecting through Putty, WinSCP, etc?

That way, you could have it defined in one place, and the connections could automatically try to use that key.

Are you still hoping to add command-line parameters for WinSCP? I'd like to use the

-privatekey=<privatekey.ppk> option so that I can use private keys to connect through WinSCP.

Thanks!

No, those browsers are not supported/allowed for use at my workplace. It's IE mainly, though they're just now allowing Firefox to be used sparingly. However, most of the apps that I have to support require IE.

I'm not familiar with how you were going to implement a "speed dial", I'd have to see a picture or get a description to be sure. What will it do?

95% of how I use RDM though is through that tray icon, as I have a lot of other things running on my screen at any given time.

There's currently an option to "show only favorites" in tray icon menu. Can you add something where defined favorites can be their own section in the trayicon menu (similar to how you have a section for Opened Sessions, tools, etc)?

That way favorites are available along with the other connections that are created?

This way, the 10-15 connections I use the most can be in their own little submenu (perhaps identified by how often they're opened, so maybe it can be automatically called a favorite?), yet if I need a lesser-used one, the entire menu is still there.

You could change the option of "show only favorites" in tray icon menu to a drop-down list with the following options: "Show favorites in tray icon menu, show ONLY favorites in tray icon menu, do not show favorites"

Thanks!

I agree that most IT people should be able to figure it out rather quickly. I think the main idea behind having documentation in the app (or linked to it), is for people who want to look at the tool for the first time to have a better sense of comfort and familiarity. Some IT people read documentation prior to testing an unfamiliar application.

Having documentation with a few good screenshots sprinkled in for ease-of-use would probably make a world of difference for users who first hear about this application.

Are there plans for documentation or a help system to be integrated into the application? May be useful for first-timers and those looking to try the tool out.

As mature as this product is, the reviews from people aren't very good on some major sites like CNet. If you actually use this product, you know how helpful and powerful it is. It saves me a lot of time each day in supporting systems.

I urge everyone to go write an honest review. Let's give this app the face-time it deserves.

Here's the link for CNet.

http://download.cnet.com/Remote-Desktop-Manager/3000-7240_4-10611879.html#userreview

The ability to add specific files (yada.log, something.txt, etc) and have it tail through RDM, similar to a server ping, would be helpful.

Here's a link to something that does this for Win32, this may be useful for adding into RDM for such functionality:

http://tailforwin32.sourceforge.net/index.php

I noticed the other parm option for Putty is currently in the Beta. Any word on the addition of using private keys through putty?

Also there are .PTS files (PowerTerm Session files) that save configurations that can be called from the command line as well. You can basically call subsets of sessions that way. Gives you even more flexibility. (example, one PTS has all Unix servers, another has specific production mainframes). When you call a PTS from the command line, it bypasses the session callup screen at the beginning of PowerTerm.

Step-by-step:

1.) Add new blank session

2.) Choose FTP

3.) On the FTP tab (bottom half of screen) choose WinSCP as the app and SFTP as the protocol.

4.) Click on the 3-dot ellipsis for Host. It locks up at this point.

Yes. Below is from the help file concerning command line parameters.

[- | /]ParameterName [=] ParamaterValue.

[- | /]PHost = Host name

[- | /]PUser = User name

[- | /]PPassword = User Password

[- | /]PSession = Session name to load

[- | /]PFile = File name from where to get parameters

Alternatively these can be entered into a file in the following manner:

ParameterName [= | :] ParamaterValue.

Host[= | :] Host name

User [= | :] User name

Password [= | :] User Password

Session [= | :] Session name to load

File [= | :] File name from where to get parameters

Lib [= | :] Library name

Member [= | :] Member name

Action [= | :] Download/Upload

ActionPrm [= | :]

Download (0=Append, 1-Create, 3=ask)

Upload (1=create new member, 2=replace member 3=append to member)

PCFile [= | :] PC file path and name on DSN=[DSN name]

Viewer [= | :] external viewer name

VIEWOPTION [= | :] View options

(0=not open, 1=default program, 2=external program)

Beep [= | :] Beep after transfer (1=beep)

Jump [= | :] Move to foreground (1=move)

CCSID [= | :] AS/400 code page

CODEPAGE [= | :] PC code page

SAVECODEPAGE [= | :] file code page

All the parameters are optional and their order is not of any consequence.

Example:

"D:\Ericom\dft.exe" -Session=LoadWeeklyTransctions