Integration was not as expected for me

[LoneBandit]

Once integrated, I noticed that all of my sites are now available within each SecureCRT/FX - thats fine...but I have FTP sites and TELNET sites
and they are not interchangable.

Integration mashed all of these together and now whenever I try to add/delete one - as expected its deleted from both.

I like the integration aspect as far as settings/keys/options goes, but how can I maintain that and yet maintain separate session databases?

This particular merge was not good for my purposes

-LoneBandit

[johns]

As a work around, you should be able to set the un-needed protocol to None on the Connection page. For example, if you have a session that you want to be TELNET only, set the "File transfer" protocol to "None". For a FTP only session, set the "Terminal" protocol to "None"

[LoneBandit]

but after doing this, the FTP sites still shows up in the sessions window
and vice-versa...

-LB

[johns]

Yes, it is true that they will show up in the session list requardless of which application you are running. We are aware of this and will probably address this in future releases. Some of the ideas that we have had are.

1) Not show single protocol sessions that do not have a protocol that
matches the application that is being run.
2) Somehow marking the sessions that fit this situation.

We would be most interested on your thoughts on what you think would
be the best way to address this issue.

[Maureen]

As a work around for the time being, if you want to have your sessions integrated, but want more of a distinction between your transfer and terminal sessions, you could organize them in separate folders.

If you decide that you don't want SecureCRT and SecureFX to be integrated, let me know and I'll give you instructions on how to separate them.

Maureen

[LoneBandit]

Actually....this is what I had thought would happen:

1) Not show single protocol sessions that do not have a protocol that
matches the application that is being run.


If I do not select any FTP/SFTP in a connection, then the shared session database should NOT show up in SecureFX...and likewise...if I have a FTP/SFTP in a connection and nothing 'telnet/ssh/serial' related - that should only show up in SecureFX and not SecureCRT.

Thats my $ .02 ......OTOH, what can I do in the meantime to 'unmerge' these and use separate session databases for each program (like the older versions do)

Thanks

-LB

[LoneBandit]

Originally Posted by Maureen

As a work around for the time being, if you want to have your sessions integrated, but want more of a distinction between your transfer and terminal sessions, you could organize them in separate folders.

If you decide that you don't want SecureCRT and SecureFX to be integrated, let me know and I'll give you instructions on how to separate them.

Maureen

Can you please offer the group both choice instructions?
I am sure I wont be the only person who finds this shared entry thing a bit uncool....I like the approach but....

I dont mind if I have to redo any or all of my sessions...just as long as I can keep FTP sessions within SecureFX and telnet sessions within SecureCRT.

The merge really made a mess for me...oh well !

-LB

[Maureen]

Below are instructions for what to change so that SecureCRT and SecureFX aren't integrated and run as completely separate applications.

Important: This only needs to be done if your settings are integrated and you have decided that you no longer want them to be integrated.

1. Run the Registry Editor and navigate to:

   HKEY_CURRENT_USER\Software\VanDyke\Global

   Set the "Integrated" value data to 0.
   
2. In the Registry Editor and navigate to:

   HKEY_CURRENT_USER\Software\VanDyke\SecureCRT

   and note the setting for "Config Path".
   
3. Select a new location for the SecureFX configuration folder edit the following registry setting to point to the new location.

   HKEY_CURRENT_USER\Software\VanDyke\SecureFX\Config Path

4. Move the SecureFX session .INI files from the Sessions folder in the location noted in step #2 to the Sessions folder in the location from step #3. You will need to create the Sessions folder. If you're not sure which sessions are for SecureFX, you can copy all of them and delete the ones you don't want from within SecureCRT and SecureFX. For example:
   
   copy "C:\Documents and Settings\<user>\Application Data\VanDyke\Config\Sessions\*.ini"
   "C:\Documents and Settings\<user>\Application Data\VanDyke\SecureFX\Config\Sessions"

Let me know if you have any questions about these instructions or any problems getting your sessions separated.

Maureen

[LoneBandit]

This didnt work as well as I had thought it would.

So I removed all aspects of SecureFX and reinstall and then resetup my sessions.

I had issues with secureFX remembering things...such as 'set initial directory' on the remote side...

Thanks-

-LB

[Maureen]

I'm sorry that you had to go through all that. Because it's so painful to separate the sessions after they have been integrated, we would like to help people make the best choice for their situation from within the migrate wizard. What additional information could we have given that would have made it clearer what integration means? Below is the current text from the migration wizard.

SecureCRT and SecureFX have been detected on this machine.
SecureCRT 5.0 and SecureFX 3.0 support shared global and session
settings. If the sessions are integrated, they can be used by either client.

Would you like to integrate SecureCRT and SecureFX?

Maureen

[LoneBandit]

I dont have any advice on this. It would be nice (perhaps?) to have a migration choices menu maybe?

Alot of the aspects of migration are a good idea...like keys and settings...but merging the session database (for me) was a disaster.

-LB