kwizcom banner advertisement

How to Restrict Users from Switching Views in SharePoint?

8:30 PM    , , , ,
Yes, that was a common requirement from our SharePoint users! They wants to restrict other users from changing views from views drop-down in SharePoint. Here is how we can make it happen: Browse to the target list or library Click on Site Action > Edit Page On the Web Part Click Edit > Modify Shared Web Part Change Toolbar to either ‘Summary’ or ‘No toolbar’ Now users won't get the select ‘View’ drop-down menu This will hide the "View" drop down! Same thing can be done with SharePoint designer as well. And for users who needs the access,  you can create a target audience navigation link that links them to the proper view of the list/library. Disadvantage: What if user types the View URL directly? we can't stop them, right? So the perfect solution is Set Permissions and Restrict Access to SharePoint Views
How to Restrict Users from Switching Views in SharePoint? How to Restrict Users from Switching Views in SharePoint? Reviewed by Salaudeen Rajack on 8:30 PM Rating: 5

Get Installed SharePoint Farm Version Build Number/Patch Level/Service Pack

5:06 PM    , , , , , , ,
Want to know SharePoint version installed on your environment? There are several ways to get your MOSS 2007/SharePoint 2010 version build numbers. Here are some: How to find installed SharePoint 2013 build version? Simple! Navigate to Central Administration >> System Settings >> Servers in this Farm   1. You can find SharePoint 2007 version in Central Administration:     Go to Central Administration     Click the Operations tab.     Click Servers in farm under the "Topology and Services" section. This shows the version number for the farm and each individual server in the farm.       Find what version of SharePoint is installed in SharePoint 2010 : Find out SharePoint version you are running, Go to Central Admin >> Upgrade and Migration >> Select "Check product and path installation status" to get the currently installed version. 2. Open any of your SharePoint site, click Site Action >> and then click Site Se
Get Installed SharePoint Farm Version Build Number/Patch Level/Service Pack Get Installed SharePoint Farm Version Build Number/Patch Level/Service Pack Reviewed by Salaudeen Rajack on 5:06 PM Rating: 5

Fix "Missing Event Receivers" issue in SharePoint Migration

12:34 PM    , , ,
During SharePoint 2010 Migration, Preupgradecheck reported the issue of missing Event Receivers: The following event receiver assembly(s) are referenced by the content, but they are not installed on the web server So,  To resolve this issue we need to two steps: Get all list locations, where a particular event receivers  is registered Un-register the event receiver from the list/document library. Step 1: Get the list of location (Lists, Document Libraries) where the particular Event handler is registered: How to get the locations where event receivers are installed? Simple! Just execute the following STSADM command:   stsadm -o enumallwebs -includeeventreceivers > EventReceivers.txt Now we got the report. By opening the EventReceivers.txt in Excel, you can examine where that particular event receiver is in use. Step 2: Un-Register the Event Receivers: We have got the locations now. Next step is un-register them. Here comes the Handy tool: Event Receiver
Fix "Missing Event Receivers" issue in SharePoint Migration Fix "Missing Event Receivers" issue in SharePoint Migration Reviewed by Salaudeen Rajack on 12:34 PM Rating: 5
SharePoint 2010 Topology - For 25k Users SharePoint 2010 Topology - For 25k Users Reviewed by Salaudeen Rajack on 2:15 PM Rating: 5

Visual Upgrade All SharePoint Sites in a web application using PowerShell

5:52 PM    , , , , ,
After the Migration using database attachment method, Had to upgrade all sites to New SharePoint 2010 User Interface. Used this PowerShell code to accomplish. SharePoint 2010 visual upgrade powershell script ##### Visual Upgrade All SharePoint Sites to 2010 version in a Web Application ##### $SPwebApp = Get-SPWebApplication "http://migration.company.com" foreach ($SPsite in $SPwebApp.Sites) { foreach($SPweb in $SPsite.AllWebs) { $SPweb.UIVersion = 4 #set it to 3 if you want SharePoint 2007 look and feel $SPweb.Update() write-host $spweb.url } } read-host #just to pause Or you can use the SPSite's VisualUpgradeWebs() method: $webapp = Get-SPWebApplication <web-app-URL> foreach ($site in $webapp.sites) { $site.VisualUpgradeWebs() } Here is the Before/After images:
Visual Upgrade All SharePoint Sites in a web application using PowerShell Visual Upgrade All SharePoint Sites in a web application using PowerShell Reviewed by Salaudeen Rajack on 5:52 PM Rating: 5

Remove a Web Part Programmatically using PowerShell

6:45 PM    , , ,
We have had bunch of SharePoint 2007 site collections and recently upgraded them to SharePoint 2010. After the upgrade for some reasons, we wanted to delete a particular web part (Tip of the day web part) from the home page of All migrated sites' default.aspx page of the many sites. I get into Maintenance mode (by just appending " ?contents=1 " to the end of URL) and deleted the particular web part. But there are 1000+ sites migrated from SharePoint 2003, OMG! So, wrote the code to delete the error web parts Programmatically remove web parts. This saved my day! Here is the code to remove web part on default.aspx page of a particular site: Remove a Webpart Programmatically using PowerShell $SPsite = Get-SPSite http://sharepoint-site/sites/admin/ $SPweb = $SPsite.OpenWeb() $webpartmanager = $SPweb.GetLimitedWebPartManager(($SPweb.Url + "default.aspx"), [System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared) $webpartsarray = @() F
Remove a Web Part Programmatically using PowerShell Remove a Web Part Programmatically using PowerShell Reviewed by Salaudeen Rajack on 6:45 PM Rating: 5

MOSS 2007 to SharePoint 2010 Migration Project Plan

1:20 PM    , , , , ,
Here are the Milestones for SharePoint 2007 to SharePoint 2010 migration plan from one of my Migration Project from MOSS 2007 to SharePoint 2010 using Database attach method.  MOSS 2007 to SharePoint 2010 Migration - Milestones (Assuming planning stage is completed) S.No Task Name Resource I Prepare Existing Environment for Migration Run Pre-Upgrade check tool SharePoint Admin Resolve and Clean the Pre-upgrade checker reported issues SharePoint Admin Analyze and remove any un-used feature/site in existing environment SharePoint Admin Create list of customizations, Settings which needs manual move SharePoint Admin II Planning Review    Review Software Availability SharePoint Admin    Review Available Hardware SharePoint Admin    Obtain and verify Service accounts, DNS Entries, URLs SharePoint Admin & Infrastructure Team III Create and configure the new environment (DEV, STAGING, PROD) Identify and Prepare Architectural, Topology Diagrams SharePoint Admin Install nece
MOSS 2007 to SharePoint 2010 Migration Project Plan MOSS 2007 to SharePoint 2010 Migration Project Plan Reviewed by Salaudeen Rajack on 1:20 PM Rating: 5
Powered by Blogger.