Free SharePoint 2013 eBooks

Looking for new and free SharePoint reference books? This eBook collection will certainly satisfy your appetite for improvement in SharePoint technology field. There’s plenty of valuable tutorials here to keep you busy reading for a while. Be sure to grab few of these eBooks, check more related goodies at the bottom and don’t forget to tell us what you think.

SharePoint 2013 WCM Advanced Cookbook

SharePoint 2013 Server includes new and improved features for web content management that simplify how you design publishing sites, and enhances the authoring and publishing processes of organizations.

With SharePoint 2013 WCM Advanced Cookbook, you will learn about a full-fledged web content management system using Microsoft SharePoint Server 2013.

Publisher: Packt Publishing

By: John Chapman

Published Year: 2014
Pages: 436
Download PDF (7 MB)
Buy the paper book version

---

SharePoint 2013 Branding and User Interface Design

If you are planning, designing, and launching your brand using SharePoint, this book and author trio will walk you through everything you need to know in an understandable and approachable way.
This visual book provides step-by-step instructions in a simple and striking format that focuses on each of the tasks you will face in your own branding project.

Publisher: Wrox
By: Randy Drisgill, John Ross, Paul Stubbs
Published Year: 2013
Pages: 432
Download PDF (54 MB)
Buy the paper book version

---

Pro SharePoint 2013 App Development

Using step-by-step tutorials, author Steve Wright creates a sample SharePoint app throughout the course of the book, and you can walk with him through the entire lifecycle of a SharePoint app.

Publisher: Apress
By: Steve Wright
Published Year: 2013
Pages: 432
Download PDF (15.5 MB)
Buy the paper book version

---

Microsoft SharePoint 2013 App Development

Led by two SharePoint experts, you’ll learn development techniques such as building app lists, creating event handlers, and the major classes in the object model that provide access to content stored in SharePoint.

Publisher: Microsoft Press
By: Scot Hillier, Ted Pattison
Published Year: 2013
Pages: 202
Download PDF (34 MB)
Buy the paper book version

---

Pro SharePoint 2013 Branding and Responsive Web Development

Pro SharePoint 2013 Branding and Responsive Web Development is the definitive reference on the technologies, tools, and techniques needed for building responsive websites and applications with SharePoint 2013. The book focuses on solutions that provide the best browser experience for the myriad of devices, browsers, and screen orientations and resolutions.

Publisher: Apress
By: Eric Overfield, Rita Zhang, Oscar Medina, Kanwal Khipple
Published Year: 2013
Pages: 580
Download PDF (26 MB)
Buy the paper book version

---

Microsoft SharePoint 2013: Designing and Architecting Solutions

Determine the best design for your SharePoint implementation by gaining a deeper understanding of how the platform works. Written by a team of SharePoint experts, this practical guide introduces the Microsoft SharePoint 2013 architecture, and walks you through design considerations for planning and building a custom SharePoint solution. It’s ideal for IT professionals, whether or not you have experience with previous versions of SharePoint.

Publisher: Microsoft Press
By: Shannon Bray, Miguel Wood, Patrick Curran
Published Year: 2013
Pages: 488
Download PDF (55 MB)
Buy the paper book version

---

SharePoint 2013 User’s Guide, 4th Edition

Microsoft SharePoint 2013 provides a collection of tools and services you can use to improve user and team productivity, make information sharing more effective, and facilitate business decision–making processes. In order to get the most out of SharePoint 2013, you need to understand how to best use the capabilities to support your information management, collaboration, and business process management needs. The SharePoint 2013 User’s Guide is designed to provide you with the information you need to effectively use these tools.

Publisher: Apress
By: Anthony Smith
Published Year: 2013
Pages: 536
Download PDF (53 MB)
Buy the paper book version

---

Microsoft SharePoint 2013 Inside Out

You’re beyond the basics, so dive right into SharePoint 2013—and really put your business collaboration platform to work! This supremely organized reference packs hundreds of timesaving solutions, troubleshooting techniques, and workarounds. It’s all muscle and no fluff. Discover how the experts facilitate information sharing across the enterprise—and challenge yourself to new levels of mastery.

