As you may have noticed by now, there doesn’t seem to be any nice built in way to set environmental variables in intune 🙁 The Problem Setting a user environmental variable using powershell is an easy task to accomplish, you basically just run the following: 1 Set-ItemProperty -Path HKCU:\Environment -Name temp -Value "c:\temp\" This works just fine, but won’t take effect until the user either reboots or signs into the device again.
So you have already figured out how to dynamically generated outlook signatures, but now you want to make sure that people actually use them. but without preventing the use of other signatures your users might have. Well it just so happens that I have a solution for you! No default signature has been set To do all this, we create a new Proactive Remediation in Intune. Add the detection and remediations scripts from below, and set it to run as the user.
Have you ever looked at a report on a Portal Page and wanted to know just WHERE the data just came from? Well you can - and finding the information can be so easy. Read on below to see how. Introduction Take for example this report on a Proactive Remediation. I used one of the built in Proactive Remediations for the example, but it could easily be one of our other Proactive Remediation posts, like Dynamic Outlook Signatures, Building VPN Connections, or Repairing Folder permissions.
⚠️ UPDATE (2023-03-11) ⚠️ Due to changes introduced by Microsoft in KB5014754 and being enforced on November 14, 2023, the name mapping method used in the scripts below will no longer work, and authentication will fail at that time. Thankfully, commenter Anders Hannus has pointed out a policy module named TameMyCerts for Microsoft Active Directory Certificate Services (AD CS). This policy module, used in conjunction with the below scripts, will let us work around Microsoft’s changes and give us the added benefit of no longer needing name mappings that are insecure.
Hello, This is a long and overdue update on a solution I started working on last year to allow my organization to use the modern driver management solution without the need of the custom webservice. I also wanted the solution to use the built-in task sequence steps as much as possible to allow other administrators to customize the solution to their need without the need to go modify a big PowerShell script.
Introduction In this post I’ll show you how you can create a new boot image in ConfigMgr. There’s plenty of good content out there already on this, but I was interested to write this because I didn’t see many PowerShell examples out there until I came across Michael Niehaus’ post on Build your own Windows PE image. A fantastic post, highly recommend reading it. Michael provided a useful script at the end of this post in a .
Distribution Points are great, but they can often be a huge annoyance. Getting content distributed is one thing, but then making sure it STAYS distributed, and old things are getting cleaned up, and making sure all the content hashes are correct, etc. It’s easy to feel like you’re constantly drowning in a sea of DP warnings and errors. Luckily, there’s some simple things we can do to take this burden away.
Introduction In this post I’m going to share with you a task sequence for ConfigMgr / SCCM / MEMCM / MECM / MCM (this is just getting silly now) that localises Windows 10 to a language other than the default language of the OS install media. This is a follow up from my previous post Language Packs, Language Experience Packs, Language Interface Packs… what?! In that post I broke down the necessary bits in order to understand how to localise a Windows system.
I volunteer to help run Southwest CCDC every year, and had a need to deploy all of the communication infrastructure in a hurry. With Covid Times™ upon us, we needed to move a competition that usually has at least one round in person to all-virtual. Discord was the obvious choice for how to do that successfully - it is targeted to communities of people, and has moderation tools. My discord server needed to have a few things:
Have you ever wanted to get a simple notification when there is a new Release for your favorite PowerShell Module or other Public Repo on GitHub? In this post we’ll talk about how you can use Power Automate to watch for new releases and trigger events on these and send out Teams messages, Emails, or even Kick off an Azure Function or similar automation. Introduction In my previous post, we did some automation with client-side scripts and Microsoft Graph to update Outlook Auto-Responses on a schedule.