<?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>Andrew Morgan &#187; oneliner</title>
	<atom:link href="http://andrewmorgan.ie/tag/oneliner/feed/" rel="self" type="application/rss+xml" />
	<link>http://andrewmorgan.ie</link>
	<description>Grumpy ramblings</description>
	<lastBuildDate>Fri, 30 Jun 2017 09:24:25 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.0</generator>
	<item>
		<title>Exporting XenApp policys with powershell.</title>
		<link>http://andrewmorgan.ie/2011/03/exporting-xenapp-policys-with-powershell/</link>
		<comments>http://andrewmorgan.ie/2011/03/exporting-xenapp-policys-with-powershell/#comments</comments>
		<pubDate>Tue, 29 Mar 2011 11:17:25 +0000</pubDate>
		<dc:creator><![CDATA[andyjmorgan]]></dc:creator>
				<category><![CDATA[Citrix]]></category>
		<category><![CDATA[PowerShell Scripting]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[XenApp]]></category>
		<category><![CDATA[oneliner]]></category>
		<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[xenapp]]></category>

		<guid isPermaLink="false">http://andymorgan.wordpress.com/?p=402</guid>
		<description><![CDATA[I needed to export our XenApp policies, as both a backup and a reference for an upcoming proof of concept involving XenApp 6. As no migration path is available, having the exported policies in a text document I can keep them open side by side while creating the new policies. The following assumes your have the Xenapp Cmdlets installed and called. foreach ($policy in get-xapolicy) {get-xapolicyconfiguration $policy.policyname &#124; out-file &#8220;$env:temp$policy.txt&#8221;} if you would prefer xml files: foreach ($policy in get-xapolicy) [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><a href="/wp-content/uploads/2011/03/windows_powershell_icon.png"><img class="alignright size-full wp-image-403" title="Windows_PowerShell_icon" src="/wp-content/uploads/2011/03/windows_powershell_icon.png" alt="" width="78" height="78" /></a>I needed to export our XenApp policies, as both a backup and a reference for an upcoming proof of concept involving XenApp 6. As no migration path is available, having the exported policies in a text document I can keep them open side by side while creating the new policies.</p>
<p>The following assumes your have the Xenapp Cmdlets installed and called.</p>
<p style="padding-left:30px;"><em>foreach ($policy in get-xapolicy) {get-xapolicyconfiguration $policy.policyname | out-file &#8220;$env:temp$policy.txt&#8221;}</em></p>
<p>if you would prefer xml files:</p>
<p style="padding-left:30px;"><em>foreach ($policy in get-xapolicy) {get-xapolicyconfiguration $policy.policyname | export-clixml &#8220;$env:temp$policy.xml&#8221;} </em></p>
<p>The above script dumps the policys in the chosen format to your temp folder. To auto jump to temp add &#8220;explorer $Env:temp&#8221; to the end of the line. E.G:</p>
<p style="padding-left:30px;"><em>foreach ($policy in get-xapolicy) {get-xapolicyconfiguration $policy.policyname | export-clixml &#8220;$env:temp$policy.xml&#8221;} <strong>explorer $env:temp</strong></em></p>
]]></content:encoded>
			<wfw:commentRss>http://andrewmorgan.ie/2011/03/exporting-xenapp-policys-with-powershell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
