<?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 Server 2016 Unidentified Network on HP ProLiant server restart in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016194#M13083</link>
    <description>&lt;P&gt;Well, it looks this might need indepth investigation and i would suggest you open a ticket with HPE.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I Thank you for your cooperation in this regard.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Aug 2018 07:52:33 GMT</pubDate>
    <dc:creator>Taurus78</dc:creator>
    <dc:date>2018-08-28T07:52:33Z</dc:date>
    <item>
      <title>Windows Server 2016 Unidentified Network on HP ProLiant server restart</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7014131#M13064</link>
      <description>&lt;P&gt;Windows Server 2016 Unidentified network on reboot.&amp;nbsp; We have a brand two new HP ProLiant Gen9 servers that when rebooted will not connect to the domain.&amp;nbsp; It just shows as Unidentified network.&amp;nbsp;&lt;BR /&gt;This servers have statics IP settings.&lt;/P&gt;&lt;P&gt;My problem is accurately described in the discussion &lt;A href="https://www.experts-exchange.com/questions/29099058/Windows-2016-Server-Unidentified-Network-on-server-restart.html" target="_blank"&gt;https://www.experts-exchange.com/questions/29099058/Windows-2016-Server-Unidentified-Network-on-server-restart.html&lt;/A&gt;&lt;BR /&gt;But I did not find an answer to my question in this discussion.&lt;/P&gt;&lt;P&gt;I have all updates installed from Microsoft site. And I update all drivers from HP site.&lt;/P&gt;&lt;P&gt;Anyone, have any ideas on how to fix this problem?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Aug 2018 08:08:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7014131#M13064</guid>
      <dc:creator>androsovms</dc:creator>
      <dc:date>2018-08-06T08:08:43Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Server 2016 Unidentified Network on HP ProLiant server restart</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016083#M13079</link>
      <description>&lt;P&gt;Have you checked from the device manager if any of your network adapter shows any ! Sign which would indicate any faulty hardware or driver issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, is it possible to paste any screenshot here.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Aug 2018 11:43:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016083#M13079</guid>
      <dc:creator>Taurus78</dc:creator>
      <dc:date>2018-08-27T11:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Server 2016 Unidentified Network on HP ProLiant server restart</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016088#M13080</link>
      <description>&lt;P&gt;Thanks for answer.&lt;/P&gt;&lt;P&gt;We using Windows Server with Russian GUI. In the Device Manager all devices is OK. I make screenshots:&lt;/P&gt;&lt;P&gt;&lt;A href="https://1drv.ms/f/s!AtYSSvsIGFJph8wa9Zn62F1aS76bpA" target="_blank"&gt;https://1drv.ms/f/s!AtYSSvsIGFJph8wa9Zn62F1aS76bpA&lt;/A&gt;&lt;/P&gt;&lt;P&gt;pic1.png - is Device Manager status.&lt;/P&gt;&lt;P&gt;pic2.png - is Network status now. After the server is restarted, an Unidentified Network will appear instead of sfh.local.&lt;/P&gt;&lt;P&gt;&lt;IMG src="C:\Downloads\pic1.png" border="0" alt="" /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Aug 2018 12:34:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016088#M13080</guid>
      <dc:creator>androsovms</dc:creator>
      <dc:date>2018-08-27T12:34:00Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Server 2016 Unidentified Network on HP ProLiant server restart</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016106#M13081</link>
      <description>&lt;P&gt;you may try the following... Note. Don't attempt this on production servers.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Open elevated CMD&lt;/P&gt;&lt;P&gt;2. run the command Set devmgr_show_nonpresent_devices=1&lt;/P&gt;&lt;P&gt;3. Then run devmgmt.msc&lt;/P&gt;&lt;P&gt;4. Then click on View and Click show hidden devices and expand the network adapters&lt;/P&gt;&lt;P&gt;5. Un-insall the the network adapter that is show as greyed out and then you can scan for the hardware again and check if this detects it again and re-installs it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;You may also check the log file setupapi.dev.log file for any issues at the hardware level.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, there was a know issue documented by Microsoft which is&amp;nbsp;&lt;A href="https://support.microsoft.com/en-in/help/2846340/duplicate-friendly-names-of-network-adapters-are-displayed-in-windows" target="_blank"&gt;https://support.microsoft.com/en-in/help/2846340/duplicate-friendly-names-of-network-adapters-are-displayed-in-windows&lt;/A&gt; . You may want to run Windows update for any know issues that might have been fixed by Microsoft.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Aug 2018 14:55:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016106#M13081</guid>
      <dc:creator>Taurus78</dc:creator>
      <dc:date>2018-08-27T14:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Server 2016 Unidentified Network on HP ProLiant server restart</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016192#M13082</link>
      <description>&lt;P&gt;This is new servers. I installed them recently.&lt;/P&gt;&lt;P&gt;I don't see new devices after command Set devmgr_show_nonpresent_devices=1&lt;/P&gt;&lt;P&gt;This is two new servers. I have many other servers. I do not see this error any other servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 07:45:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016192#M13082</guid>
      <dc:creator>androsovms</dc:creator>
      <dc:date>2018-08-28T07:45:20Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Server 2016 Unidentified Network on HP ProLiant server restart</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016194#M13083</link>
      <description>&lt;P&gt;Well, it looks this might need indepth investigation and i would suggest you open a ticket with HPE.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I Thank you for your cooperation in this regard.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 07:52:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/windows-server-2016-unidentified-network-on-hp-proliant-server/m-p/7016194#M13083</guid>
      <dc:creator>Taurus78</dc:creator>
      <dc:date>2018-08-28T07:52:33Z</dc:date>
    </item>
  </channel>
</rss>

