DCourtel wrote:
Here's the options.xml file after making the mistake:
Very strange that the error message is "Could not establish trust relationship for the SSL/TLS secure channel.", despite the fact that SSL is not used !I can easily replicate this mistake in the "Settings..." window by changing the connection port to 443 before checking the "Connect to local server" box. The result is two identical strings in the server picker: "WSUSSERVERNAME (Local)" and "WSUSSERVERNAME (Local)"
Here's the options.xml file after making the mistake:
<WsusPackagePublisher>
<Server>
<Name>WSUSSERVERNAME</Name>
<IsLocal>True</IsLocal>
<Port>80</Port>
<UseSSL>False</UseSSL>
<IgnoreCertErrors>False</IgnoreCertErrors>
<DeadLineDaysSpan>0</DeadLineDaysSpan>
<DeadLineHour>0</DeadLineHour>
<DeadLineMinute>0</DeadLineMinute>
<VisibleInWsusConsole>LetMeChoose</VisibleInWsusConsole>
</Server>
<Server>
<Name>WSUSSERVERNAME</Name>
<IsLocal>True</IsLocal>
<Port>443</Port>
<UseSSL>True</UseSSL>
<IgnoreCertErrors>False</IgnoreCertErrors>
<DeadLineDaysSpan>0</DeadLineDaysSpan>
<DeadLineHour>0</DeadLineHour>
<DeadLineMinute>0</DeadLineMinute>
<VisibleInWsusConsole>Never</VisibleInWsusConsole>
</Server>
</WsusPackagePublisher>
Based on this, I propose that there should be some way to further distinguish between options in the server picker, like including the port number and whether or not the connection will be made using SSL, or adding a field to the XML definition like <Description>Custom Server Connection Description Here</Description> that is automatically generated by the "Settings..." interface if left blank, but customizable.