SharePoint Excellence

Are you an IT Professional looking to learn more about how SharePoint Online can help supplement your on-premise SharePoint 2010 Products deployment? then below is the list of a comprehensive set of learning materials that illustrate the benefits of SharePoint Online and how you can leverage its capabilities to bring additional value to your on-premise deployment. Video Learning Series Introduction Scenarios Users Support Conclusion Narrated Presentation Exploring SharePoint Online for IT Professionals Whitepaper Microsoft SharePoint Online: An Overview for Enterprise IT Professionals Reference : http://www.sharepointworld.in/2011/08/sharepoint-online-learning-materials.html

When upgrading to SharePoint 2010 from WSS 3.0, MOSS 2007 or Search Search 2008 there are some choices on whether or not the administrator wants to upgrade sites to the new SharePoint 2010 look and feel. If the sites are not upgraded to the new look and feel, there is a way to try out and then set the new look and feel through the site settings page->Title, description, and icon page. If the sites are upgraded to the new look and feel, there is not a way to go back to the previous versions look through the site settings page->Title, description, and icon page. There is hope though to go back to the previous version look and feel if it is needed, the SharePoint 2010 Management Shell. To enable the look and feel choice back to enabled on every site within a site collection, use the script below. Replace SiteCollection with the actual URL for your site collection. $SiteCollection=Get-SPsite http:// SiteCollection foreach($SPWeb in $SiteCollection.AllWebs){$...

This post is a copy of SharePoint World. As SharePoint Developers we have to quite often Recycle the application pool after deployment of our assemblies in GAC I have developed a small VBScript which I always add to my task bar to recycle the application pool of web application hosting my solution package. Copy this script in a vbscript file (.vbs)  and keep a short cut in quick launch by this we can avoid using iisreset. ** please replace <<Server Name>> by your server name and <<AppPoolName >> by application pool name of your web application strServerName = <<Server Name>> strAppPoolName =<<AppPoolName >> set objAppPools = GetObject("IIS://" & strServerName & "/w3svc/AppPools/" & strAppPoolName & "") objAppPools.Recycle()

I am working on SharePoint 2010. I created a blog sub site. My problem was, when I composing a post in blog I can insert images and link but the video insertion is in disabled mode. After some R&D I found SharePoint 2010 blog engine does not allow in insert videos in a blog post. There is a simple way to work around this limitation. Create new post and insert video embed code. SharePoint will escape all HTML characters when record is being saved in a database. What we have to do is to register a javascript function which will replace escaped HTML back with the original one. I used this jquery code snippet: <script type="text/javascript"> $(document).ready(function() { $(".ms-PostBody").html(function(index, oldHtml) { var matchStr = /(\&lt;object.+\/object\&gt;)/i; var m = oldHtml.match(matchStr); $.each(m, function (index, value) { oldHtml = oldHtml.replace(value, value.replace(/\&gt;/g, ">").replace(/\&l...

Recently I have a requirement is to migrate a SharePoint website created in wss3.0 to wss4.0. For moving the website to SharePoint 2010, you have to upgrade the WSS 3.0 to WSS 4.0. Follow these steps Take the backup of current live website (wss3.0) using stsadm utility.  Create a new machine having Windows 2008 64-bit R2 and SQL Server 2008 R2 Express 64-bit. Install WSS 3.0 64-Bit and created a Site Collection using the same URL of the original server. Then patched it until it matched the 32-bit WSS 3.0 exactly. Restore backup (created in step 1) on to newly created machine. Once we had a working site on newly machine then simply install SharePoint Foundation 2010 and it upgraded the server to WSS 3.0 to WSS 4.0. Upgrade all SharePoint custom web parts (previously build in 32 bit with VS 2008) as per 64 bit configuration.