<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;A08MQXo8cSp7ImA9WhRRFE4.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971</id><updated>2011-11-27T16:24:40.479-08:00</updated><category term="serviceapplicationpool" /><category term="&quot;page not found&quot; SharePoint" /><category term="Hold feature subsites powershell every site" /><category term="set-executionpolicy get-executionpolicy WMI" /><category term="&quot;default.aspx&quot;" /><category term="PDF ifilter sharepoint 2010 registry GUID foxit" /><category term="powershell" /><category term="retire Exchange 2003 2007 &quot;message tracking&quot;" /><category term="duplicate results people search peoplesearc sharepoint" /><category term="SharePoint" /><category term="Windows Server 2008" /><category term="server manager refresh WSUS Windows updates" /><category term="Exchange 2010" /><category term="Exchange 2007" /><category term="backup" /><title>MOSS-Exchange</title><subtitle type="html">Welcome to a blog dedicated to the support of Microsoft technologies such as Exchange, SharePoint and Active Directory.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://moss-exchange.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>40</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/Moss-exchange" /><feedburner:info uri="moss-exchange" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;C0QBRXg5fSp7ImA9WhRSE0Q.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-5432043387722430652</id><published>2011-11-15T13:09:00.000-08:00</published><updated>2011-11-15T13:09:14.625-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-15T13:09:14.625-08:00</app:edited><title>enumerate all sites and subsites in a web application with PowerShell</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/5432043387722430652/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=5432043387722430652" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/5432043387722430652?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/5432043387722430652?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/DlzJIGEMsJM/enumerate-all-sites-and-subsites-in-web.html" title="enumerate all sites and subsites in a web application with PowerShell" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">I have been struggling to make a change to each site in my SharePoint 2010 farm.  The first step was to list all sites and subsites.

get-spsite | get-spweb -Limit ALL

I can get that into an array thusly:  $allsites= (get-spsite|get-spweb -Limit ALL)

