https://mvdb.io/posts/ Recent content in Posts on Exploring IT with Michaël https://mvdb.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E https://mvdb.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E Hugo -- 0.127.0 en Sun, 01 Dec 2024 01:00:03 +0000 https://mvdb.io/posts/how-i-discovered-a-moroccan-scammer-ring-by-accident/ Sun, 01 Dec 2024 01:00:03 +0000 https://mvdb.io/posts/how-i-discovered-a-moroccan-scammer-ring-by-accident/ This blog post describes how I discovered a (currently inactive) Moroccan scam ring. In 2021, I started looking for a short .com domain for a potential business in the future. After a lot searching I finally landed on cotyx.com that was available and only 5 letters long! As any IT person would, I added it to M365 and didn’t think much more about it. In 2024, to optimize my expenditure, and since I was closing my freelance company. https://mvdb.io/posts/other-user-slow-login-process/ Mon, 14 Oct 2024 12:00:03 +0000 https://mvdb.io/posts/other-user-slow-login-process/ At my customer, we had 1 Windows Server with quite a slow login process. The screen would be stuck on “Other User” 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. https://mvdb.io/posts/az-login-failure/ Mon, 08 Jul 2024 12:00:03 +0000 https://mvdb.io/posts/az-login-failure/ Today I started my journey on learning terraform. During the Azure login process in Powershell, I ran into the following error: User cancelled the Accounts Control Operation.. Status: Response_Status.Status_UserCanceled, Error code: 0, Tag: 528315210 I’ve never had this issue before, so I was a bit puzzled. It seems that since version 2.61.0, that the Web Account Manager (WAM) is now the default authentication method. Luckily we can bypass the WAM using PowerShell and proceed to login. https://mvdb.io/posts/azure-site-recovery-source-agent-driver-version-is-not-supported/ Thu, 04 Jul 2024 12:00:03 +0000 https://mvdb.io/posts/azure-site-recovery-source-agent-driver-version-is-not-supported/ I was recently busy migrating a customer from the classic ASR vault to the modernized ASR vault. However, during the process I ran into an issue. This post is to explain the issue and how you can easily resolve it yourself. In my scenario, I already deployed modern vault in Azure with a new ASR appliance. In your classic ASR vault, navigate to replicated items and click on Upgrade to modernized VMware replication. https://mvdb.io/posts/azure-stack-hci-23h2-installation-and-setup-guide/ Tue, 14 May 2024 12:00:03 +0000 https://mvdb.io/posts/azure-stack-hci-23h2-installation-and-setup-guide/ Navigate to the Azure portal -> Azure Arc -> Azure Stack HCI and click on Download Azure Stack HCI. Select the version, in this case we will go with the latest version and we agree to the terms and proceed to click on Download Azure Stack HCI. Flash the ISO on a USB device using rufus or a similar program, plug it into the server and enter the button to enter the boot menu. https://mvdb.io/posts/logon-as-a-service-batch-job-at-scale/ Wed, 10 Apr 2024 12:00:03 +0000 https://mvdb.io/posts/logon-as-a-service-batch-job-at-scale/ Recently at a customer there was an issue with a GPO and a service that couldn’t start due to User Rights Assignments being configured wrong. They were using a GPO per server to define this, but using a GPO per server isn’t very scalable and friendly to manage. The solution? Group policy preferences! We start by creating a GPO and navigating to Computer Configuration -> Preferences -> Control Panel Settings -> Local Users and Computers. https://mvdb.io/posts/removing-the-isp-proximus-modem-for-an-ftth-connection/ Tue, 02 Apr 2024 12:00:03 +0000 https://mvdb.io/posts/removing-the-isp-proximus-modem-for-an-ftth-connection/ After a very painful installation process to get Proximus Ultra Fiber (8.5Gbps down/1.5Gbps up) I decided to remove the Proximus modem between my UDM-SE and the ONTP. According to the Proximus documentation, for an FFTH installation this can be done by using VLAN 20 on the WAN port of the UDM-SE. We can configure this by navigating to Settings -> Internet -> Primary (WAN 1). Under advanced, we need to select Manual and check the box next to VLAN ID. https://mvdb.io/posts/add-printers-based-on-ip-octet/ Thu, 28 Mar 2024 12:00:03 +0000 https://mvdb.io/posts/add-printers-based-on-ip-octet/ At a previous company I worked at, we managed over 60+ sites, each with a dedicated /24 subnet and a preconfigured printer on a print server. The challenge was to automatically add the local printer and move printers from other sites when users traveled between sites. Initially, I used a heavily modified VBS script from a friend to address this issue. Although this solution worked, it was slow over 300 lines long. https://mvdb.io/posts/azure-stack-hci-unable-to-retrieve-data-for-physicaldisk/ Thu, 28 Mar 2024 12:00:03 +0000 https://mvdb.io/posts/azure-stack-hci-unable-to-retrieve-data-for-physicaldisk/ During the prerequisite check of Azure Stack HCI I came across an odd error related to the storage. I had the minimum requirements of 2 NVMe drives, an RAID card in JBOD mode. Type 'ValidateHardware' of Role 'EnvironmentValidator' raised an exception: Hardware requirements not met. Review output and remediate: Rule: HealthCheckSource : Deployment\Hardware\3bc73c2f Name : AzStackHci_Hardware_Test_PhysicalDisk DisplayName : Test PhysicalDisk API SERVERNAME1 Tags : {} Title : Test PhysicalDisk API Status : FAILURE Severity : CRITICAL Description : Checking PhysicalDisk has CIM data Remediation : https://learn. https://mvdb.io/posts/deploy-dell-bios-settings-and-unique-per-device-bios-passwords-using-intune/ Thu, 28 Mar 2024 12:00:03 +0000 https://mvdb.io/posts/deploy-dell-bios-settings-and-unique-per-device-bios-passwords-using-intune/ It seems that Dell now has a specific version of command configure that’s used for Intune. But why would we want to use it? Because it supports some neat features like an unique per device BIOS password that is managed by Intune. Download Dell Command | Configure Application and configure your desired BIOS settings. Click on Export config and save the CCTK file. Open the Microsoft Intune admin center portal and navigate to Devices -> Configuration.