<?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>Group Policy | RobWillis.info</title>
	<atom:link href="/tag/group-policy/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>#yolosec</description>
	<lastBuildDate>Mon, 20 Jan 2020 11:48:39 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>Disabling PowerShell v2 with Group Policy</title>
		<link>/2020/01/disabling-powershell-v2-with-group-policy/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Mon, 20 Jan 2020 11:39:09 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[PowerShell/Scripting]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[10]]></category>
		<category><![CDATA[2012]]></category>
		<category><![CDATA[2016]]></category>
		<category><![CDATA[2019]]></category>
		<category><![CDATA[Disable]]></category>
		<category><![CDATA[Dism]]></category>
		<category><![CDATA[DismOpenSession failed]]></category>
		<category><![CDATA[Downgrade Attack]]></category>
		<category><![CDATA[Error code = 0x80040154]]></category>
		<category><![CDATA[GPO]]></category>
		<category><![CDATA[Group Policy]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[v2]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[WindowsOptionalFeature]]></category>
		<guid isPermaLink="false">/?p=4855</guid>

					<description><![CDATA[<p>In this post I am going to tackle something that I have been wanting to play around with for awhile, disabling PowerShell v2 at an enterprise scale. As a former systems engineer and now a security engineer, I have a love/hate relationship with PowerShell since it is amazingly useful but also incredibly dangerous in the [&#8230;]</p>
The post <a href="/2020/01/disabling-powershell-v2-with-group-policy/">Disabling PowerShell v2 with Group Policy</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Everything You Need To Know To Get Started Logging PowerShell</title>
		<link>/2019/10/everything-you-need-to-know-to-get-started-logging-powershell/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Mon, 07 Oct 2019 00:15:30 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[Pen Testing]]></category>
		<category><![CDATA[PowerShell/Scripting]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[4103]]></category>
		<category><![CDATA[4104]]></category>
		<category><![CDATA[Downgrade Attacks]]></category>
		<category><![CDATA[ELK]]></category>
		<category><![CDATA[Get-PSEventLogSize]]></category>
		<category><![CDATA[GPO]]></category>
		<category><![CDATA[Group Policy]]></category>
		<category><![CDATA[Module]]></category>
		<category><![CDATA[Obfuscated]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Restricted]]></category>
		<category><![CDATA[Script block]]></category>
		<category><![CDATA[SD]]></category>
		<category><![CDATA[Security Descriptor]]></category>
		<category><![CDATA[Tool]]></category>
		<category><![CDATA[Transcription]]></category>
		<guid isPermaLink="false">/?p=4432</guid>

					<description><![CDATA[<p>Intro Recently, I have been spending a lot of time researching and working with PowerShell logging. Since PowerShell is readily available (built-in to the OS) and has an assortment of functionality that can be used across the entire kill chain right out of the box, it is an ideal candidate for virtually any type of [&#8230;]</p>
The post <a href="/2019/10/everything-you-need-to-know-to-get-started-logging-powershell/">Everything You Need To Know To Get Started Logging PowerShell</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Powershell scripts fail when deployed via Group Policy as Startup scripts with Event ID 1055 and 1130</title>
		<link>/2017/10/powershell-scripts-fail-when-deployed-via-group-policy-as-startup-scripts-with-event-id-1055-and-1130/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Mon, 02 Oct 2017 07:27:23 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[PowerShell/Scripting]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[1055]]></category>
		<category><![CDATA[1130]]></category>
		<category><![CDATA[2012]]></category>
		<category><![CDATA[Event ID]]></category>
		<category><![CDATA[Failure]]></category>
		<category><![CDATA[GPO]]></category>
		<category><![CDATA[Group Policy]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[R2]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[Startup]]></category>
		<category><![CDATA[Windows]]></category>
		<guid isPermaLink="false">/?p=3354</guid>

					<description><![CDATA[<p>I recently went to deploy a new Powershell based Startup script in my test environment, and while the majority of my Windows machines happily complied, 2 of my test servers that were running Remote Desktop Services did not like the new Startup policy. The script itself was pretty straight forward &#8211; it pulled some files [&#8230;]</p>
The post <a href="/2017/10/powershell-scripts-fail-when-deployed-via-group-policy-as-startup-scripts-with-event-id-1055-and-1130/">Powershell scripts fail when deployed via Group Policy as Startup scripts with Event ID 1055 and 1130</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Simple BGInfo AD logon script</title>
		<link>/2014/01/simple-bginfo-ad-logon-script/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Mon, 27 Jan 2014 16:43:50 +0000</pubDate>
				<category><![CDATA[PowerShell/Scripting]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[2008]]></category>
		<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[AD]]></category>
		<category><![CDATA[BGInfo]]></category>
		<category><![CDATA[GPO]]></category>
		<category><![CDATA[Group Policy]]></category>
		<category><![CDATA[Login]]></category>
		<category><![CDATA[Logon]]></category>
		<category><![CDATA[R2]]></category>
		<category><![CDATA[script]]></category>
		<guid isPermaLink="false">/?p=2247</guid>

					<description><![CDATA[<p>This is my simple logon script for the popular BGInfo utility that uses a few batch scripts along with Group Policy to run at each user login. What this script does: Checks to see if bginfo.exe exist on the local machine, if not copy it from the network share to c:\bginfo\ Copy bg.jpg and default.bgi [&#8230;]</p>
The post <a href="/2014/01/simple-bginfo-ad-logon-script/">Simple BGInfo AD logon script</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
	</channel>
</rss>
