Hi Diogène,
Is your project configured to use the pywinrm node executor/file copier? Can you share that config?
Alternatively, you can set the node-executor and file-copier attributes in your Windows remote node model source entry.
Example:
<node name="Hostname" description="Windows Server" tags="windows" hostname="192.168.10.10" osArch="amd64" osFamily="windows" osName="Windows Server 2022" osVersion="2022" username="Administrator" winrm-password-storage-path="keys/winpasswd" winrm-authtype="basic" node-executor="WinRMPython" file-copier="WinRMcpPython" />I’ve included more info here.
Regards.
Hi Diogène,
I get it now.
It seems related to how SSHJ interprets the Windows paths. After some tests, I’ve reproduced your issue.
The quickest way to solve this is to switch to SSH Node Executor / File Copier (managed by JSCH plugin), you can do it at the project level (go to Project Settings> Edit Configuration > Default Node Executor & Default File Copier and change SSHJ by SSH).
If you prefer to do so via node level, you can add the node-executor and file-copy-destination-dir attributes as follows:
<?xml version="1.0" encoding="UTF-8"?> <project> <node name="windows" description="Windows Server 2022" tags="win" hostname="192.168.1.14" osArch="amd64" osFamily="windows" osName="Windows 2022" osVersion="21H2" username="Administrator" ssh-authentication="password" ssh-password-storage-path="keys/winpasswd" file-copy-destination-dir="C:\Windows\Temp" node-executor="jsch-ssh" file-copier="jsch-scp" /> </project>If you need to use Powershell scripts, make sure to define the powershell.exe invocation string as follows:
- defaultTab: nodes description: '' executionEnabled: true id: bcce3833-45ee-4f2d-bfbf-3c9c97fd3092 loglevel: INFO name: WindowsScript nodeFilterEditable: false nodefilters: dispatch: excludePrecedence: true keepgoing: false rankOrder: ascending successOnEmptyNodeFilter: false threadcount: '1' filter: 'name: windows ' nodesSelectedByDefault: true plugins: ExecutionLifecycle: {} scheduleEnabled: true sequence: commands: - fileExtension: .ps1 interpreterArgsQuoted: false script: ls scriptInterpreter: powershell.exe keepgoing: false strategy: node-first uuid: bcce3833-45ee-4f2d-bfbf-3c9c97fd3092Amyway, the best way to connect to Windows remote nodes is to use the Winrm native protocol via the pywinrm plugin.
Hope it helps.
--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/5dcdabc1-0cf1-4ba6-a71b-c7b05b639b38n%40googlegroups.com.