<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Windows Server on Exploring IT with Michaël</title>
    <link>https://mvdb.io/tags/windows-server/</link>
    <description>Recent content in Windows Server on Exploring IT with Michaël</description>
    <image>
      <title>Exploring IT with Michaël</title>
      <url>https://mvdb.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://mvdb.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.127.0</generator>
    <language>en</language>
    <lastBuildDate>Mon, 14 Oct 2024 12:00:03 +0000</lastBuildDate>
    <atom:link href="https://mvdb.io/tags/windows-server/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Windows Server: Other User slow login process</title>
      <link>https://mvdb.io/posts/other-user-slow-login-process/</link>
      <pubDate>Mon, 14 Oct 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/other-user-slow-login-process/</guid>
      <description>At my customer, we had 1 Windows Server with quite a slow login process. The screen would be stuck on &amp;ldquo;Other User&amp;rdquo; for about 2-3 minutes every time a new user tried to login or unlock the locked account.
After checking a few things, we noticed that the server is Hybrid AD joined.
dsregcmd /status We have the server leave the Hybrid AD join with the below command.
dsregcmd /leave And when we check the status now, the server is no longer Hybrid joined and the login process is faster.</description>
    </item>
  </channel>
</rss>
