PowerShell Script and occupied SPN
In the near future we will use the operation “PowerShell Script” using the WinRM protocol to execute actions on Windows servers. We’re currently testing our developed PowerShell solution and most of the Windows servers are connectable so that’s a good thing J.
We can’t connect to a certain amount of servers because the SPN is already occupied by another service in combination with another AD account (for example IIS or SQL Reporting Service). We’ve found a possible workaround/fix for this issue using the parameter “–IncludePortInSPN” (see Microsoft documentation). We would like to use this parameter in the PowerShell Script operation. Are you familiar with this SPN issue? Do you know if it’s possible to include this parameter in the PowerShell script operation?
We’re currently investigating all options/workarounds with our colleagues of the Windows department. Could you give us more information from the OO perspective?
thanks in advance
Re: PowerShell Script and occupied SPN
Thank you for contacting Microfocus Forum.
My name is Olman, I am from the OO/CSA team.
Regarding your question, my recomendation is to open a case with support in order to test it in a lab and check your workaround and then, if its possible open an enhacenment request with all steps.
We will glad to help you.
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.