<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: How to Prevent Truncation of Long Output in Exchange Management Shell</title>
	<atom:link href="http://exchangeserverpro.com/how-to-prevent-truncation-of-long-output-in-exchange-management-shell/feed" rel="self" type="application/rss+xml" />
	<link>http://exchangeserverpro.com/how-to-prevent-truncation-of-long-output-in-exchange-management-shell</link>
	<description>Microsoft Exchange Server News - Tips - Tutorials</description>
	<lastBuildDate>Tue, 22 May 2012 08:50:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Exchange Proxy Address (alias) Report &#171; Mike Crowley&#039;s Whiteboard</title>
		<link>http://exchangeserverpro.com/how-to-prevent-truncation-of-long-output-in-exchange-management-shell#comment-7419</link>
		<dc:creator>Exchange Proxy Address (alias) Report &#171; Mike Crowley&#039;s Whiteboard</dc:creator>
		<pubDate>Mon, 16 Apr 2012 18:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1082#comment-7419</guid>
		<description>[...] there are ways (example1, example2) to manipulate this output on the screen, I recently needed to create a complete list of all users [...]</description>
		<content:encoded><![CDATA[<p>[...] there are ways (example1, example2) to manipulate this output on the screen, I recently needed to create a complete list of all users [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchange Management-Shell &#8211; Ausgabe wird abgeschnitten (&#8230;) &#171; IT und Ihre Tücken</title>
		<link>http://exchangeserverpro.com/how-to-prevent-truncation-of-long-output-in-exchange-management-shell#comment-5586</link>
		<dc:creator>Exchange Management-Shell &#8211; Ausgabe wird abgeschnitten (&#8230;) &#171; IT und Ihre Tücken</dc:creator>
		<pubDate>Thu, 17 Nov 2011 09:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1082#comment-5586</guid>
		<description>[...] Der englische Artikel in dem ich den Hinweis fand. [...]</description>
		<content:encoded><![CDATA[<p>[...] Der englische Artikel in dem ich den Hinweis fand. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to Add Remote IP Addresses to Existing Receive Connectors &#124; Exchange Server Pro</title>
		<link>http://exchangeserverpro.com/how-to-prevent-truncation-of-long-output-in-exchange-management-shell#comment-1210</link>
		<dc:creator>How to Add Remote IP Addresses to Existing Receive Connectors &#124; Exchange Server Pro</dc:creator>
		<pubDate>Tue, 05 Jan 2010 01:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1082#comment-1210</guid>
		<description>[...] Note: if the list of IP addresses is too long and is being truncated in the shell output see this tip for extending the enumeration limit. [...]</description>
		<content:encoded><![CDATA[<p>[...] Note: if the list of IP addresses is too long and is being truncated in the shell output see this tip for extending the enumeration limit. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Cunningham</title>
		<link>http://exchangeserverpro.com/how-to-prevent-truncation-of-long-output-in-exchange-management-shell#comment-1188</link>
		<dc:creator>Paul Cunningham</dc:creator>
		<pubDate>Thu, 17 Dec 2009 23:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1082#comment-1188</guid>
		<description>Hi Mike, actually I don&#039;t edit the Exchange.ps1 file, I just change the variable at the cmd line for that current session.

It might make sense to configure a higher limit in your Powershell profile but I&#039;ve read it can cause problems with some other output scenarios, so I just bump it up as required per-session.</description>
		<content:encoded><![CDATA[<p>Hi Mike, actually I don&#8217;t edit the Exchange.ps1 file, I just change the variable at the cmd line for that current session.</p>
<p>It might make sense to configure a higher limit in your Powershell profile but I&#8217;ve read it can cause problems with some other output scenarios, so I just bump it up as required per-session.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Koch</title>
		<link>http://exchangeserverpro.com/how-to-prevent-truncation-of-long-output-in-exchange-management-shell#comment-1187</link>
		<dc:creator>Mike Koch</dc:creator>
		<pubDate>Thu, 17 Dec 2009 20:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://exchangeserverpro.com/?p=1082#comment-1187</guid>
		<description>Exchange.ps1 contains a signature block. Doesn&#039;t modifying the $FormatEnumerationLimit variable break the signature, and will that affect the shell&#039;s ability to load that PS1 file?</description>
		<content:encoded><![CDATA[<p>Exchange.ps1 contains a signature block. Doesn&#8217;t modifying the $FormatEnumerationLimit variable break the signature, and will that affect the shell&#8217;s ability to load that PS1 file?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

