<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Windows-Customization on Jon's Notes</title><link>https://4c4806b4.configjon-blog.pages.dev/category/windows-customization/</link><description>Recent content in Windows-Customization on Jon's Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 26 Jun 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://4c4806b4.configjon-blog.pages.dev/category/windows-customization/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows Customizations with PowerShell</title><link>https://4c4806b4.configjon-blog.pages.dev/windows-customizations-with-powershell/</link><pubDate>Wed, 26 Jun 2019 00:00:00 +0000</pubDate><guid>https://4c4806b4.configjon-blog.pages.dev/windows-customizations-with-powershell/</guid><description>&lt;p&gt;The out of the box Windows 10 experience has improved over the years, but I still find most clients I work with want to make various tweaks and modifications to the default settings. In the past I would add these customizations to a Configuration Manager task sequence as individual steps. But I&amp;rsquo;m lazy, and I didn&amp;rsquo;t want to have to continually add each individual step over and over. Plus I like to keep task sequences shorter when I can. The solution was to create a PowerShell script that allows the admin to select which of the common Windows customizations to run in their environment.&lt;/p&gt;</description></item></channel></rss>