All About SharePoint SharePoint 2010 and MOSS 2007 Resource Website

26Jan/120

Sandboxed Solutions in SharePoint 2010

This topic describes how site collection administrators can install, uninstall, and upgrade sandboxed solutions.

Installing a Sandboxed Solution


Just as with a farm solution, there are two steps to installing a sandboxed solution. In the context of sandboxed solutions, these two steps are called uploading and activating.

  • Upload stage: The upload stage consists of uploading a sandboxed solution to the solution gallery of a site collection. This parallels adding a farm solution.
  • Activation stage: The activation stage occurs after the solution is uploaded to a solution gallery. When a solution is uploaded, it is still functionally inert. Activating the solution makes it operate within the site by deploying files, registering event receivers, and running solution validation. This parallels deploying a farm solution. If a sandboxed solution includes a Feature that is scoped to the site collection level, the Feature is automatically activated when the solution is activated.

A sandboxed solution is installed by a site collection administrator to the site collection's solution gallery. This gallery also shows the current resource usage, average resource usage over the past two weeks, and the status of each sandboxed solution. For more information about the resource usage and monitoring system for sandboxed solutions, see Resource Usage Limits on Sandboxed Solutions in SharePoint 2010.

The following are the steps a site collection administrator takes to install a sandboxed solution.

To install a sandboxed solution

  1. From a page in the site collection, click Site Actions, and then select Site Settings.
  2. On the Site Settings page, click Solutions under the Galleries heading.
  3. On the Solutions tab of the Server ribbon, click Upload Solution.
  4. In the Upload Solution dialog box, click Browse, and browse to the sandboxed solution package (.wsp file). Click Open.
  5. The solution package is now in the site collection's solution gallery, but it is not yet deployed.
  6. In the Activate Solution dialog box, click Activate to activate the solution.

Uninstalling a Sandboxed Solution


There are also two steps to uninstalling a sandboxed solution.

  • Deactivation stage: A site collection administrator can deactivate a sandboxed solution from the site collection's solution gallery. Deactivation reverses most of the deployment actions of activation and, thus, turns off various capabilities of the solution. (If a solution that contains a Web Part is deactivated after the Web Part is added to a page, the Web Part displays an error instead of the usual information contained in the Web Part. The Web Part does not entirely disappear because deactivation does not undeploy the Web Part's .webpart file.)
  • Deletion stage: The deletion stage occurs when an administrator chooses to delete a sandboxed solution from the solution gallery. When the administrator chooses to delete a solution, additional validations and checks occur to warn the administrator of the negative consequences of an unintended deletion. A sandboxed solution cannot be deleted if it is still activated. When a sandboxed solution is deleted, it is moved into the Recycle Bin and can be restored or deleted permanently from the Recycle Bin.

Upgrading a Sandboxed Solution


A site collection administrator upgrades a sandboxed solution by installing a new sandboxed solution package (.wsp file) that has the same solution ID as the existing sandboxed solution but a different hash code.

If the sandboxed solution contains any Features, feature upgrade actions are also processed: During upgrade, the Feature definitions for the existing solution are compared with the Feature definitions for the new solution. Existing Feature definitions are upgraded on the site. All new Feature definitions are activated on the site. (Incoming requests for the sandboxed solution fail during the upgrade process.)

 

13Jul/110

What’s new in SharePoint 2010 SP1

What's new in SharePoint 2010 SP1

With all the latest buzz on the release of SharePoint 2010 Service Pack1, here is what SharePoint 2010 SP1 adds:

Site Recycle Bin: With this new feature, administrators can restore site collections and/or sites that have been accidentally deleted by their owners. How often does this happen? Hopefully not too often. But when it does, having recoverable copies without getting out backups is a plus. We've had the Recycle Bin feature in SharePoint for lists, libraries, and documents for while now; this is a nice additional safety net.

Broader browser support: SharePoint 2010 SP1 adds support for IE9 in Internet Explorer 8 Standards Mode, as well as for Google Chrome.

