Differences
This shows you the differences between the selected revisions of the page.
| 2016-02-27 | 2016-06-02 | ||
| https (martin) | resolving redirect (martin) | ||
| Line 7: | Line 7: | ||
| * Environment variables referenced in script are not resolved, because they are not set by the service's account. | * Environment variables referenced in script are not resolved, because they are not set by the service's account. | ||
| * Access to files on mapped network drives fails, because the drives are not mapped for the service's account. | * Access to files on mapped network drives fails, because the drives are not mapped for the service's account. | ||
| - | * You rely on [[ui_pageant|Pageant authentication]], but the Pageant is running in a different Windows session, so it cannot talk to an automated instance of WinSCP.((Learn about [[https://blogs.technet.com/b/voy/archive/2007/02/23/services-isolation-in-session-0-of-windows-vista-and-longhorn-server.aspx|Windows Session 0 isolation]].)) | + | * You rely on [[ui_pageant|Pageant authentication]], but the Pageant is running in a different Windows session, so it cannot talk to an automated instance of WinSCP.((Learn about [[https://blogs.technet.microsoft.com/voy/2007/02/23/services-isolation-in-session-0-of-windows-vista-and-longhorn-server/|Windows Session 0 isolation]].)) |
| Note that when using registry as [[config|configuration storage]], the settings are accessible only for your Windows account. When the script is run from Windows Scheduler, SSIS, DTS or other automation service, it is typically run under different (service) account that cannot access your configuration. | Note that when using registry as [[config|configuration storage]], the settings are accessible only for your Windows account. When the script is run from Windows Scheduler, SSIS, DTS or other automation service, it is typically run under different (service) account that cannot access your configuration. | ||