<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Powershell on Network Haven</title>
    <link>/tags/powershell/</link>
    <description>Recent content in Powershell on Network Haven</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 10 Apr 2026 23:10:03 +0200</lastBuildDate>
    <atom:link href="/tags/powershell/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Issue detecting domain network on domain controller when using NIC teaming</title>
      <link>/posts/2026/issue-detecting-domain-network-on-domain-controller-when-using-nic-teaming/</link>
      <pubDate>Fri, 10 Apr 2026 23:10:03 +0200</pubDate>
      <guid>/posts/2026/issue-detecting-domain-network-on-domain-controller-when-using-nic-teaming/</guid>
      <description>&lt;p&gt;We had an issue where our domain controller lost its domain network profile after a reboot. When it came back up it was set to public instead of domain.&lt;/p&gt;&#xA;&lt;p&gt;The problem occurred only when Windows NIC teaming (switch-independent) was used in combination with two network adapters in the team. As soon as one network adapter was disabled from the team (while the other remained active), the network profile (domain) was recognized correctly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