Shallow Copy: This new feature allows you to move site collections to new content databases without having to move all the Remote Blob storage content. Thus, only the ownership information is moved, without having to copy the unstructured data in the file store. The Move-SPSite PowerShell cmdlet has been enhanced to allow this feature

StorMan.aspx (Storage Space Allocation page: StorMan.aspx has been reintroduced in SharePoint 2010 SP1. It was removed from the original version of SharePoint 2010. Now that it is back, it adds the ability to display better information to users regarding their quota information. That makes it easier for users to clean up their sites by deleting content they may not need.

Support for SQL Server "Denali" (aka SQL Server 2011) ): Given that SharePoint is heavily integrated with SQL, it stands to reason that new features in the forthcoming Denali version of SQL Server will only make SharePoint 2010 better.

Cascading filters in PerformancePoint Services: Filters values can now be passed from one filter to the next.

7Jul/110

Improvements in SharePoint 2010 Service Pack1

As some of you already started testing the release of SharePoint 2010 Service pack1 and there is already enough fuss about this Service pack 1. Personally I feel that the SP1 release and the June CU for SharePoint 2010 releases added more fuel to the problem.

I have stressed this enough to install the Service pack 1 and then install the June CU.

Please see the link below for more detailed info on the improvements and various blogs posts by SharePoint MVP's.

http://blogs.c5insight.com/Home/tabid/40/entryid/198/Improvements-in-SharePoint-2010-Service-Pack-1.aspx

7Jul/110

How to Pass Querystring data into an InfoPath Form

Recently I came across this blog when trying to test some new functionality in  Infopath and SharePoint 2010.

How to easily send a value from the browser’s query string into an InfoPath form. Hopefully this will help somoeone. Please see the link below.

 http://blogs.msdn.com/b/infopath/archive/2010/06/03/how-to-pass-querystring-data-into-an-infopath-form.aspx

6Apr/110

SharePoint Illegal Characters

Today we started to bring in the documents for our new department and found lot of errors trying to move the folders and the documents to SharePoint. This is due to the Illegal characters in the naming conventions.

Characters that can't or shouldn't be used in File, folder and site names.

~ # % & * { } \ : < > ? / + | " . _

Notes:

  • Period can't be used consecutively in the middle of a name or at the end
  • Underscore shouldn't be used at the start of any name
  • Spaces are encoded as %20 (3 characters) and count to the 240 character Web-DAV file length limit

9Feb/111

How to Install a software update for SharePoint Foundation 2010

Recently we encountered some issues with the SharePoint updates. Even though the previous update procedures may be quite successful you may somehow find new or additional issues after the updates. Please see the below link from Technet explains the procedures for various SharePoint Server 2010 updates.

Click Here to see the Procedure for Updates

9Feb/111

SharePoint 2010 boundaries, Thresholds and Supported limits

SharePoint 2010 boundaries, Thresholds and Supported limits

Many would be considering SharePoint 2010 for their environment and questions will be asked to SharePoint Admins and Architects on the product.
Here is some handy information from Microsoft on the limitations (boundaries) of SharePoint 2010.

Before we dive into it, letz define what are the limit types:

  • Boundaries: Static limits that cannot be exceeded by design
  • Thresholds: Configurable limits that can be exceeded to accommodate specific requirements
  • Supported limits: Configurable limits that have been set by default to a tested value.

30Aug/105

Accounts used by application pools or service identities are in the local administrator group

Least Privilege Service Accounts for SharePoint 2010

In the last few years, enterprises have come to care about least privilege—the security concept that relates to an account being given only the permissions it requires to perform its tasks, nothing more. Least privilege is important for security, auditing, and compliance, and it applies not only to the accounts used by human beings, but also by service accounts.

And, like least privilege, enterprises have come to care about service accounts as well. I remember the days when it was perfectly acceptable to create a service account and set “password never expires.” Now, most enterprises have security policies that explicitly forbid such configuration because of the open door it leaves into a system.