Publisher: Microsoft Press
By: Darvish Shadravan, Penelope Coventry, Thomas Resing, Christina Wheeler
Published Year: 2013
Pages: 904
Download PDF (124 MB)
Buy the paper book version

---

Pro SharePoint 2013 Administration, 2nd Edition

Pro SharePoint 2013 Administration is a practical guide to SharePoint 2013 for intermediate to advanced SharePoint administrators and power users, covering the out-of-the-box feature set and capabilities of Microsoft’s collaboration and business productivity platform.

Publisher: Apress
By: Robert Garrett
Published Year: 2013
Pages: 655
Download PDF (32 MB)
Buy the paper book version

---

Professional SharePoint 2013 Administration

The new iteration of SharePoint boasts exciting new features. However, any new version also comes with its fair share of challenges and that’s where this book comes in. The team of SharePoint admin gurus returns to presents a fully updated resource that prepares you for making all the new SharePoint 2013 features work right. They cover all of the administration components of SharePoint 2013 in detail, and present a clear understanding of how they affect the role of the administrator.

Publisher: Wrox
By: Shane Young, Steve Caravajal, Todd Klindt
Published Year: 2013
Pages: 840
Download PDF (56 MB)
Buy the paper book version

---

Practical SharePoint 2010 Branding and Customization

With Practical SharePoint 2010 Branding and Customization, SharePoint branding expert Erik Swenson cuts through the fluff and discusses accessible, easy-to-understand consulting and processes to create aesthetically pleasing, highly usable branded and customized SharePoint websites, both internally and externally. Designed to be a quick reference, how-to guide that lets you dive straight into the task at hand, you’ll find this book’s attention to detail and pragmatism make it an attractive companion during your branding experience.

Publisher: Apress
By: Erik Swenson
Published Year: 2013
Pages: 368
Download PDF (7 MB)
Buy the paper book version

---

Professional SharePoint 2013 Development

A team of well-known Microsoft MVPs joins forces in this fully updated resource, providing you with in-depth coverage of development tools in the latest iteration of the immensely popular SharePoint. From building solutions to building custom workflow and content management applications, this book shares field-tested best practices on all aspect of SharePoint 2013 development.

Publisher: Wrox
By: Reza Alirezaei, Brendon Schwartz, Matt Ranlett, Scot Hillier, Brian Wilson, Jeff Fried, Paul Swider
Published Year: 2013
Pages: 816
Download PDF (47 MB)
Buy the paper book version

---

Exploring Microsoft SharePoint 2013

Your guide to the most significant changes in SharePoint 2013. Discover what’s new and what’s changed in SharePoint 2013—and get a head start using these cutting-edge capabilities to improve organizational collaboration and effectiveness.

Led by a Microsoft MVP for SharePoint, you’ll learn how to take advantage of important new features and functionality, including app development, collaborative social enterprise tools, enhanced versioning, themes, improved search, and an extended client object model.

Publisher: Microsoft Press
By: Penelope Coventry
Published Year: 2013
Pages: 200
Download PDF (17 MB)
Buy the paper book version

---

SharePoint 2013 For Dummies

SharePoint Portal Server is an essential part of the enterprise infrastructure for many businesses. Building on the success of previous versions of SharePoint For Dummies, this new edition covers all the latest features of SharePoint 2013 and provides you with an easy-to-understand resource for making the most of all that this version has to offer. You’ll learn how to get a site up and running, branded, and populated with content, workflow, and management. In addition, this new edition includes essential need-to-know information for administrators, techsumers, and page admins who want to leverage the cloud-hosted features online, either as a standalone product or in conjunction with an existing SharePoint infrastructure.

Publisher: Wiley
By: Ken Withee
Published Year: 2013
Pages: 384
Download PDF (32 MB)
Buy the paper book version

If you are unable to download email me

Ref : topsharepoint

SharePoint Tasks List plus Project – Better Together

