Apr 13, 2017
Some of us are walking in situations wondering who is providing for me, but it's time to check your bag, you've been carrying Holy Spirit!
Planetshakers
seen from United States
seen from United States
seen from China
seen from South Africa
seen from United States
seen from United States
seen from Singapore
seen from Malaysia
seen from United States
seen from United States
seen from United States
seen from United States
seen from China
seen from Canada
seen from United States
seen from China
seen from Australia
seen from Canada
seen from Malaysia
seen from Malaysia
Some of us are walking in situations wondering who is providing for me, but it's time to check your bag, you've been carrying Holy Spirit!
Planetshakers
If PSConfig/PSConfigUI encountered a problem it showed a generic error message and pointed to a PSCDiagnostics log with more details. The challenge for administrators was to locate the actual problem description inside this huge log file. This was not very convenient. The main reason for this behavior is, that the main upgrade work is not...
psconfig hasn’t changed much on the outside over the years. It’s typically been a “run it, cross your fingers and hope for the best” tool particularly in patching scenarios. When it works, its works great but when it doesn’t you’re left digging through piles of logs trying to get to the root of the problem.
But not anymore! After the August 2016 CU for SharePoint 2016 (and coming soon to SharePoint 2013) both the psconfig UI in the GUI and the command line have been updated to improve the output for error reporting.
From Stefan Goßner (@stefan_gossner):
To improve the user experience PSConfig has been updated to retrieve the actual problems the timer job encountered and shows them to the user directly in the UI.
Just today a nice person posted a comment on my blog explaining an issue some customers were running into which was most likely caused by the fact that these customers were using PSCONFIG.EXE rather than PSCONFIGUI.EXE after installing a CU.
Just today a nice person posted a comment on my blog explaining an issue some customers were running into which was most likely caused by the fact that these customers were using PSCONFIG.EXE rather than PSCONFIGUI.EXE after installing a CU.
It would be remiss of me not to post this here.
In case you need to use PSCONFIG.EXE to automate some tasks you should use the following command:
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources
I guess I'll have to update my tagline as well.
SBS2011: Integritätsbenachrichtigung / PSConfig
SBS2011: Integritätsbenachrichtigung / PSConfig
Nach einem SharePoint Update unter SBS 2011 erscheint nach der Anmeldung häufig ein Fenster mit folgendem Inhalt:
Microsoft Small Business Server 2011 Standard-Integritätsbenachrichtigung
Ein Update für Microsoft SharePoint Foundation 2010 wurde auf dem Small Business Server installiert. Sie müssen die Installation abschließen. Führen Sie dazu das PSConfig-Hilfsprogramm aus, um die…
View On WordPress
Forcing farm upgrade with psconfig.exe when it's being stubborn
psconfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures -cmd installcheck -noinstallcheck