There are more than 300 SharePoint PowerShell cmdlets and its growing and changing from time-to-time. How administrator or developer will be able to remember all of those cmdlets? The answer :
Using HELP (get-help) if you have access to PowerShell console and Microsoft.SharePoint.PowerShell snap-in ; PowerShell for SharePoint Command Builder (http://bit.ly/16masoE).
The PowerShell for SharePoint Command Builder is a powerfull dictionary tools – build using Silverlight that lists all SharePoint’s PowerShell cmdlets. It’s been around before SharePoint 2013 becomes public – contains all SharePoint 2010 and SharePoint 2013 CMDLETS description.
Eventually its not too user friendly – but all developer/IT Pro should easily understand what to do with the tools. Basically there are 2 things that you [read more...]
In case you have not tried Windows Azure to host your blog, I think it is time todo so; because Windows Azure is also capable to host many types of blogging platform such as WordPress. I stumbled upon “Convert a WordPress Site to Multisite” – when trying to figure-out how to host my blog in Windows Azure.
Instead of using FTP or GIT as described in that article, I use WebMatrix and standard WordPress configuration in Windows Azure. The WebMatrix allow us to load deployment configuration XML directly from the Windows Azure web sites – so basically we don’t need to perform extra configuration on the client side.
By default, Windows Azure website will provide sub-domain under *.azurewebsites.net [read more...]
EnglishI have same experience with Arudell, who wrote SharePoint Installer Troubleshooting here, however with different path of achieving the success.
Among some servers in our farm, we had almost un-fixed issue. The problem is all server have been updated with SharePoint Server 2010 SP1 but the newer servers show version 14.0.6028.1000 and on the older servers show version 14.0.6029.1000. This is really stressing, since I can not re-deploy SP1 to fix the issue. And moreover, adding CU after SP are not helping at all.
Service Pack 1 mismatch
Basically the solution presented by Arudell, is to remove problematic product (version 14.0.6028.100) and manually replace it with correct binaries extracted and manually installed [read more...]
Its been a history, that some early release of CU contains regression bug or a slip-streamed bits contains incomplete update. Early-adopter sometimes face a dead-end situation, where the early-release patch has been deployed and unable to install the new update. The reason is because every patch/CU also contains version checking mechanism that will prevent installation/patching to wrong system. Basically, it does your homework to read the pre-requisites in the system.
Is it really a dead-end?
If you’re 110% sure that you have read all the pre-requities, and your system need the updated patch – execute the patch with PACKAGE.BYPASS.DETECTION.CHECK=1 option. For example,
This option will bypass version checking, and force patch installation.
Finally, I should remind you [read more...]