Forum » Scripting / Automation »

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: WinSCP Key-Based Auth Issue in Parallel Migration (2012 → 2022 Server)

Yes, in general you can use the same key pair. The problem is likely elsewhere.

Please attach a full session log file showing the problem (preferably logs from both machines).

To generate the session log file, use /log=C:\path\to\winscp.log command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
lascrams

WinSCP Key-Based Auth Issue in Parallel Migration (2012 → 2022 Server)

Hi all,

I have an existing Windows Server 2012 server running WinSCP scripts successfully using key-based authentication. I’m now building a new Windows Server 2022 server and want to run it in parallel during testing before decommissioning the 2012 server.

I copied the WinSCP scripts and key files to the new server, but the jobs fail there, while the same process continues to work fine on the 2012 server.

I’m trying to confirm whether, in a parallel setup, I can reuse the same existing key pair on the new server, or if I need to generate a new key pair from the 2022 server and provide the new public key to the vendor.

Any insight would be appreciated.

Documentation

Support

Associations

Follow Us