You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
whytewolf opened this issue
Dec 17, 2018
· 5 comments
Labels
Featurenew functionality including changes to functionality and code refactors, etc.WindowsZDThe issue is related to a Zendesk customer support ticket.
Currently, the WinRM offerings for Saltify and Cloud use SMB to transfer files. It would be good if there were an option to enable WinRM as a fall back option in case SMB is not available on the network. This would allow a wider range of accessibility for the WinRM offerings.
Yes, WinRM is a slower protocol. But some environments do block SMB traffic And this would allow those environments to still use the Saltify and Cloud options.
The text was updated successfully, but these errors were encountered:
whytewolf
added
the
ZD
The issue is related to a Zendesk customer support ticket.
label
Dec 17, 2018
As this feature is scheduled for implementation, another related feature (which likely resulted in this request) would be to support the preflight_cmds against Windows hosts as it's not implemented by salt.utils.deploy_windows.
This way a user can execute commands prior to deploying the minion binary namely to disable to firewall and actually enable SMB via something like: netsh advfirewall firewall set rule name="File and Printer Sharing (SMB-In)" new enable=yes, or Enable-NetFirewallRule -Name "FPS-SMB-In-TCP".
Although you're only copying a file once so performance might not be too important, http://github.com/hashicorp/packer has had issues with winrm file-transfer performance for quite a while and similarly pywinrm has had an issue reported with regards the file copy performance at diyan/pywinrm#77.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.
Featurenew functionality including changes to functionality and code refactors, etc.WindowsZDThe issue is related to a Zendesk customer support ticket.
Description of Issue/Question
Currently, the WinRM offerings for Saltify and Cloud use SMB to transfer files. It would be good if there were an option to enable WinRM as a fall back option in case SMB is not available on the network. This would allow a wider range of accessibility for the WinRM offerings.
Yes, WinRM is a slower protocol. But some environments do block SMB traffic And this would allow those environments to still use the Saltify and Cloud options.
The text was updated successfully, but these errors were encountered: