Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Transfer winSCP registry from CURRENT_USER to LOCAL_MACHINE or USERS

mcpeterc wrote:

Edit2: Ok my scheduled task now starts a bat file which contains this;
winscp.com /log="C:\Program Files (x86)\WinSCP\log\winSCP.log" /ini="C:\Program Files (x86)\WinSCP\WinSCP.ini" /script="C:\Program Files (x86)\WinSCP\synchronizescript.txt"


It runs and works. Now I hope it will keep running for ever- I will post back

That's the correct way.
See https://winscp.net/eng/docs/scripting#configuration
mcpeterc

Transfer winSCP registry from CURRENT_USER to LOCAL_MACHINE or USERS

I have a keepuptodate script that I have scheduled to run. But its only working if I launch it manually by rightclicking on the job and hit Run.
After some reading this may happen because some winSCP settings are stored in CURRENT_USER in regdb.

My question is if it possible to export my winSCP reg to another container such as LOCAL_MACHINE or USERS so it would work even though im not logged on the machine? Or am I way off here?

Edit: I also have managed to generate a .ini if that could help. Iv made a bat file with this code; "winscp.exe /ini="C:\Program Files (x86)\WinSCP\WinSCP.ini" but when I run it, it just starts winscp.exe. I also tried with winscp.com /ini="C:\blabla" but that does not seem to sync files

Edit2: Ok my scheduled task now starts a bat file which contains this;
winscp.com /log="C:\Program Files (x86)\WinSCP\log\winSCP.log" /ini="C:\Program Files (x86)\WinSCP\WinSCP.ini" /script="C:\Program Files (x86)\WinSCP\synchronizescript.txt"


It runs and works. Now I hope it will keep running for ever- I will post back