During the next few weeks, I’ll be posting steps to help you deploy SharePoint with least privilege and to manage SharePoint service accounts. Let’s start by clearing up some confusion and all-too-prevalent mistakes that I see made with SQL Server, SharePoint administration, and farm accounts—and don’t be surprised that at least some of the confusion is due to the weirdness of the SharePoint setup wizard itself.

3 Accounts
Microsoft describes the administrative and service accounts required for initial deployment but skims over some important details and emphases, so let’s take a look at the three accounts this week, then we’ll return to some refiners next week.

2Aug/100

Best Practices in Developing Requirements for SharePoint Projects

This is one of my favorites blog posts from SharePoint Project Management Guru-Dux Raymond Sy.

I had the great opportunity to facilitate "Best Practices in Developing Requirements for SharePoint Projects" webcast for O'Reilly Media last July 28, 2010.

You can download the PPT presentation at: http://bit.ly/d1xbLN

Click the image below to watch the recorded presentation:

As promised, you can download the templates I showed at: http://www.meetdux.com/dl/req4sp.zip

In addition, I have compiled a list of valuable SharePoint resources related to the webcast:
- PM Resources for SharePoint 2010 Projects
- How SharePoint Can Deliver Project Transparency
- 5 Reasons Why SharePoint Ignorance is not Bliss
- Are you doing what it takes to Success at Implementing SharePoint?
SharePoint Worst Practices: 5 Common Mistakes to Avoid

Lastly, if you want to join this session live, make sure you attend Best Practices Conference in DC from Aug 24-27, 2010

26Jul/100

SharePoint 2010 Virtual Labs

Microsoft has published a number of Virtual Labs on MSDN and TechNet, simplifying a range of testing scenarios focused on SharePoint 2010. Customers already familiar with Microsoft’s Virtual Labs know that the resources are offered free of charge, and are available to all, not just MSDN and TechNet subscribers

“Microsoft SharePoint 2010 makes it easier for people to work together. Using SharePoint 2010, your people can set up Web sites to share information with others, manage documents from start to finish, and publish reports to help everyone make better decisions,” Microsoft revealed.
At the bottom of this article, you will be able to find a list of links pointing you to the TechNet and MSDN Virtual Labs for SharePoint Server 2010. Obviously, the TechNet Virtual Labs are focused on IT pros, while the MSDN resources are designed for developers. SharePoint Server 2010 RTM’d in mid-April 2010, along with additional products including Office 2010, Visio 2010 and Project 2010. As of May 12, 2010, SharePoint Server 2010 along with all the solutions enumerated above became available for purchase to business customers worldwide.

SharePoint Server 2010 Virtual Labs are essentially virtualized instances of the product running in Hyper-V on a Microsoft Server. Customers that want to access the resources will need to be running Windows and use Internet Explorer 8, IE7, or IE6. Since the virtual machines with SharePoint 2010 are running on Microsoft servers, customers don’t need to worry about details such as downloading, deploying or configuring the product. For each Virtual Lab, IT pros and devs get a 90-minute block of time per module, but they can also sign up for more

From TechNet:

TechNet Virtual Lab: Backup and Restore in SharePoint Server 2010
TechNet Virtual Lab: Business Continuity Management in SharePoint Server 2010
TechNet Virtual Lab: Configuring Remote Blob Storage FILESTREAM Provider for SharePoint Server 2010
TechNet Virtual Lab: Configuring Tenant Administration on SharePoint Server 2010
TechNet Virtual Lab: Configuring User Profile Synchronization in SharePoint Server 2010
TechNet Virtual Lab: Introduction to Microsoft SharePoint Server 2010 Upgrade
TechNet Virtual Lab: New IT Pro Features in SharePoint Server 2010
TechNet Virtual Lab: Windows PowerShell in SharePoint Server 2010

From MSDN:

MSDN Virtual Lab: Developing a BCS External Content Type with Visual Studio 2010
MSDN Virtual Lab: Developing a Visual Web Part in Visual Studio 2010
MSDN Virtual Lab: Developing SharePoint 2010 User Interface with Silverlight in Visual Studio 2010

