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.
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.