<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Intermediate &#8211; Tulips, Windmills &amp; PowerShell: Dutch Scripting Guys</title>
	<atom:link href="https://dutchscriptingguys.com/tag/intermediate/feed/" rel="self" type="application/rss+xml" />
	<link>https://dutchscriptingguys.com</link>
	<description></description>
	<lastBuildDate>Sun, 14 Dec 2025 14:17:30 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://dutchscriptingguys.com/wp-content/uploads/2024/10/cropped-Logo_vierkant-scaled-1-32x32.jpg</url>
	<title>Intermediate &#8211; Tulips, Windmills &amp; PowerShell: Dutch Scripting Guys</title>
	<link>https://dutchscriptingguys.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>A way to Secure Credentials in Your PowerShell Scripts</title>
		<link>https://dutchscriptingguys.com/a-way-to-secure-credentials-in-your-powershell-scripts/</link>
					<comments>https://dutchscriptingguys.com/a-way-to-secure-credentials-in-your-powershell-scripts/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 15 Dec 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Quick Learnings]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1287</guid>

					<description><![CDATA[Storing credentials in plain text within scripts is a common but risky practice. While it may seem convenient for automation, it exposes sensitive data to anyone with access to the code. In this article, we explore a safer approach using PowerShell’s ConvertTo-SecureString and ConvertFrom-SecureString to encrypt passwords tied to a specific user and machine. This method significantly reduces the risk of credential leaks while keeping automation seamless.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/a-way-to-secure-credentials-in-your-powershell-scripts/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>When Automation Goes Wrong: A Painful Lesson in PowerShell</title>
		<link>https://dutchscriptingguys.com/when-automation-goes-wrong-a-painful-lesson-in-powershell/</link>
					<comments>https://dutchscriptingguys.com/when-automation-goes-wrong-a-painful-lesson-in-powershell/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 01 Dec 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1276</guid>

					<description><![CDATA[Have you ever written a script that worked perfectly in testing, only to cause chaos in production? I have, and it was one of the most stressful days of my career.

This experience changed how I write scripts. More checks, fewer assumptions, and no blind trust in defaults.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/when-automation-goes-wrong-a-painful-lesson-in-powershell/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Switch Statements in PowerShell: The Swiss Army Knife of Decision Making</title>
		<link>https://dutchscriptingguys.com/switch-statements-in-powershell-the-swiss-army-knife-of-decision-making/</link>
					<comments>https://dutchscriptingguys.com/switch-statements-in-powershell-the-swiss-army-knife-of-decision-making/#respond</comments>
		
		<dc:creator><![CDATA[Casper Stekelenburg]]></dc:creator>
		<pubDate>Mon, 24 Nov 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Quick Learnings]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1265</guid>

					<description><![CDATA[Switch statements in PowerShell are like the Swiss Army knife of control flow &#8211; they can handle multiple conditions with the elegance of a ballet dancer and the efficiency of a German engineer. Think of them as the sophisticated cousin of the if-else statement who went to college, learned multiple languages, and now works at [&#8230;]]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/switch-statements-in-powershell-the-swiss-army-knife-of-decision-making/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Enums in PowerShell: Strongly Typed Values for Robust Scripts</title>
		<link>https://dutchscriptingguys.com/enums-in-powershell-strongly-typed-values-for-robust-scripts/</link>
					<comments>https://dutchscriptingguys.com/enums-in-powershell-strongly-typed-values-for-robust-scripts/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 17 Nov 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Deep Dive]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1267</guid>

					<description><![CDATA[Enums in PowerShell provide a clean way to work with strongly typed values, improving readability, maintainability, and reducing errors. By grouping related constants under a single type, you avoid magic numbers and hardcoded strings, gain autocompletion, and enable built-in validation in functions. Whether you use native syntax, Add-Type with C#, or classes with static properties, enums make your scripts more robust and easier to manage.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/enums-in-powershell-strongly-typed-values-for-robust-scripts/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Dot Sourcing in PowerShell: The Art of Script Inclusion (Without the Drama)</title>
		<link>https://dutchscriptingguys.com/dot-sourcing-in-powershell-the-art-of-script-inclusion-without-the-drama/</link>
					<comments>https://dutchscriptingguys.com/dot-sourcing-in-powershell-the-art-of-script-inclusion-without-the-drama/#respond</comments>
		
		<dc:creator><![CDATA[Casper Stekelenburg]]></dc:creator>
		<pubDate>Mon, 10 Nov 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Intermediate]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1260</guid>

					<description><![CDATA[Dot sourcing is like the PowerShell equivalent of borrowing your neighbor&#8217;s tools &#8211; except instead of forgetting to return them, you get to keep everything permanently in your workspace. It&#8217;s a powerful feature that allows you to run a script in the current scope rather than in a new, child scope, making all its goodies [&#8230;]]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/dot-sourcing-in-powershell-the-art-of-script-inclusion-without-the-drama/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>PowerShell: Hashtable vs PSCustomObject Explained</title>
		<link>https://dutchscriptingguys.com/powershell-hashtable-vs-pscustomobject-explained/</link>
					<comments>https://dutchscriptingguys.com/powershell-hashtable-vs-pscustomobject-explained/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 03 Nov 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Deep Dive]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1248</guid>

					<description><![CDATA[Hashtables and PSCustomObjects may look similar in PowerShell, but they serve very different purposes. This post explores their syntax, performance, and practical use cases, helping you choose the right structure for dynamic data handling or clean output formatting.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/powershell-hashtable-vs-pscustomobject-explained/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Why Your Intune File Commits Fail in PowerShell 7.4+</title>
		<link>https://dutchscriptingguys.com/why-your-intune-file-commits-fail-in-powershell-7-4/</link>
					<comments>https://dutchscriptingguys.com/why-your-intune-file-commits-fail-in-powershell-7-4/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Fri, 03 Oct 2025 11:46:01 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Quick Learnings]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1242</guid>

					<description><![CDATA[PowerShell 7.4 introduces a subtle but impactful change: the default encoding for HTTP requests is now UTF-8 instead of ASCII. This shift can cause unexpected issues when working with the Microsoft Graph API, particularly during .intunewin file commits in Intune. In this post, I explain the root cause, share workarounds, and offer practical solutions to keep your automation workflows running smoothly.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/why-your-intune-file-commits-fail-in-powershell-7-4/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Automating LEGO Instruction Downloads with PowerShell</title>
		<link>https://dutchscriptingguys.com/automating-lego-instruction-downloads-with-powershell/</link>
					<comments>https://dutchscriptingguys.com/automating-lego-instruction-downloads-with-powershell/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 22 Sep 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1238</guid>

					<description><![CDATA[Tired of manually downloading LEGO building instructions? This PowerShell function automates the process by fetching the instruction page, filtering valid PDF links, and saving them neatly into a folder per set. Whether you're organizing your collection or just love scripting, this tool adds efficiency and fun to your LEGO hobby.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/automating-lego-instruction-downloads-with-powershell/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>PowerShell Remoting: Managing Multiple Systems from One Console</title>
		<link>https://dutchscriptingguys.com/powershell-remoting-managing-multiple-systems-from-one-console/</link>
					<comments>https://dutchscriptingguys.com/powershell-remoting-managing-multiple-systems-from-one-console/#respond</comments>
		
		<dc:creator><![CDATA[Casper Stekelenburg]]></dc:creator>
		<pubDate>Mon, 08 Sep 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1227</guid>

					<description><![CDATA[PowerShell Remoting lets you run commands, gather inventory, and automate fixes across dozens—or hundreds—of systems from one console. In this guide you’ll enable remoting safely, run one‑off commands with Invoke-Command, build persistent sessions for faster workflows, push scripts, move files, and troubleshoot connectivity like a pro. If you manage Windows servers or mixed environments, mastering these patterns will cut tedious RDP hops, standardize execution, and boost reliability—while keeping security (WinRM, auth, firewall, encryption) front and center.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/powershell-remoting-managing-multiple-systems-from-one-console/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Exploring Recursive Functions in PowerShell: A Backend Adventure</title>
		<link>https://dutchscriptingguys.com/exploring-recursive-functions-in-powershell-a-backend-adventure/</link>
					<comments>https://dutchscriptingguys.com/exploring-recursive-functions-in-powershell-a-backend-adventure/#respond</comments>
		
		<dc:creator><![CDATA[Jos Fissering]]></dc:creator>
		<pubDate>Mon, 25 Aug 2025 06:00:00 +0000</pubDate>
				<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[PowerShell]]></category>
		<guid isPermaLink="false">https://dutchscriptingguys.com/?p=1204</guid>

					<description><![CDATA[Discover how recursive functions work in PowerShell and why they’re perfect for navigating complex, nested data structures. Inspired by Boot.dev’s RPG-style learning, this post walks through a practical example using JSON and hashtables to build file paths recursively—ideal for backend developers looking to level up their scripting skills.]]></description>
		
					<wfw:commentRss>https://dutchscriptingguys.com/exploring-recursive-functions-in-powershell-a-backend-adventure/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