SharePoint tasks lists provide a great way to collaborate and stay up to date on the status of your projects. By using Microsoft Project Professional, you can take your project management to the next level by using more advanced features like scheduling and even create gorgeous and comprehensive reports. In a way, the SharePoint site and its tasks lists are where team members can view and edit the progress of their tasks, and Project Professional is where project managers can manage the progress of their projects. SharePoint tasks list sync empowers you to use the great functionalities of both Project and SharePoint tasks lists, at the same time.

You can create a new SharePoint tasks list that supports tasks with hierarchy, and indent/outdent those tasks while typing them in SharePoint, using the Alt+shift+Right/Left shortcuts. Then, in order to sync this SharePoint tasks list with Project, all you need to do is select the “Open with Project” button in the List tab of the ribbon:

This will open your tasks list along with the timeline view in Project Professional and you’ll even be started in a screen that walks you through 3 steps to show you how you can take advantage of the powerful features of Project:

And when you switch to the Gantt view, you can see the same tasks list as was in SharePoint:

You can continue editing the project plan in Project, and when you hit Save, Project will automatically sync the plan with the SharePoint tasks list, and also save the project file (.mpp) in the Site Assets library of the SharePoint site. Therefore, every time you, or any other project manager, open the project plan, you can view the most recent status of the project. In 2013, we are saving an up to date project file in the Site Assets library so that users won’t have to deal with multiple conflicting or out-of-date project files. Moreover, we have greatly improved the conflict resolution mechanism so we now look for conflicts at the cell-level instead of the task-level.

Accessing and re-opening this project is very easy: if you are in the SharePoint site, you can open the same project plan by selecting the “Open with Project” button. Alternatively, if you already have Project Professional open, you can find this project in the Recent Projects list in the Open tab:

Using the SharePoint tasks list feature, you can also convert standalone project plans into SharePoint tasks list and start collaborating with other team members on those plans. For instance, if you are using Project Professional to manage a special launch event, you can now go to the Save As tab of the File menu and create a new project site with an associated SharePoint tasks list:

This will create a new Project Site and save the project plan in the Site Assets library of that site. From that point on, you can open this this project plan from the tasks list and keep the tasks list and the project plan in sync.

During the SharePoint tasks list sync, we sync the following fields between your SharePoint list and Project by default: task name, start date, finish (due) date, % Complete, resource name, and predecessors. However, if you want to map more fields to be synced between Project and SharePoint, you can do so in the Info tab of the File menu: open the “Map Fields” dialog, and pick any new fields that you’d like to sync. This way, you can have your team members report on other custom fields, or generate reports based on non-default SharePoint columns.

Ref : Office Blogs

New Best Practices for SharePoint 2013 Farm Design – Streamlined Topology

Microsoft some time back released “Streamlined Topology for SharePoint 2013”, new way to build & configure SharePoint 2013 farm. It’s really nice to see official documentation on new approach which I had first heard at SPC12 during SPC119 “Designing Your SharePoint Server 2013 Enterprise Deployment” Session. In that session Luca Bandinelli delivered prescriptive guidance to build SharePoint 2013 On-Premises farm similar to SharePoint Online based on Microsoft’s lessons learned and best practices while maintaining and building their own SharePoint online data centers.

As far as Physical Topology, We have three tiered approach since MOSS 2007 days. In MOSS 2007, we had Web Tier, Application Tier (Central Admin, Shared Service Providers – Search, Excel, Profile Import), and Database Tier. In SharePoint 2010, there wasn’t much changed and we had almost same 3-tier topology (except Application Tier dedicated for Service Applications instead of SSP) but dedicated servers can be added in application tiers for high preformat service applications like Search or PerformancePoint etc.

With SharePoint 2013, we had lot more service applications and many of these service applications can be grouped in similar groups either based on their CPU and RAM needs or either based on their latency, throughput, or workloads/resource utilization to optimize system resources and maximize performance for users. Even though we can get away with traditional 3-tier topology approach in SharePoint 2013, there are some new services may require additional tier and dedicated attention on Application tier. All the windows & WCF services can be divided into – very low, low, and high tolerant latency and this may require us dividing up application tier in multiple tiers for each type of latency tolerant service applications.

As shown in the diagram below, Microsoft provides us alternative farm design topology by redefining traditional web and application tier into multiple tiers.