Once I have the site list "in memory" as the $allsites variable, I can then run a command on each subsite using a foreach loop.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/P5H5Y19y3MJDeK71fUN4a63apj8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/P5H5Y19y3MJDeK71fUN4a63apj8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/P5H5Y19y3MJDeK71fUN4a63apj8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/P5H5Y19y3MJDeK71fUN4a63apj8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/DlzJIGEMsJM" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/11/enumerate-all-sites-and-subsites-in-web.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UMQno9cCp7ImA9WhdaEU4.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-8828389560887485364</id><published>2011-10-20T11:28:00.000-07:00</published><updated>2011-10-20T11:28:03.468-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-20T11:28:03.468-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="duplicate results people search peoplesearc sharepoint" /><title>Multiple results in People Search in SharePoint 2010</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/8828389560887485364/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=8828389560887485364" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/8828389560887485364?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/8828389560887485364?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/yctYqLyl8JQ/multiple-results-in-people-search-in.html" title="Multiple results in People Search in SharePoint 2010" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">I had an issue in my lab server with User Profiles in SharePoint 2010 (big surprise!).  In my troubleshooting, I had added multiple sps3://servername start address entries in my Content Source.  I was troubleshooting and added the extra entries with the port and alternate access mappings variations.  I solved my other issues with the User Profile service application and with search.  I forgot to 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/78AFdOasz01Rq0ckKbAeQoeNDhs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/78AFdOasz01Rq0ckKbAeQoeNDhs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/78AFdOasz01Rq0ckKbAeQoeNDhs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/78AFdOasz01Rq0ckKbAeQoeNDhs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/yctYqLyl8JQ" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/10/multiple-results-in-people-search-in.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8ER3g7fCp7ImA9WhdbFUk.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-1203135679177245857</id><published>2011-10-13T16:00:00.000-07:00</published><updated>2011-10-13T16:00:06.604-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-13T16:00:06.604-07:00</app:edited><title>Co-authoring an Office 2010 document</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/1203135679177245857/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=1203135679177245857" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1203135679177245857?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1203135679177245857?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/ihoTR9r9Ugs/co-authoring-office-2010-document.html" title="Co-authoring an Office 2010 document" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">In a recent demonstration to new Office and SharePoint 2010 clients, I successfully demonstrated how two users can edit the same document at the same time.  Here's how you do it with Word 2010:
Have a SharePoint 2010 document library available.
Create a Word 2010 document
Select the file menu then Save and Send to publish to the SharePoint document Library
Browse to the document library in 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/SNGS51bJyuSbVnNTwCKld6bLX5g/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SNGS51bJyuSbVnNTwCKld6bLX5g/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/SNGS51bJyuSbVnNTwCKld6bLX5g/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SNGS51bJyuSbVnNTwCKld6bLX5g/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/ihoTR9r9Ugs" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/10/co-authoring-office-2010-document.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkUAQns4fCp7ImA9WhdVFUs.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-68693356138526601</id><published>2011-09-20T16:07:00.000-07:00</published><updated>2011-09-20T16:10:43.534-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-20T16:10:43.534-07:00</app:edited><title>Cancel all workflows in SharePoint 2010</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/68693356138526601/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=68693356138526601" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/68693356138526601?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/68693356138526601?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/dSKcfyEh1B8/cancel-all-workflows-in-sharepoint-2010.html" title="Cancel all workflows in SharePoint 2010" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">If you've ever had a glitch where custom workflows are all in an error state or other circumstances where you just need to wipe the slate clean of the workflows genreated in SharePoint, use this PowerShell command from the SharePoint 2010 Management Shell:foreach ($wf in $web.Workflows){[Microsoft.SharePoint.Workflow.SPWorkflowManager]::CancelWorkflow($wf)}
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/x4BXugs1_-U9D1jevbv0AV4nH3I/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/x4BXugs1_-U9D1jevbv0AV4nH3I/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/x4BXugs1_-U9D1jevbv0AV4nH3I/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/x4BXugs1_-U9D1jevbv0AV4nH3I/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/dSKcfyEh1B8" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/09/cancel-all-workflows-in-sharepoint-2010.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUMBQHgyfip7ImA9WhdREkw.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-7294691806515105272</id><published>2011-08-01T09:29:00.000-07:00</published><updated>2011-08-01T09:50:51.696-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-01T09:50:51.696-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="set-executionpolicy get-executionpolicy WMI" /><title>AuthorizationManager check failed when launching scripts in PowerShell</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/7294691806515105272/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=7294691806515105272" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/7294691806515105272?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/7294691806515105272?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/EUkJHji2vi0/authorizationmanager-check-failed-when.html" title="AuthorizationManager check failed when launching scripts in PowerShell" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">Recently, I received this error when trying to run a script on my Server 2008 R2 server.AuthorizationManager check failed.At line:1 char:3+ &amp;amp; &amp;lt;&amp;lt;&amp;lt;&amp;lt; ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 '+ CategoryInfo : NotSpecified: (:) [], PSSecurityException+ FullyQualifiedErrorId : RuntimeExceptionI was also unable to run the 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/WAUgRqlk_hss7FKaRPb2VoOIqBc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/WAUgRqlk_hss7FKaRPb2VoOIqBc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/WAUgRqlk_hss7FKaRPb2VoOIqBc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/WAUgRqlk_hss7FKaRPb2VoOIqBc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/EUkJHji2vi0" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/08/authorizationmanager-check-failed-when.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0MESHwyeyp7ImA9WhdSGUs.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-1354395385812532245</id><published>2011-07-29T10:31:00.000-07:00</published><updated>2011-07-29T10:43:29.293-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-29T10:43:29.293-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="PDF ifilter sharepoint 2010 registry GUID foxit" /><title>Installing Foxit 2.x PDF IFilter in SharePoint 2010</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/1354395385812532245/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=1354395385812532245" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1354395385812532245?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1354395385812532245?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/YVWUK8Sqjpk/installing-foxit-2x-pdf-ifilter-in.html" title="Installing Foxit 2.x PDF IFilter in SharePoint 2010" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">Installing Foxit 2.x PDF IFilter in SharePoint 2010 has been a bit of an adventure for me to get working. I found the instructions in bits and chunks on several different sites so I compiled the instructions here from start to finish:1. Download the IFilter installer and icon from Foxit.2. Open a command prompt “As Administrator”3. Run IISRESET /STOP (leave the command prompt open)4. Launch the 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/JLVURrTdvkR8yWDooPkXjU1MwaU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/JLVURrTdvkR8yWDooPkXjU1MwaU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/JLVURrTdvkR8yWDooPkXjU1MwaU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/JLVURrTdvkR8yWDooPkXjU1MwaU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/YVWUK8Sqjpk" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/07/installing-foxit-2x-pdf-ifilter-in.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUFQn48fCp7ImA9WhdSFk0.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-7745460766832117193</id><published>2011-07-25T07:08:00.000-07:00</published><updated>2011-07-25T07:13:33.074-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-25T07:13:33.074-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="server manager refresh WSUS Windows updates" /><title>Console cannot refresh until computer is restarted</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/7745460766832117193/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=7745460766832117193" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/7745460766832117193?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/7745460766832117193?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/qp0d6BvvqCY/console-cannot-refresh-until-computer.html" title="Console cannot refresh until computer is restarted" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">In Windows Server 2008 R2, I periodically get the error "Console cannot refresh until computer is restarted" in Server Manager.  Even after a reboot, the error condition remains.  I may also see "Windows Update Client failed to detect with error 0x80070bc9" the ReportingEvents.log file and Windows updates will fail.There are several ways to fix this, but the simplest and quickest is to reboot the
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/k7G3Qa8WXNJaiepcslX4Nkz1kdw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/k7G3Qa8WXNJaiepcslX4Nkz1kdw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/k7G3Qa8WXNJaiepcslX4Nkz1kdw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/k7G3Qa8WXNJaiepcslX4Nkz1kdw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/qp0d6BvvqCY" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/07/console-cannot-refresh-until-computer.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEcGRH8zeyp7ImA9WhdSEks.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-2979815362323225</id><published>2011-07-21T08:17:00.000-07:00</published><updated>2011-07-21T08:27:05.183-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-21T08:27:05.183-07:00</app:edited><title>enable or disable a feature for all subsites</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/2979815362323225/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=2979815362323225" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/2979815362323225?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/2979815362323225?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/9EO7-DwTQYQ/enable-or-disable-feature-for-all.html" title="enable or disable a feature for all subsites" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">I have run into situations where I had to rapidly change features or other aspects of subsites across multiple site collections.  How can you do that with PowerShell?  It turns out to be quite easy.  You don't even need a script.  You can run a nested command.  Here is the example on how to enable a feature on every site and subsite in the farm:get-spsite|get-spweb | foreach-object {
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/OlpypV2X7QCehMmEPXygOVFSaQY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/OlpypV2X7QCehMmEPXygOVFSaQY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/OlpypV2X7QCehMmEPXygOVFSaQY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/OlpypV2X7QCehMmEPXygOVFSaQY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/9EO7-DwTQYQ" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/07/enable-or-disable-feature-for-all.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0MCQno7cCp7ImA9WhdSEks.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-8949496758506577962</id><published>2011-07-21T08:05:00.000-07:00</published><updated>2011-07-21T08:17:43.408-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-21T08:17:43.408-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Hold feature subsites powershell every site" /><title>Hold and eDiscovery feature in SharePoint 2010</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/8949496758506577962/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=8949496758506577962" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/8949496758506577962?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/8949496758506577962?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/rVr4G5gXbo4/hold-and-ediscovery-feature-in.html" title="Hold and eDiscovery feature in SharePoint 2010" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">I have been tasked to deploy the Hold and eDiscovery feature for an entire farm so that the legal team in the enterprise can create litigation holds in SP 2010.  This feature is managed at the site collection level, but it does not automatically turn on the features on each subsite.  I had to come up with a quick solution to enable this for all sites:get-spsite | get-spweb | foreach-object {
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/TJCfPPOBW00U0xzf-i_c80gwELs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TJCfPPOBW00U0xzf-i_c80gwELs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/TJCfPPOBW00U0xzf-i_c80gwELs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TJCfPPOBW00U0xzf-i_c80gwELs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/rVr4G5gXbo4" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/07/hold-and-ediscovery-feature-in.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU4AQXgycSp7ImA9WhZQFEQ.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-1125257177073073981</id><published>2011-04-22T10:28:00.000-07:00</published><updated>2011-04-22T10:39:00.699-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-22T10:39:00.699-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="powershell" /><category scheme="http://www.blogger.com/atom/ns#" term="SharePoint" /><category scheme="http://www.blogger.com/atom/ns#" term="serviceapplicationpool" /><title>cmdlet change in SharePoint 2010 New-SPIISWebServiceApplicationPool</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/1125257177073073981/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=1125257177073073981" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1125257177073073981?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1125257177073073981?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/-SOiIssG4vg/cmdlet-change-in-sharepoint-2010-new.html" title="cmdlet change in SharePoint 2010 New-SPIISWebServiceApplicationPool" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">I hope I can save you the frustration I had in debugging my script:New-SPIISWebServiceApplicationPool -Name ManagedMetadataServiceAppPool -Account domain\userThe term 'Get-SPIISWebServiceApplicationPool' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/qyTlnKkhqveflb0kp7A_p9Tw4z0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qyTlnKkhqveflb0kp7A_p9Tw4z0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/qyTlnKkhqveflb0kp7A_p9Tw4z0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qyTlnKkhqveflb0kp7A_p9Tw4z0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/-SOiIssG4vg" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/04/cmdlet-change-in-sharepoint-2010-new.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0UEQ3s_cCp7ImA9WhZRFUk.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-3044106994925891242</id><published>2011-04-11T12:01:00.000-07:00</published><updated>2011-04-11T12:13:22.548-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-11T12:13:22.548-07:00</app:edited><title>New-SPSite : User cannot be found</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/3044106994925891242/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=3044106994925891242" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/3044106994925891242?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/3044106994925891242?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/DZ-8tomN89Q/new-spsite-user-cannot-be-found.html" title="New-SPSite : User cannot be found" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">I recently had a bit of a head-scratcher with a "User cannot be found" error when using PowerShell to create a site collection in SharePoint Server 2010.  My command was quite simple:New-SPSite -url http://servername/sites/site -owneralias "domain\username" -template "STS#0" -Name "Site Title Here"I received an error "User cannot be found"If I removed the "domain\" the command worked every time:
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/e8c7E8QjvkuSqB5xWK_JkI7WUfw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/e8c7E8QjvkuSqB5xWK_JkI7WUfw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/e8c7E8QjvkuSqB5xWK_JkI7WUfw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/e8c7E8QjvkuSqB5xWK_JkI7WUfw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/DZ-8tomN89Q" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/04/new-spsite-user-cannot-be-found.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0QMRXg4fip7ImA9WhZSFUo.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-7677084754822074364</id><published>2011-03-31T05:27:00.000-07:00</published><updated>2011-03-31T05:43:04.636-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-31T05:43:04.636-07:00</app:edited><title>Update conflict in MOSS 2007</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/7677084754822074364/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=7677084754822074364" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/7677084754822074364?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/7677084754822074364?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/Bi4JRttk-I8/update-conflict-in-moss-2007.html" title="Update conflict in MOSS 2007" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">An update conflict has occurred, and you must re-try this action. The object SPContentDatabase Name=WSS_Content_name Parent=SPDatabaseServiceInstance is being updated by domain\user, in the w3wp process, on machine server. View the tracing log for more information about the conflict. I was receiving this error in Central Admin when I was trying to increase the maximum number of sites in Manage 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Vglv1V-aFVKi3DrEJaFdIZ118Wc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Vglv1V-aFVKi3DrEJaFdIZ118Wc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Vglv1V-aFVKi3DrEJaFdIZ118Wc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Vglv1V-aFVKi3DrEJaFdIZ118Wc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/Bi4JRttk-I8" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2011/03/update-conflict-in-moss-2007.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D04NQ34_fyp7ImA9Wx5bGUQ.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-3761053763093667636</id><published>2010-11-05T12:48:00.000-07:00</published><updated>2010-11-05T15:26:32.047-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-11-05T15:26:32.047-07:00</app:edited><title>Unknown Error when trying to acitvate publishing</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/3761053763093667636/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=3761053763093667636" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/3761053763093667636?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/3761053763093667636?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/1-6wojDgxfE/unknown-error-when-trying-to-acitvate.html" title="Unknown Error when trying to acitvate publishing" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">Have you ever received an "Unknown Error" when activating a site collection feature: Office SharePoint Server Publishing InfrastructureUse STSADM to deply the feature:stsadm -o activatefeature -name PublishingResources -url http://websiteIf it fails, run the same command with the -force switch.The run:stsadm -o activatefeature -name Publishing -url http://websiteAgain, if it fails, use the -force
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/4AcV6SOXKJ9sI8S5AMdXKMMUwrk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/4AcV6SOXKJ9sI8S5AMdXKMMUwrk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/4AcV6SOXKJ9sI8S5AMdXKMMUwrk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/4AcV6SOXKJ9sI8S5AMdXKMMUwrk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/1-6wojDgxfE" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2010/11/unknown-error-when-trying-to-acitvate.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YHRXo9fyp7ImA9Wx5WFk8.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-9220166779271234471</id><published>2010-09-27T14:43:00.000-07:00</published><updated>2010-09-27T15:05:34.467-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-09-27T15:05:34.467-07:00</app:edited><title>the database name located at the specified database server contains user-defined data</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/9220166779271234471/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=9220166779271234471" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/9220166779271234471?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/9220166779271234471?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/c1xrl-01VxY/database-name-located-at-specified.html" title="the database name located at the specified database server contains user-defined data" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">During a recent SharePoint 2007 install I received the error: "the database name located at the specified database server contains user-defined data." Reusing a shared SQL server in a development environment, I received this error from the Config Wizard (SharePoint Products and Technologies Configuration Wizard) in MOSS 2007. I specified a unique name for the Config database so what's the problem
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/mggnDrE1EQQFEQnqJprAkbQypHc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mggnDrE1EQQFEQnqJprAkbQypHc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/mggnDrE1EQQFEQnqJprAkbQypHc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mggnDrE1EQQFEQnqJprAkbQypHc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/c1xrl-01VxY" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2010/09/database-name-located-at-specified.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0ANR346fSp7ImA9Wx5SEE4.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-8955537951152554071</id><published>2010-08-05T12:07:00.001-07:00</published><updated>2010-08-05T12:16:36.015-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-05T12:16:36.015-07:00</app:edited><title>Windows Update fails on Server 2008 R2</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/8955537951152554071/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=8955537951152554071" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/8955537951152554071?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/8955537951152554071?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/dD_rMQ9RwV8/windows-update-fails-on-server-2008-r2.html" title="Windows Update fails on Server 2008 R2" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>1</thr:total><content type="html">I have seen a common issue with Windows 2008 R2 and WSUS where the Windows Update client stops working with the error: Windows Update Client failed to detect with error 0x80070bc9 in the log. During these times, I notice that Server Manager complains that it cannot be refreshed until the server is restarted.  I cannot use Windows Update, add roles, or view the roles in Server Manager.  The error 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/4z2XwYLNg6B4qyf72R-5u43cpcI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/4z2XwYLNg6B4qyf72R-5u43cpcI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/4z2XwYLNg6B4qyf72R-5u43cpcI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/4z2XwYLNg6B4qyf72R-5u43cpcI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/dD_rMQ9RwV8" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2010/08/windows-update-fails-on-server-2008-r2.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0IEQ3o4eyp7ImA9Wx5SEE4.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-6172433691089000929</id><published>2010-08-05T10:53:00.000-07:00</published><updated>2010-08-05T11:05:02.433-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-05T11:05:02.433-07:00</app:edited><title>ASP.NET exception Event ID 1314</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/6172433691089000929/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=6172433691089000929" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/6172433691089000929?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/6172433691089000929?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/E7x1xGM70w0/aspnet-exception-event-id-1314.html" title="ASP.NET exception Event ID 1314" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_b4CFRJywS3w/TFr8fCcdBEI/AAAAAAAAADQ/vq6qoAJ6k7k/s72-c/read-permissions.png" height="72" width="72" /><thr:total>0</thr:total><content type="html">an unhandled exception has occurred event code 4011On one of my web front-end servers, I was receivning this error. The page was intermittently having trouble loading from one node of the cluster. I was seeing generic Windows SharePoint Error pages, but mostly 403 errors.Adding the servername\Users Read (Read &amp;amp; Execute, List Folder Contents, Read) permissions to the \bin folder in the IIS virtual
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/qaKuW0nZ-_s74c-IkN6c819-x1E/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qaKuW0nZ-_s74c-IkN6c819-x1E/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/qaKuW0nZ-_s74c-IkN6c819-x1E/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qaKuW0nZ-_s74c-IkN6c819-x1E/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/E7x1xGM70w0" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2010/08/aspnet-exception-event-id-1314.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkQFQXY5cCp7ImA9WxFbF00.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-1799950006294124354</id><published>2010-07-09T12:33:00.000-07:00</published><updated>2010-07-09T12:38:30.828-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-09T12:38:30.828-07:00</app:edited><title>Error when applying CU</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/1799950006294124354/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=1799950006294124354" title="10 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1799950006294124354?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1799950006294124354?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/IXnY-jH4Th8/error-when-applying-cu.html" title="Error when applying CU" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>10</thr:total><content type="html">I was in a hurry updating a multi-server farm with the June 2010 CU for MOSS 2007.  I launched the config wizard before it was finished on another front-end server.  I received this error:unable to upgrade sharepoint products and technologies because an upgrade is already in progressThinking I had already finished the first front-end, troubleshooting generated this message:An update conflict has 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/SsFTPdu1sEfJyYxC1ewrAkTB5ts/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SsFTPdu1sEfJyYxC1ewrAkTB5ts/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/SsFTPdu1sEfJyYxC1ewrAkTB5ts/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SsFTPdu1sEfJyYxC1ewrAkTB5ts/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/IXnY-jH4Th8" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2010/07/error-when-applying-cu.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUcBSHs9cSp7ImA9WxNbEEs.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-7598921340044086865</id><published>2009-11-12T15:02:00.000-08:00</published><updated>2009-11-12T15:04:19.569-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-12T15:04:19.569-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Exchange 2010" /><title>Exchange 2010 Product Keys and Licensing</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/7598921340044086865/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=7598921340044086865" title="20 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/7598921340044086865?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/7598921340044086865?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/terg5sFVJtU/exchange-2010-product-keys-and.html" title="Exchange 2010 Product Keys and Licensing" /><author><name>jaxdagger</name><uri>http://www.blogger.com/profile/09225261420649199668</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_8370OL289Gw/Su9lFCU6DPI/AAAAAAAAAAM/CnF1NN9k578/S220/groo1.JPG" /></author><thr:total>20</thr:total><content type="html">As part of the post installation tasks, the first two immediate steps include verifying the installation and then registering a product key on the server. The former step requires a little experience on installing Exchange servers.  The primary step recommended by Microsoft is to view the Exchange Setup Logs which will be in a folder of similar name on the installation drive.  These logs should 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/xQAxtaqzMePMWR1K4j2CINVpwIA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xQAxtaqzMePMWR1K4j2CINVpwIA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/xQAxtaqzMePMWR1K4j2CINVpwIA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xQAxtaqzMePMWR1K4j2CINVpwIA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/terg5sFVJtU" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2009/11/exchange-2010-product-keys-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0INQXwzfip7ImA9WxNUGUU.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-1940001078435719139</id><published>2009-11-10T16:35:00.000-08:00</published><updated>2009-11-11T17:33:10.286-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-11T17:33:10.286-08:00</app:edited><title>Exchange 2010 Installation</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/1940001078435719139/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=1940001078435719139" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1940001078435719139?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/1940001078435719139?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/NrtdfxJZ3Ik/installing-exchange-2010.html" title="Exchange 2010 Installation" /><author><name>jaxdagger</name><uri>http://www.blogger.com/profile/09225261420649199668</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_8370OL289Gw/Su9lFCU6DPI/AAAAAAAAAAM/CnF1NN9k578/S220/groo1.JPG" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_8370OL289Gw/SvoHRlrHZtI/AAAAAAAAAAw/hvkiDpRuCYk/s72-c/CAS+External+Domain.JPG" height="72" width="72" /><thr:total>1</thr:total><content type="html">On the day of the RTM release of Exchange 2010, I successfully installed the RC version on a virtual machine. My delay was not due its difficulty. I ran into those virtual machine foibles such as running out of disk space and accidental shut downs by sons who want to get on www.lego.com.It would also have speeded up if I found a comprehensive list of the software prereqs. It may be out there but 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/q-j79Aigg-Qgb-Z5YHshCwhbJBk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/q-j79Aigg-Qgb-Z5YHshCwhbJBk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/q-j79Aigg-Qgb-Z5YHshCwhbJBk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/q-j79Aigg-Qgb-Z5YHshCwhbJBk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/NrtdfxJZ3Ik" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2009/11/installing-exchange-2010.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4ASHc4eSp7ImA9WxNUEkg.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-4802789173962213334</id><published>2009-11-03T04:52:00.000-08:00</published><updated>2009-11-03T04:55:49.931-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-03T04:55:49.931-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Exchange 2010" /><title>Exchange 2010 Preparing the Environment</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/4802789173962213334/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=4802789173962213334" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/4802789173962213334?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/4802789173962213334?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/bmzUXOk7rEM/exchange-2010-preparing-environment.html" title="Exchange 2010 Preparing the Environment" /><author><name>jaxdagger</name><uri>http://www.blogger.com/profile/09225261420649199668</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_8370OL289Gw/Su9lFCU6DPI/AAAAAAAAAAM/CnF1NN9k578/S220/groo1.JPG" /></author><thr:total>1</thr:total><content type="html">     In my last blog, I laid out the basic steps of performing a migration to Exchange 2010.  Since the most probable customers choosing to migrate will have Exchange Server 2003, the direction of the migration will be based on the following environment:-  A single domain Windows Server 2003 Active Directory environment with the highest domain and forest functional levels. -  A single Exchange 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/NHHZaiksxKrljaSXe-ZGcG1RgyQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/NHHZaiksxKrljaSXe-ZGcG1RgyQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/NHHZaiksxKrljaSXe-ZGcG1RgyQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/NHHZaiksxKrljaSXe-ZGcG1RgyQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/bmzUXOk7rEM" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2009/11/exchange-2010-preparing-environment.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUQBSH06fCp7ImA9WxNUEk0.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-9005280173177215148</id><published>2009-11-02T15:03:00.000-08:00</published><updated>2009-11-02T15:09:19.314-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-02T15:09:19.314-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Exchange 2010" /><category scheme="http://www.blogger.com/atom/ns#" term="Exchange 2007" /><title>Exchange 2010 - Planning and Coexistence</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/9005280173177215148/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=9005280173177215148" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/9005280173177215148?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/9005280173177215148?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/Pn_sDRWFIik/exchange-2010-planning-and-coexistence.html" title="Exchange 2010 - Planning and Coexistence" /><author><name>jaxdagger</name><uri>http://www.blogger.com/profile/09225261420649199668</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://4.bp.blogspot.com/_8370OL289Gw/Su9lFCU6DPI/AAAAAAAAAAM/CnF1NN9k578/S220/groo1.JPG" /></author><thr:total>4</thr:total><content type="html">Given my current employment, I’ve got the time to devote to studying Exchange 2010. To hone my skills, I plan posting my notes on this beloved blog to encourage the masses to migrate to Exchange 2010 and hire me to do it.Currently, Exchange 2010 is in the Release Candidate phase of development. This means it is one step before the Release (Ready?) to Market (RTM) or gold standard. Thus it is very
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/tLr46k0uL5tPO4u1HfadWj_3fKs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tLr46k0uL5tPO4u1HfadWj_3fKs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/tLr46k0uL5tPO4u1HfadWj_3fKs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tLr46k0uL5tPO4u1HfadWj_3fKs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/Pn_sDRWFIik" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2009/11/exchange-2010-planning-and-coexistence.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkYCQ3Y4eip7ImA9WxNREEQ.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-5288270233691394537</id><published>2009-09-04T11:49:00.001-07:00</published><updated>2009-09-04T11:49:22.832-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-04T11:49:22.832-07:00</app:edited><title>Symantec Enterprise Vault</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/5288270233691394537/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=5288270233691394537" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/5288270233691394537?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/5288270233691394537?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/mtdTB8XGyAc/symantec-enterprise-vault.html" title="Symantec Enterprise Vault" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">A lesson from the field for Enterprise Vault.  8390 Errors.  These usually mean that you need to put the DisableLoopbackCheck =1 DWORD in the HKLM\SYSTEM\CurrentControlSet\Control\Lsa … But not always.  Look for name resolution issues in your environment.  Cure these two things and you will most likely solve the problems.Need to change your Vault service account password?  Use the Site Settings 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/91ep1DkQapwnyH752AB6ytwp4Ws/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/91ep1DkQapwnyH752AB6ytwp4Ws/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/91ep1DkQapwnyH752AB6ytwp4Ws/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/91ep1DkQapwnyH752AB6ytwp4Ws/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/mtdTB8XGyAc" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2009/09/symantec-enterprise-vault.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0IFR3s-fSp7ImA9WxJUEkg.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-3462127622558880027</id><published>2009-07-10T11:34:00.000-07:00</published><updated>2009-07-10T11:45:16.555-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-10T11:45:16.555-07:00</app:edited><title>SharePoint 2007 WSS 3.0 Service Pack 2</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/3462127622558880027/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=3462127622558880027" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/3462127622558880027?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/3462127622558880027?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/aPG7VYhIqeM/sharepoint-2007-wss-30-service-pack-2.html" title="SharePoint 2007 WSS 3.0 Service Pack 2" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">Several of my clients have installed SP2 for MOSS 2007.  Aside from a glitch which puts the farm in trial mode--which has been fixed before the 180 days expiration--I have heard nothing good or bad about this release. I did some timings (based solely on logs) on the length of incremental crawls, content deployment, backups, etc.  I don't really notice a difference, but I didn't set this up 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/mn2RTqv-e4Ee1cciKUdsk3Ir6X4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mn2RTqv-e4Ee1cciKUdsk3Ir6X4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/mn2RTqv-e4Ee1cciKUdsk3Ir6X4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mn2RTqv-e4Ee1cciKUdsk3Ir6X4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/aPG7VYhIqeM" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2009/07/sharepoint-2007-wss-30-service-pack-2.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0YFR3k7eCp7ImA9WxJUEEU.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-5898124456940295043</id><published>2009-07-08T10:20:00.000-07:00</published><updated>2009-07-08T12:25:16.700-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-08T12:25:16.700-07:00</app:edited><title>Notes to SharePoint migration - Phase Two Design and testing</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/5898124456940295043/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=5898124456940295043" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/5898124456940295043?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/5898124456940295043?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/tFot850iMeY/notes-to-sharepoint-migration-phase-two.html" title="Notes to SharePoint migration - Phase Two Design and testing" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>2</thr:total><content type="html">Once you've completed the Discovery phase of your Notes to SharePoint migrations (see the steps here:http://moss-exchange.blogspot.com/2009/05/notes-to-sharepoint-migration-phase-one.html ) you are ready for the next steps. This phase is where you design the migration.  First, you need a target environment.  If you already have a SharePoint environment setup, it's likely organized by department 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/_Iy7tfL71HbNB7fL6byo09p8SRQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_Iy7tfL71HbNB7fL6byo09p8SRQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/_Iy7tfL71HbNB7fL6byo09p8SRQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_Iy7tfL71HbNB7fL6byo09p8SRQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/tFot850iMeY" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2009/07/notes-to-sharepoint-migration-phase-two.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4NRXs6fip7ImA9WxJQGE0.&quot;"><id>tag:blogger.com,1999:blog-1889709198604311971.post-4005585716732605312</id><published>2009-05-31T12:48:00.000-07:00</published><updated>2009-05-31T13:49:54.516-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-31T13:49:54.516-07:00</app:edited><title>Notes to SharePoint migration - Phase One Discovery</title><link rel="replies" type="application/atom+xml" href="http://moss-exchange.blogspot.com/feeds/4005585716732605312/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=1889709198604311971&amp;postID=4005585716732605312" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/4005585716732605312?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1889709198604311971/posts/default/4005585716732605312?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Moss-exchange/~3/OhXOmuNKVn0/notes-to-sharepoint-migration-phase-one.html" title="Notes to SharePoint migration - Phase One Discovery" /><author><name>Greg Zook</name><uri>http://www.blogger.com/profile/15385819073299429584</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="24" src="http://bp0.blogger.com/_b4CFRJywS3w/R2ntlFvFA2I/AAAAAAAAAAk/_29S8CfwaxU/S220/PIC-0044.jpg" /></author><thr:total>0</thr:total><content type="html">More and more of the migration projects I am involved with are Lotus Notes to SharePoint.These projects often start out with thousands of Notes, Domino.Doc, or Quickplace applications (or databases as they have been known in the Notes vernacular).  It can be veryoverwhelming. Remember the old question: "How do you eat an elephant?"  Answer:  "One bite at a time."  Well, aside from being disgusted
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Zh0hjUmYpzGkfLPy_2xYUWWfxyI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Zh0hjUmYpzGkfLPy_2xYUWWfxyI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Zh0hjUmYpzGkfLPy_2xYUWWfxyI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Zh0hjUmYpzGkfLPy_2xYUWWfxyI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Moss-exchange/~4/OhXOmuNKVn0" height="1" width="1"/&gt;</content><feedburner:origLink>http://moss-exchange.blogspot.com/2009/05/notes-to-sharepoint-migration-phase-one.html</feedburner:origLink></entry></feed>

