Here’s what I posted to the bottom of this blog:

Service Pack 1 for SharePoint 2010 Products is Now Available for Download:
http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=984

“Can you post clearly in technet how to do a patch deployment on a single standalone server?  It’s not clear to me that psconfig needs to be manually done after patching.

Secondly for these standalone deployments, can you change the wording of the KB that shows up in Microsoft Update and WSUS that a psconfig command is needed to properly deploy this update?”

I think the documentation for how SharePoint needs to manually run psconfig is not well documented.  Certainly not for standalone SharePoint servers.  And should be exposed in MU or WSUS in the KB details that it needs to be run. 

Bingle juice for others:

If you hit here because of any of these error messages and you just installed SharePoint sp1, make sure you run a manual psconfig command.  See this blog for more details:  http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx

A Volume Shadow Copy Service operation failed.Unknown error (0x800423f0)

Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key

Information Store (2264) Shadow copy instance 2 aborted

The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition

spsearch4 vss writer inconsistent shadow copy

 

3 Responses to I’m still of the opinion that psconfig is still not well documented

  1. Dean says:

    I have soooo many questions like that. The documentation always leaves you hanging. Documentation HAS to be accurate and complete. Otherwise you go in circles.

    Their excuse for not filling in the details is always the same. We don’t have time now. I don’t believe for a second that that is the real reason. I think it’s corporate policy.

    What is Bingle juice ?

  2. Dean says:

    That KB article is a good example of incomplete documentation. Usually the KB article will have a section that tells you WHY the problem happens and under what circumstances. That KB does not.

  3. Dean says:

    “5+ years to write 1 paragraph about what the program actually does seems pretty poor form!”

    LOL !

    http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/5d5ea2be-9a13-441f-98ad-2075b531e214