PSconfig – I’m lazy

So to do some testing on a SBS 2011 I was building a brand new one.. and 47 gazillion updates later and about 40 psconfigs (okay more like three so far) at about the second time doing a psconfig command I realized there has to be a better way.


So whether you are a command line person, a bat file person a powershell person….what I did for me since I’m a .bat command line gal, is I stuck a little .bat file in the Windows\system32 folder


The name of the file is psconfigbat.bat


The contents of psconfigbat.bat is as follows:


CD\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures


That’s it.  Save it as a .bat file and dump it into the c:\windows\system32 folder just because that’s where you end up when you runas admin at the command com icon.


When I run a Sharepoint update, I then go to the command com icon on the start menu, right mouse click run as admin and then type in psconfigbat and hit enter


The command then does it’s thing.


 

3 Thoughts on “PSconfig – I’m lazy

  1. Chris Lilley on October 9, 2013 at 8:11 am said:

    Hi Susan

    Thank you for this handy tip.

    One point I’m always a little unsure of by the PSConfig requirement when patching SharePoint – Is it best run before the server is rebooted, or afterwards?

    Thanks

    Chris

  2. bradley on October 9, 2013 at 9:05 am said:

    I do SharePoint updates all by themselves. I patch the server for everything else. Reboot. Then come back and do SharePoint and it typically does not need a reboot at that time. Otherwise I do it after I’ve rebooted the server.

  3. Chris Lilley on October 9, 2013 at 4:01 pm said:

    Thank you

Post Navigation