Traditional webtier is redefined as Caching and Request Processing tier which would group similar web front end servers forend user request processing along with new service applications like Request Management and Distributed Cache which would require very low latency but very high throughout. Request Management is disabled by default and Distributed Cache is enabled by default. Since Request Manager is CPU intensive and Distributed Cache is memory intensive, both of these services can share same server without any major performance hit.

• Traditional Application tier is divided into two optimized tiers – Front End Servers and Batch Processing Servers.
  • Front-End Servers would group similar service applications which would serve user requests with low latency, low resource utilization, and optimized for faster performance and response time. Services like Central Administration, Managed Metadata, User Profile, App Management, Search Query Role, and Business Data Connectivity are ideal for Front End Servers.
  • Batch Processing Servers would group similar service applications which would typically require long running back ground processes, high latency, and high resource utilization, and optimized for higher workload by maximizing system resources. Services like User Profile Sync, Work Management, Search Crawl and Index Role, Workflow, Machine Translation etc. are ideal for Batch Processing Servers. For large scale farms, Batch processing tier can be divided further into specialized load servers for services like Search, PerformancePoint, or Excel Services which can cause high spikes in performance during peak time.
  • Database tier stays same in both traditional and streamlined model. These servers can be either clustered, mirrored, or configured with Always On.

 

Ok, So, What’s your take on this new Model..

Having said that, my take on this new approach is what I used to say while designing SharePoint 2010 topologies. Even though you would ideally love to plan for 4-5 tier topology, it may not be possible in real world due to possible hardware funding issues. You are looking at nearly 10 high performing virtual machines or physical hardware, which may be daunting to get through budget approval  process.

Depending on your situation, number of users, and size of farm, you may get away with running traditional three tiered approach as long as they have enough hardware resources like RAM and CPU allocated. With the traditional 3-tier approach, you can run Distributed Cache and Request Management on Web Servers, Central Admin and all the Service applications in Application tier as initial farm design and plan to scale out or add more dedicated servers for specific workloads like Search as needed.

Resources

• Streamlined topologies for SharePoint Server 2013
• Services on server install worksheet for streamlined SharePoint Server 2013 topologies
• Traditional topologies for SharePoint 2013
• Services on server install worksheet for traditional SharePoint Server 2013 topologies
• Plan service deployment in SharePoint 2013
• Nik Patel’s SharePoint World

How to Identify the Version and Service Packs installed on a SharePoint 2013 Server

In many cases, we may not be bothered about the Version, Service Packs installed on our Server when we do the development. It is obvious that, when we get the requirement, immediately we will start analysis the requirement.

But recently there was a situation that one of our client wants to move on to the new Service Pack which released on this April. In that case, we may also have to analyze the impact of the new Service Pack. Before knowing that, I just wanted to know, what are the things installed on our Dev environment first. Then on top of it, what needs to be installed and what would be the impact after installation.

To answer all these questions, First we need to know what is the version installed on our Farm. Use the following command to get the Version of the product installed using PowerShell script.(Get-SPFarm).Products.

First Run ISE as below :

Then after selecting the Commands of “Add.PSSnapin” output of the above command will be something like,

By seeing the GUID, we will be able to identify the Product. These GUIDs will not change. On all the environments, and all the machines, the GUIDs will remain same.

Here are all of the product GUIDs:

GUID : 35466B1A-B17B-4DFB-A703-F74E2A1F5F5E Product : Project Server 2013

GUID : BC7BAF08-4D97-462C-8411-341052402E71 Product : Project Server 2013 Preview

GUID : C5D855EE-F32B-4A1C-97A8-F0A28CE02F9C Product : SharePoint Server 2013

GUID : CBF97833-C73A-4BAF-9ED3-D47B3CFF51BE Product : SharePoint Server 2013 Preview

GUID : B7D84C2B-0754-49E4-B7BE-7EE321DCE0A9 Product : SharePoint Server 2013 Enterprise

GUID : 298A586A-E3C1-42F0-AFE0-4BCFDC2E7CD0 Product : SharePoint Server 2013 Enterprise Preview

GUID : D6B57A0D-AE69-4A3E-B031-1F993EE52EDC Product : Microsoft Office Web Apps Server 2013

