Every time someone mentions psconfig I shudder. Do you? It's a fact of life for SharePoint admins. When you're patching your SharePoint environments you can't breathe a sigh of relief until you tackle the psconfig beast.
There's a lot out there about psconfig, and if you're like me and don't spend a heckuva lot of time in command prompts, it can be a little intimidating. Sure, you can run psconfig via Central Admin - but where's the fun in that? I like to be in control of my environment and IMO psconfig in Central Admin is the antithesis of control.
To avoid slapping in unknown commands returned from a search engine into our SharePoint environment, here's Rightpoint's contribution to the world and what I'm calling our "psconfig command line elixir" because it should get you out of most psconfig jams. I can't say I wrote this, as the talented Zach Quinn at Rightpoint did that, but it got me out of a SP1 jam and hopefully it'll help you out too.
Open up SharePoint Management Shell as an administrator and let this code fly:
So what does this do and how is it different than other psconfig commands out there? This runs the upgrade command with both a force and wait flag. It'll then copies the application data to existing web app virtual directories, then registers what's located on the server's file system with the server farm. The last flag is to ignore the patch verification on the server.
You may have to deal with other fun-ness like restarting the timer service, but that's the nature of the psconfig beast.
For more details, check out PSConfig's tech net article.