login about faq

For the intial connection to an external's server in order to retrieve/save their hostkey, we have special 'handshake' processes coded to have USERSPROFILE and ALLUSERSPROFILE point to the Windows profile of the ID used by our Maestro Scheduler that runs our production scripts. But, after we have upgraded to Tectia SSH Client, the saving of the hostkeys are defaulting to the profile of the actual user running the 'handshake'. Is there a setting or configuration update needed in order to have the hostkeys saved to our scheduler id's profile?

Here is what is coded in our 'handshake' processes to sva ethe hostkey to the scheduler's profile (maestbas) and it had worked just fine until the upgrade:

SET USERPROFILE=c:\documents and settings\maestbas SET ALLUSERSPROFILE=c:\documents and settings\maestbas

asked Feb 26 '14 at 00:12

ctokach's gravatar image


Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Feb 26 '14 at 00:12

Seen: 2,617 times

Last updated: Feb 26 '14 at 00:12

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.