GUID : 9FF54EBC-8C12-47D7-854F-3865D4BE8118 Product : SharePoint Foundation 2013

And to know about the Service Packs, there is no need of any PowerShell Commands. That we can directly go to the Central Administration and find.

Go to Central Administration.

Click on “Upgrade and Migration” on the Quick Links.

Click on “Check Product and Patch Installation Status”

This will tell us the current Patches Installation. By seeing the Version column we can identify. On the screen shot above shared, there is no SP installed.

Using PowerShell – Make a new site – SharePoint 2010

1. Launch PowerShell for SharePoint Administration

2. Get-help

3. Make a new site using PowerShell

4. Get a list of all the site collections that exist in the farm

SharePoint Content Deployment Successful, but Throwing Event IDs 6398 & 4958

Recently, I launched a public-facing site with a client that utilizes content deployment.  Every 15 minutes, changes from their ‘Content Authoring’ (internal) environment are published out to their read-only Production environment.  For well over a month, things have been working very well, with no errors.  Suddenly the other day, I noticed two events being thrown every time the content deployment job was run:

Event ID 6398 from the Timer job detail was:

Log Name:      Application
Source:        Windows SharePoint Services 3
Date:          10/15/2009 11:45:15 PM
Event ID:      6398
Task Category: Timer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER

Description:
The Execute method of job definition Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition (ID 809108c8-7685-46b1-9580-7fa68113a364) threw an exception. More information is included below.

ContentDeploymentJobReport with ID ‘{00000000-0000-0000-0000-000000000000}’ was not found.
Parameter name: jobReportId

Event ID 4958 from Content Deployment had the following detail:

Log Name:      Application
Source:        Office SharePoint Server
Date:          10/15/2009 11:45:15 PM
Event ID:      4958
Task Category: Content Deployment
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER

Description:
Publishing: Content deployment job failed. Error: ‘System.ArgumentOutOfRangeException: ContentDeploymentJobReport with ID ‘{00000000-0000-0000-0000-000000000000}’ was not found.
Parameter name: jobReportId
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobReport.GetInstance(Guid jobReportId)
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.get_LastReport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.get_SQMDeploymentJobFlags()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.CollectSQMData()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean runAsynchronously)
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition.Execute(Guid targetInstanceId)’

Now what I found really strange was that even though these errors were being thrown, the content deployment job was running successfully.  The history showed all objects were being exported/imported properly, ‘Successful’ was listed for the status, and the content managers were seeing their changes.  So it was looking like these events were false.

I did some digging through the SharePoint logs after I turned on verbose logging for content deployment, and nothing other than what was already being reported in the Event Viewer could be found.  So I took things one step further – I went over to the SharePoint_Config database, and performed a lookup of the Content Deployment Job Definition GUID from event ID 6398 against the TimerRunningJobs table:

SELECT * from TimerRunningJobs
where jobid = ’809108c8-7685-46b1-9580-7fa68113a364′

And what I found was very interesting:

As you can see, the error is related to the Content Deployment Timer Job for Quick Deploy… but in this particular implementation, we are not using Quick Deploy.

So… I disabled the Quick Deploy jobs in Central Administration for my Content Deployment Path, and voila – the events stopped coming up!

Ref : Jack of all that is Microsoft, Master of None

Creating Connected Web Parts in SharePoint 2010

Connected web parts allow you to provide enhanced interactivity within SharePoint application pages. Consumer and provider web parts pass information back and forth, which can be very useful in master-details scenarios, such as selecting a list item and seeing additional information about that item. In this sample from TrainSignal’s SharePoint 2010 Development course, speaker walks you through the process of creating a provider web part that has a message among its properties, and connecting it with a consumer web part that displays the message from the provider

Ref : Creating Connected Web Parts in SharePoint 2010

Moving sites and subsites in SharePoint 2007 Portals

Moving sites and subsites within SharePoint 2007

There is a really cool way that you can move a sharepoint site up or down in your hierarchy.

