<?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/"
	xmlns:series="https://publishpress.com/"
	>

<channel>
	<title>PowerShell &#8211; JPPinto.com &#8211; Tech Blog</title>
	<atom:link href="https://jppinto.com/powershell/feed/" rel="self" type="application/rss+xml" />
	<link>https://jppinto.com</link>
	<description>Seasoned IT Dude - Azure MCSE, MCSA, MCTS: SharePoint 2010, MCP</description>
	<lastBuildDate>Tue, 31 Dec 2019 15:31:21 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Windows 10 PATH Environment Variable Update with PowerShell</title>
		<link>https://jppinto.com/2019/12/windows-10-path-environment-variable-update-with-powershell/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Thu, 26 Dec 2019 03:26:37 +0000</pubDate>
				<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[Windows 10]]></category>
		<category><![CDATA[powershell]]></category>
		<category><![CDATA[path environment variable]]></category>
		<category><![CDATA[environment variable]]></category>
		<guid isPermaLink="false">http://www.jppinto.com/?p=1867</guid>

					<description><![CDATA[Testing Environment Information: Windows 10 Enterprise: Version 1909 (OS Build 18396.535) (Type winver or systeminfo at a Command Prompt) PowerShell Version: 5.1.18362.145 (Type &#8220;HOST&#8221; at a PowerShell Prompt) Testing Date: 12/25/2019 Background: Unfortunately, when using the following PowerShell command, it erases all other entries in your PATH Environment Variable. Most forums I&#8217;ve seen are telling [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Update Enom Domain Name via PowerShell (Dynamic DNS Update)</title>
		<link>https://jppinto.com/2014/09/update-enom-domain-name-via-powershell-dynamic-dns-update/</link>
		
		<dc:creator><![CDATA[JPPinto]]></dc:creator>
		<pubDate>Thu, 25 Sep 2014 05:15:34 +0000</pubDate>
				<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[dynamic dns]]></category>
		<category><![CDATA[enom domain name update]]></category>
		<category><![CDATA[update enom name]]></category>
		<category><![CDATA[update dns record]]></category>
		<category><![CDATA[free dynamic dyn. dyndns free]]></category>
		<guid isPermaLink="false">http://www.jppinto.com/?p=1815</guid>

					<description><![CDATA[DynDNS.org, the awesome service that lets you access your home computers from anywhere, recently announced that it&#8217;s getting rid of its free accounts. The most basic account now costs $25 per year. Fortunately, we can use PowerShell to keep our DNS names updated with the latest public IP Address from our Internet Service Provider for [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>How to check if a Domain User exists using PowerShell without loading AD Snap-Ins</title>
		<link>https://jppinto.com/2014/08/checking-domain-user-exists-using-powershell-without-loading-ad-snap-ins/</link>
		
		<dc:creator><![CDATA[JPPinto]]></dc:creator>
		<pubDate>Mon, 18 Aug 2014 08:41:04 +0000</pubDate>
				<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[powershell]]></category>
		<category><![CDATA[get user]]></category>
		<category><![CDATA[get domain user]]></category>
		<category><![CDATA[check user exist]]></category>
		<category><![CDATA[check user]]></category>
		<guid isPermaLink="false">http://www.jppinto.com/?p=1794</guid>

					<description><![CDATA[I was trying to run &#8220;New-SPSite&#8221; to create a Site Collection in SharePoint. I accidentally typed in the wrong username as the owner so I received an error. Upon investigation there is not a quick and simple way to see if a user exists outside of SharePoint before its added. Most recommended solutions require you [&#8230;]]]></description>
		
		
		
			</item>
	</channel>
</rss>
