Back in June I explored the Crescendo module for Powershell to wrap native command line tool into cmdlets. In the blog post, I needed to make a deviation and did not spend time on looking to the output handler.
ReadQuite recently I was facing an issue whereas a new service was introduced which needed deployment through Azure DevOps remotely. Normally spoken I would fallback in Windows Remote Management (WinRM) and use it in combination with the Invoke-Command cmdlet to create in conduction with the New-Service cmdlet. Unfortunately, WinRM was disallowed by the Network Security Groups (NSGs) on the Azure VMs. Luckily the RPC protocol was allowed, giving us the ability to use the native sc.exe command line tool.
ReadQuite recently I was facing an issue whereas a new service was introduced which needed deployment through Azure DevOps remotely. Normally spoken I would fallback in Windows Remote Management (WinRM for short) and use it in combination with the Invoke-Command cmdlet to create in conduction with the New-Service cmdlet. What if WinRM only cannot be used? Are there any other protocols that I was able to use? In this case, I used the RPC protocol, as in many native tools, it is possible to use it in conduction with a computer name parameter. In this blog, I will explore the native sc.exe command line tool.
Read