Differences
This shows you the differences between the selected revisions of the page.
| faq_environment 2010-10-10 | faq_environment 2023-08-07 (current) | ||
| Line 5: | Line 5: | ||
| ===== Configuration ===== | ===== Configuration ===== | ||
| - | Configuration of WinSCP in the new environment may differ. Term configuration here does not include only preferences, but also stored sessions and caches for accepted SSH hostkeys and SSL/TLS certificates. | + | Configuration of WinSCP in the new environment may differ. Term configuration here does not include only preferences, but also sites and caches for accepted SSH host keys and TLS/SSL certificates. |
| - | Note that even when you are running WinSCP on the same machine as before, just under a different account (including different system account, such as when using Scheduler, SSIS, etc), you may not have the same configuration. By default WinSCP uses account-specific hive of registry to store its configuration, which is not accesible by other accounts. You may want to use [[config|INI file]] instead to ease configuration sharing. | + | Note that even when you are running WinSCP on the same machine as before, just under a different account (including different system account, such as when using Scheduler, SSIS, etc), you may not have the same configuration. By default WinSCP uses account-specific hive of registry to store its configuration, which is not accessible by other accounts. You may want to use [[config|INI file]] instead to ease configuration sharing. |
| Learn how to [[config#transfer|transfer your existing configuration]] to the new environment in general. | Learn how to [[config#transfer|transfer your existing configuration]] to the new environment in general. | ||
| - | Particuarly when using [[scripting|scripting]] you should avoid depending on configuration, where possible. In script always [[scripting#hostkey|specify fingerprint of expected hostkey or certificate]] explicitly, instead of depending on caches. | + | Particularly when using [[scripting|scripting]] you should avoid depending on configuration, where possible. Prefer configuring your session completely using ''[[scriptcommand_open|open]]'' command, using [[session_url|session URL]] (and [[rawsettings|raw sesssion settings]], if needed), instead of storing [[session_configuration#site|site]]. Also always [[scripting#hostkey|specify fingerprint of expected host key or certificate]] explicitly, instead of depending on caches. Good practice is to develop your scripts with [[scripting#configuration|configuration isolated from GUI]]. |
| - | If you are not able to find what differs between environments, turn on [[logging|logging]] in both of them and compare the logs. It should become obvious. Even if you give up and decide to seek [[support|support]], make sure you post both complete logs. | + | If you are not able to find what differs between environments, turn on [[logging|session logging]] in both of them and compare the logs. It should become obvious. Even if you give up and decide to seek [[support|support]], make sure you post both complete logs. |
| - | //You may want to check more specific article dealing with problems [[faq_scheduler|running WinSCP script under Windows Scheduler, SSIS or other automation services]].// | + | You may want to check these more specific articles: |
| + | |||
| + | * [[faq_scheduler|*]] | ||
| + | * [[faq_script_vs_gui|*]] | ||
| + | * [[guide_debugging_scheduler|*]] | ||
| ===== Firewall ===== | ===== Firewall ===== | ||