Let’s say you created a sharepoint site your root level (ie http://intranet/website) and six months later you decide it really should be contained under your IT subsite (http://intranet/it/website). You can use the program STSADM to move a site from one location to another.

Steps to move a WSS subsite.

1. Create the new target URL (I created a blank site @ http://intranet/it/website)
2. Fire up the command line
3. CD \”Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN”
4. Export the old URL using the following Command:

stsadm -o export -url http://intranet/website -filename c:\test\backup.cmp

5. Import the file back into Sharepoint using the following command:

stsadm -o import -url http://intranet/it/website -filename c:\test\backup.cmp

That’s it! You have moved your website. You need to check user permissions especially if you are moving to a new subsite!

OTHER COOL STUFF: There is an option to -includeusersecurity while you do the export. You can also choose whether or not to pull all the revision history over with the doc libs or not…

For a full view of options for Export / Import, run the following commands to see all your options:

stsadm -o export

stsadm -o import

Ref : Rob Ashcroft’s

Configuring MOSS 2007 server to search pdf documents – install and configure pdf ifilters

In this article we will see how to configure MOSS 2007 to search PDF documents.

 

Application Server:

1. Download Adobe PDF IFilters 6.0
2. Start –>Run–>> Services.msc and stop the IIS Admin service. The reason we need to do this is, the IFilters configuration needs an update to DOCICON.XML.
3. Download the pdf icon image   of size 17X17 from the following location and save it as “icpdf.gif” somewhere to the local hard disk
   http://www.adobe.com/misc/linking.html
4. Copy the icpdf.gif to the following location
   “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images”
5. Go the C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\
6. Edit the DOCICON.XML by adding the following entry  pdf” Value=”icpdf.gif”/> 
7. Perform an IIS RESET
8.  
9. Go to Search Settings under Central Administration and add the pdf as the new file type 

Indexing Server:

1. Run the IFilters installer on the Indexing Server
   1. Locate and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\GUID\Gather\Search\Extensions\ExtensionList
   2. On the Edit menu, point to New, and then click String Value.
   3. Type 38, and then press ENTER.
   4. Right-click the registry entry that you created, and then click Modify.
   5. In the Value data box, type pdf, and then click OK. 
2. Go the C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\
3. Edit the DOCICON.XML by adding the following entry <Mapping Key=”pdf” Value=”icpdf.gif”/> 
4. Perform an IIS RESET
5. 
6. Go to Search Settings under Central Administration and add the pdf as the new file type
7. 
8. Go to SharePoint Service Provider
9. Click on Search Setting
10. 
11. Click on Content Source
12. 
13. Perform the crawl again
14. 

Data: application/pdf 

1. Upload the PDF documents to the Windows SharePoint Services 3.0 Web site.
   1. Stop and then start the Windows SharePoint Services Search service. To do this, follow these steps:a. Click Start, click Run, type cmd, and then click OK.
   2. Stop the Windows SharePoint Services Search service. To do this, type net stop spsearch at the command prompt, and then press ENTER.
   3. Start the Windows SharePoint Services Search service. To do this, type net start spsearch at the command prompt, and then press ENTER.
   4. Type exit to exit the command prompt.

 Now MOSS is ready to search pdf documents.

Ref : C # Corner

Read-only lock on a SharePoint site collection, or Why can’t I edit anymore ?

For some reason, long-time users were unable to edit list items.  I figured we had a permissions issue, so I popped in to look at the Site Settings — and found that I couldn’t.  A quick trip to Central Administration showed that I was still listed as a Site Collection Administrator, but I had no power at all on the site collection in question.

A quick glance at the logs told me that the server had recently shut down unexpectedly (this is a Hyper-V virtual machine).  Apparently, in the confusion, somehow SharePoint decided to lock the site collection as Read Only.  This can be remedied in one of two ways:

1)  In Central Administration, go to Application Management->SharePoint Site Management->Site collection quotas and locks.  Once you have arrived, select the correct application and site collection, and you will have the opportunity to view and set the lock status of the collection (it most likely will be set to “Read-only”, and you’ll want to move that radio button to “Not locked”).

2)  Fire up stsadm and issue the following command:

stsadm -o setsitelock -url http://myportalsitecollection -lock none