Tech Trends and Insights

📌 Description This PowerShell script is used to extract the Windows Autopilot hardware hash (HWID) from a device and save it as a CSV file directly to a USB drive . Each file is created with a unique filename based on device model, serial number, and timestamp. During execution, you are prompted to enter a Group Tag . The Group Tag is written directly into the CSV file and is later used by Windows Autopilot to automatically assign the device to the correct device groups, deployment profiles, and Microsoft Intune policies. This approach is commonly used when manually collecting hardware hashes instead of paying a hardware vendor to unpack devices and pre-register them in Autopilot. By extracting the HWID in-house (for example during OOBE) and saving it to USB, organizations can reduce costs , keep full control , and still ensure devices are fully prepared for automated deployment.   🚀 Features Extracts Windows Autopilot hardware hash (HWID) Automatically adds a...

  Overview The RemoveMicrosoftCopilotApp policy allows IT administrators to uninstall the built‑in Microsoft Copilot app from Windows devices in a controlled way. The goal is to provide one unified Copilot experience , typically Microsoft 365 Copilot. Requirements This policy applies only when all of the following are true: Microsoft 365 Copilot is installed Microsoft Copilot was not installed by the user Microsoft Copilot has not been launched in the last 28 days Windows 11 version 25H2 with KB5083769 or later Supported editions: Pro, Enterprise, Education, IoT Enterprise Policy Paths (CSP) You can configure the policy either per user or per device: User scope ./User/Vendor/MSFT/Policy/Config/WindowsAI/RemoveMicrosoftCopilotApp Device scope ./Device/Vendor/MSFT/Policy/Config/WindowsAI/RemoveMicrosoftCopilotApp Configuration Format: Integer Allowed values: 0 – Removal disabled 1 – Removal enabled When set to 1 , the Microsoft Copilot app is uninstalled automatically . Users c...

This PowerShell script is intended for kiosk environments deployed using Windows Autopilot and Microsoft Intune . 📌 What This Script Does The script automatically empties all standard user libraries for a specified kiosk user (default: kioskuser0 ): Downloads Desktop Documents Pictures Music Videos It is designed to work reliably even in offline , restricted , or library/public kiosk environments where cloud-based or user-scoped cleanup policies may fail. 🛡️ Key Capabilities (Summary) A dedicated cleanup script is stored in C:\ProgramData A scheduled task runs daily at 20:30 as SYSTEM All cleanup actions are logged for traceability Supports simulation mode (WhatIf), install-only, and manual execution ⚠️ Purpose The purpose of this script is to ensure that all common user libraries are cleared regularly on kiosk devices, preventing data accumulation, protecting user privacy, and maintaining a clean and predictable kiosk experienc...

What does this policy do? This policy removes the “Recommended” section from the Windows 11 Start menu, leaving only pinned apps visible. Why use this on kiosk computers? Improves privacy – no recently opened files or apps are shown Cleaner interface – easier for public users to understand Prevents confusion – avoids showing content users can’t access This is best practice for shared or public kiosks . Supported Windows 11 Microsoft Intune Works with Assigned Access (single‑app and multi‑app kiosks) Intune Configuration (OMA‑URI) Create a Custom profile and add: Setting Value OMA‑URI /Vendor/MSFT/Policy/Config/Start/HideRecommendedSection Data type Integer Value 1 (Enabled) Assign the profile to a device group for kiosk computers. Result Start menu shows only pinned apps No Recommended apps or files Consistent experience for all kiosk users

🚀 Secure Windows Kiosk Deployment with Assigned Access & Intune This configuration demonstrates how to build a secure and controlled Windows kiosk environment using Assigned Access (Kiosk Mode) together with modern deployment tools like Windows Autopilot and Microsoft Intune . 📌 What This Script Does Before applying the Assigned Access XML, you must run the following PowerShell script. The script is a fully local, Intune remediation‑optimized wallpaper and lockscreen manager . It guarantees that the kiosk device always uses the correct background and lockscreen images — stored locally on the system. It is designed to work reliably even in offline , restricted , or library/public kiosk environments where cloud‑based personalization policies may fail. 🛡️ Key Capabilities (Summary) Creates/maintains the folder C:\Kiosk Uses two image files : background.jpg → Desktop wallpaper kiosk_lockscreen.jpg → Lock screen Applies both i...

  🚀 Secure Windows Kiosk Deployment with Assigned Access & Intune This configuration demonstrates how to build a secure and controlled Windows kiosk environment using Assigned Access (Kiosk Mode) together with modern deployment tools like Windows Autopilot and Microsoft Intune . ⚠️ Prerequisite – Required Before Assigned Access Before applying the Assigned Access XML, you must run the following PowerShell script . This step creates the required Start Menu shortcut used in the configuration. If skipped, Assigned Access may fail or not apply correctly . PowerShell – Create File Explorer Shortcut $pinFolder = "$env:PROGRAMDATA\Microsoft\Windows\Start Menu\Programs\Kiosk" New-Item -Path $pinFolder -ItemType Directory -Force | Out-Null $lnkPath = Join-Path $pinFolder "FileExplorer.lnk" $target = "$env:WINDIR\explorer.exe" $ws = New-Object -ComObject WScript.Shell $sc = $ws.CreateShortcut($lnkPath) $sc...