<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Windows 2016 Can't Connect Using PowerShell in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Windows-2016-Can-t-Connect-Using-PowerShell/m-p/156293#M35257</link>
    <description>&lt;P&gt;Most likely the change in Windows version also made some changes with regards to type of encryption supported.&lt;BR /&gt;Since the error is specifically calling out key length, have you tried generating a new, longer key in Data ONTAP?&lt;/P&gt;
&lt;P&gt;You can do so by running &lt;STRONG&gt;secureadmin setup ssl&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 18 May 2020 12:44:00 GMT</pubDate>
    <dc:creator>maffo</dc:creator>
    <dc:date>2020-05-18T12:44:00Z</dc:date>
    <item>
      <title>Windows 2016 Can't Connect Using PowerShell</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Windows-2016-Can-t-Connect-Using-PowerShell/m-p/155015#M34842</link>
      <description>&lt;P&gt;This got posted to the Virtualization channel by mistake.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a OnTAP 8.2.5 (7-mode) system and have been using PowerShell scripts to generate reports from a windows 2012 server.&amp;nbsp; I upgraded the Server to Windows 2016 and the scripts now fail performing the connect-nacontroller command.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; Connect-NaController &amp;lt;..&amp;gt; -Credential $Creds -HTTPS&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; Connect-NaController : API invoke failed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Windows 2016 disabled SSLv3 by default.&lt;/P&gt;
&lt;P&gt;If enabled, I get a different error.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;Connection to &amp;lt;..&amp;gt; using HTTPS failed - The request was aborted: Could not create SSL/TLS secure channel.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;The error may be resolved by generating a new certificate on the storage controller, with a longer key length.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The server has PSTK 9.7.1 installed.&lt;/P&gt;
&lt;P&gt;Suggestions?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 11:15:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Windows-2016-Can-t-Connect-Using-PowerShell/m-p/155015#M34842</guid>
      <dc:creator>CGulde</dc:creator>
      <dc:date>2025-06-04T11:15:58Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 2016 Can't Connect Using PowerShell</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Windows-2016-Can-t-Connect-Using-PowerShell/m-p/156293#M35257</link>
      <description>&lt;P&gt;Most likely the change in Windows version also made some changes with regards to type of encryption supported.&lt;BR /&gt;Since the error is specifically calling out key length, have you tried generating a new, longer key in Data ONTAP?&lt;/P&gt;
&lt;P&gt;You can do so by running &lt;STRONG&gt;secureadmin setup ssl&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2020 12:44:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Windows-2016-Can-t-Connect-Using-PowerShell/m-p/156293#M35257</guid>
      <dc:creator>maffo</dc:creator>
      <dc:date>2020-05-18T12:44:00Z</dc:date>
    </item>
  </channel>
</rss>

