<?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: Good advice hidden in the Infrastructure Update</title>
	<atom:link href="http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/</link>
	<description>After much frustration, it seems DEFAULT is the way to go...</description>
	<lastBuildDate>Tue, 09 Mar 2010 15:24:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SharePoint Infrastructure Update - So Far So Good &#171; The WorkerThread Blog</title>
		<link>http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/comment-page-1/#comment-1492</link>
		<dc:creator>SharePoint Infrastructure Update - So Far So Good &#171; The WorkerThread Blog</dc:creator>
		<pubDate>Mon, 04 Aug 2008 07:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/#comment-1492</guid>
		<description>[...] Paul Culmsee spotted that In the Deploy Software Updates document on TechNet, there is a section stating &#8220;To ensure that you have the correct permissions to install the software update and run the SharePoint Products and Technologies Configuration Wizard, we recommend that you add the account for the SharePoint Central Administration v3 application pool identity to the Administrators group on each of the local Web servers and application servers and then log on by using that account.&#8221;&#160; Not sure if this is new guidance - in the past I&#8217;ve applied updates while logged on as the install account, normally a local administrator with dbsecurity and dbcreator rights on SQL Server. [...]</description>
		<content:encoded><![CDATA[<p>[...] Paul Culmsee spotted that In the Deploy Software Updates document on TechNet, there is a section stating &#8220;To ensure that you have the correct permissions to install the software update and run the SharePoint Products and Technologies Configuration Wizard, we recommend that you add the account for the SharePoint Central Administration v3 application pool identity to the Administrators group on each of the local Web servers and application servers and then log on by using that account.&#8221;&nbsp; Not sure if this is new guidance &#8211; in the past I&#8217;ve applied updates while logged on as the install account, normally a local administrator with dbsecurity and dbcreator rights on SQL Server. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SharePoint Daily for July 21, 2008 - SharePoint Daily</title>
		<link>http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/comment-page-1/#comment-1347</link>
		<dc:creator>SharePoint Daily for July 21, 2008 - SharePoint Daily</dc:creator>
		<pubDate>Mon, 21 Jul 2008 15:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/#comment-1347</guid>
		<description>[...] Good Advice Hidden in the Infrastructure Update (Clever Workarounds)I guess the entire SharePoint world now is aware of the post SP1 &quot;Infrastructure updates&quot; put out by Microsoft recently. Probably the best thing about them are that the flaky &quot;content deployment&quot; feature has had some serious work done on it (I have always advised to use extreme caution and avoid it, but now I will have to reassess). [...]</description>
		<content:encoded><![CDATA[<p>[...] Good Advice Hidden in the Infrastructure Update (Clever Workarounds)I guess the entire SharePoint world now is aware of the post SP1 &quot;Infrastructure updates&quot; put out by Microsoft recently. Probably the best thing about them are that the flaky &quot;content deployment&quot; feature has had some serious work done on it (I have always advised to use extreme caution and avoid it, but now I will have to reassess). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FuzzLinks.com &#187; CleverWorkarounds » Good advice hidden in the Infrastructure Update</title>
		<link>http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/comment-page-1/#comment-1341</link>
		<dc:creator>FuzzLinks.com &#187; CleverWorkarounds » Good advice hidden in the Infrastructure Update</dc:creator>
		<pubDate>Mon, 21 Jul 2008 00:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/#comment-1341</guid>
		<description>[...] http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/" rel="nofollow">http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CleverWorkarounds &#187; A neat trick with the publishing feature</title>
		<link>http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/comment-page-1/#comment-1328</link>
		<dc:creator>CleverWorkarounds &#187; A neat trick with the publishing feature</dc:creator>
		<pubDate>Sat, 19 Jul 2008 14:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/#comment-1328</guid>
		<description>[...] I mentioned in my last post, I always security trim SharePoint. A very common issue with a security trimmed SharePoint is the [...]</description>
		<content:encoded><![CDATA[<p>[...] I mentioned in my last post, I always security trim SharePoint. A very common issue with a security trimmed SharePoint is the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Parkes</title>
		<link>http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/comment-page-1/#comment-1326</link>
		<dc:creator>Andy Parkes</dc:creator>
		<pubDate>Sat, 19 Jul 2008 10:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/2008/07/19/good-advice-hidden-in-the-infrastructure-update/#comment-1326</guid>
		<description>Interesting...i suspect this could be the reason why my recent upgrade failed (http://parkesy.wordpress.com/2008/07/17/lucky-lucky-boy/)

In an attempt to get my incoming emails to fire automatic workflows i&#039;d made changes to the service accounts

Once i&#039;d removed SharePoint and started again it was back to it&#039;s default state so the upgrade went fine

Definately something to bear in mind in the future

Thanks!</description>
		<content:encoded><![CDATA[<p>Interesting&#8230;i suspect this could be the reason why my recent upgrade failed (<a href="http://parkesy.wordpress.com/2008/07/17/lucky-lucky-boy/" rel="nofollow">http://parkesy.wordpress.com/2008/07/17/lucky-lucky-boy/</a>)</p>
<p>In an attempt to get my incoming emails to fire automatic workflows i&#8217;d made changes to the service accounts</p>
<p>Once i&#8217;d removed SharePoint and started again it was back to it&#8217;s default state so the upgrade went fine</p>
<p>Definately something to bear in mind in the future</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