14Jul/100

PowerShell Tips for SharePoint 2010

Here is a quick guide for PowerShell tips in SharePoint 2010:

http://www.powergui.org/servlet/KbServlet/download/2812-102-4534/SharePoint2010PowerShell.pdf

And this Technet article gives a complete mapping of STSADM commands with PowerShell Commands:

http://technet.microsoft.com/en-us/library/ff621081.aspx

8Jul/100

Thanks to SQL Server 2008 and SharePoint SQL 2008 Tips

With the SQL Server 2008 R2 RTM (Release to Manufacturer) and Launch, I want to give you my top reasons to upgrade with some additional tips to SQL 2008 from a SharePoint Admin/IT Pro perspective.  Now that it's RTM SharePoint (both WSS and MOSS) supports SQL 2008!

1. Transparent Encryption - SharePoint doesn't even realize the database has transparent encryption turned on.  I wouldn't recommend doing this on the Config database and especially would avoid the SSP and Search Databases.  If you do decide to use this, it would be on content databases only, and even then I'd recommend using it only on the ones you need it on.  Why?  For Performance reasons encryption is overhead even if it is transparent to the application.

2. Backup Compression - Now this is a big no brainer.  You can actually turn this on for the database so when backups happen even with the SharePoint Backup either Web UI or STSADM backup will backup the databases faster and more compressed.

3. Resource Governor - As all content is not created equal this gives you a chance to treat the most important data at a greater level of service.  I love the fact that I can limit the exposure as far as performance is concerned with apps that might share the same SQL storage.  Whether you're sharing with other SharePoint farms or sharing with other applications the resource governor allows you to be much more granular in deciding who gets what resources.

4. Mirroring enhancements - compressed logs means more reliability and quicker sync.  Also other enhancements make it more transparent to setup and configure mirroring.  Mirroring has taken some stride with SQL 2008.  A transparent failover was demo'ed at the SharePoint Conference with SQL 2008.  It wasn't clear in the demo how they dealt with the SSP, but I hope we get more prescriptive guidance from he product team on how to use the new features of mirroring to make DR for SharePoint even better.

5. Data compression - Careful here as well.  Data compression can give you more disk space, but don't expect your SharePoint databases to really shrink down.  The blobs aren't compressible.  The lists are though.  You might see 30% compression, but please avoid doing this on the Search database because of overhead unless the indexing performance isn't super key.  You might get a lot of compression on that database though... just watch for overhead impact.

2Jul/100

Stsadm Technical Reference for SharePoint Server 2007

Stsadm Technical Reference for SharePoint Server 2007

Microsoft Office SharePoint Server 2007 includes the Stsadm tool for command-line administration of SharePoint Server 2007 servers and sites. Stsadm is located at the following path on the drive where SharePoint Products and Technologies is installed: %COMMONPROGRAMFILES%\microsoft shared\web server extensions\12\bin. You must be an administrator on the local computer to use Stsadm.

Use the interactive application on this page to learn about the commands available. For more information, see Index for Stsadm operations and properties in the technical library.

For information about using the Stsadm tool with Windows SharePoint Services 3.0, see the Stsadm Technical Reference for Windows SharePoint Services 3.0.

http://technet.microsoft.com/en-us/office/sharepointserver/cc948709.aspx

29Jun/102

Disable “Delete this site” option in SharePoint

There were many a times some of our users always want to test us whether we had a good backup of SharePoint Sites and Data. Traditionally speaking even though you have all the backups required to restore a SharePoint Site, it makes sense to disable the option to delete the site in first place.

So how can we do this?

Sure. There are a couple of options for deployment. The best one is to package this feature into a Solution Package (wsp). There are plenty of articles on the web with instructions on how to do this, and there are a number of different methods and tools you can use.

Also I think this would be one of the Best practices which will save tons of time for the Administrators trying to restore a single site or subsite in SharePoint

However, the quickest and easiest (to explain) way to get this deployed is to create the feature manually, as follows.

Page 1 of 212