<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on MV — Systems Field Notes</title>
    <link>https://mvdb.io/posts/</link>
    <description>Recent content in Posts on MV — Systems Field Notes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 11 Jul 2026 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://mvdb.io/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Build Resilient PowerShell Logging for Task Scheduler</title>
      <link>https://mvdb.io/posts/powershell-logging-that-survives-task-scheduler/</link>
      <pubDate>Sat, 11 Jul 2026 00:00:00 +0200</pubDate>
      <guid>https://mvdb.io/posts/powershell-logging-that-survives-task-scheduler/</guid>
      <description>A reusable pattern for scheduled PowerShell jobs that keeps one readable log per component per day without letting a transient append failure replace the actual job result.</description>
    </item>
    <item>
      <title>Diagnosing a Slow ‘Other User’ Sign-In on Windows Server</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>A two-to-three-minute pause at the Other User screen observed on a hybrid-joined server that could no longer reach Microsoft services.</description>
    </item>
    <item>
      <title>Fix Azure CLI ‘User cancelled the Accounts Control Operation’ on Windows</title>
      <link>https://mvdb.io/posts/az-login-failure/</link>
      <pubDate>Mon, 08 Jul 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/az-login-failure/</guid>
      <description>The three Azure CLI commands that restored interactive login after the Windows authentication broker returned Status_UserCanceled.</description>
    </item>
    <item>
      <title>Fix &#39;Source Agent Driver Version Is Not Supported&#39; in Azure Site Recovery</title>
      <link>https://mvdb.io/posts/azure-site-recovery-source-agent-driver-version-is-not-supported/</link>
      <pubDate>Thu, 04 Jul 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/azure-site-recovery-source-agent-driver-version-is-not-supported/</guid>
      <description>During a migration from a classic Azure Site Recovery (ASR) vault to modernized VMware replication, the migration wizard would not allow the virtual machines to be selected. It reported Source agent driver version is not supported, even though the agents had already been upgraded.&#xA;The missing step was straightforward: the virtual machines needed to restart after the agent upgrade.&#xA;Context Before starting the migration, deploy the modernized ASR vault in Azure and install the new ASR appliance.</description>
    </item>
    <item>
      <title>Deploying Azure Stack HCI 23H2: Installation and Azure Arc Setup</title>
      <link>https://mvdb.io/posts/azure-stack-hci-23h2-installation-and-setup-guide/</link>
      <pubDate>Tue, 14 May 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/azure-stack-hci-23h2-installation-and-setup-guide/</guid>
      <description>This walkthrough covers a representative deployment path for a two-node, switchless Azure Stack HCI 23H2 cluster: installing the operating system, preparing the nodes, registering them with Azure Arc, and deploying the cluster from the Azure portal.&#xA;The example topology uses a RAID controller configured in JBOD mode, dedicated high-speed storage adapters, and separate backup and compute adapters. Hardware vendors, interface identifiers, addresses, and resource names are intentionally generalized; adapt every selection to your validated design.</description>
    </item>
    <item>
      <title>Grant Logon Rights at Scale with Group Policy</title>
      <link>https://mvdb.io/posts/logon-as-a-service-batch-job-at-scale/</link>
      <pubDate>Wed, 10 Apr 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/logon-as-a-service-batch-job-at-scale/</guid>
      <description>In one environment, a service failed to start because its User Rights Assignment was configured incorrectly. The environment used one GPO per server to manage Log on as a service and Log on as a batch job. That worked, but it left the team maintaining many nearly identical policies.&#xA;A consolidated design uses one GPO, two local groups on each server, and per-server Active Directory groups. Group Policy Preferences expands the domain and computer-name variables on each target, so the same policy can grant rights to different accounts on every server.</description>
    </item>
    <item>
      <title>Connect a UniFi UDM-SE Directly to Proximus FTTH</title>
      <link>https://mvdb.io/posts/removing-the-isp-proximus-modem-for-an-ftth-connection/</link>
      <pubDate>Tue, 02 Apr 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/removing-the-isp-proximus-modem-for-an-ftth-connection/</guid>
      <description>The WAN and LAN settings I used to remove the Proximus gateway while keeping the fibre ONTP in place.</description>
    </item>
    <item>
      <title>Deploy a Site Printer from an IP Octet with PowerShell</title>
      <link>https://mvdb.io/posts/add-printers-based-on-ip-octet/</link>
      <pubDate>Thu, 28 Mar 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/add-printers-based-on-ip-octet/</guid>
      <description>Replace a slow 300-line VBScript with a focused PowerShell workflow for users who move between consistently addressed sites.</description>
    </item>
    <item>
      <title>Deploy Dell BIOS Settings and Per-Device Passwords with Intune</title>
      <link>https://mvdb.io/posts/deploy-dell-bios-settings-and-unique-per-device-bios-passwords-using-intune/</link>
      <pubDate>Thu, 28 Mar 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/deploy-dell-bios-settings-and-unique-per-device-bios-passwords-using-intune/</guid>
      <description>Dell provides a version of Command Configure specifically for Microsoft Intune. The important addition is support for a unique BIOS password per device, managed through Intune instead of shared across the fleet.&#xA;This walkthrough covers the full setup I used: create the Dell CCTK configuration, package and install Dell Command | Endpoint Configure as a Win32 app, deploy the Intune BIOS policy, and retrieve a device password through Microsoft Graph.</description>
    </item>
    <item>
      <title>Fix Azure Stack HCI &#39;Unable to Retrieve Data for PhysicalDisk&#39;</title>
      <link>https://mvdb.io/posts/azure-stack-hci-unable-to-retrieve-data-for-physicaldisk/</link>
      <pubDate>Thu, 28 Mar 2024 12:00:03 +0000</pubDate>
      <guid>https://mvdb.io/posts/azure-stack-hci-unable-to-retrieve-data-for-physicaldisk/</guid>
      <description>During an Azure Stack HCI prerequisite check, the nodes failed PhysicalDisk validation even though the storage configuration had the required data drives and the RAID controller was configured in JBOD mode. The example used NVMe data drives, but NVMe is not a universal requirement for every supported design.&#xA;The validator&amp;rsquo;s headline message—Unable to retrieve data for PhysicalDisk—did not identify the underlying problem. The useful clue came from comparing the validator&amp;rsquo;s accepted bus types with what Windows reported for the disks.</description>
    </item>
  </channel>
</rss>
