If you ever need to compare versions of Sharepoint (Foundation, Standard, Enterprise) check out the following site:

http://sharepoint.microsoft.com/en-us/buy/Pages/Editions-Comparison.aspx

This page offers a break down of all SharePoint features, by version. Each feature is demonstrated by a video overview of the functionality.
A great resource for anyone, sales/business analyst/dev, who needs to describe SharePoint features to end users.

SharePoint Server 2010:

• SharePoint Server 2010 Tech Center is a gateway into the IT Pro documentation for SharePoint Server 2010 and a location for RSS feeds of new content.
• Resource Centers provide information across the product lifecycle for activities and solutions.
• TechNet articles are organized by the product lifecycle – evaluate, plan, deploy, operate, etc. Content includes a newly published page with an RSS feed, so you can keep up with what we’ve published, and a roadmap to the content.
• Worksheets are Microsoft Excel files that you can use to record information that you gather and decisions that you make as you plan your deployment of Microsoft SharePoint Server 2010.
• Models are poster-sized illustrations of Microsoft SharePoint Server 2010 architecture and concepts.

SharePoint Foundation 2010:

• SharePoint Foundation 2010 Tech Center is a gateway into the IT Pro documentation for SharePoint Foundation 2010 and a location for RSS feeds of new content.
• Resource Centers provide information across the product lifecycle for activities and solutions.
• TechNet articles are organized by the product lifecycle – evaluate, plan, deploy, operate, etc. Content includes a newly published page with an RSS feed, so you can keep up with what we’ve published, and a roadmap to the content.
• Worksheets are Microsoft Excel files that you can use to record information that you gather and decisions that you make as you plan your deployment of Microsoft SharePoint Foundation 2010.
• Models are poster-sized illustrations of Microsoft SharePoint Foundation 2010 architecture and concepts.

 

First version of SharePoint 2010 Administration Toolkit is now available. The toolkit included a couple of tools that were shipped releases and are now adapted to SharePoint 2010, along with two new tools.

User Profile Replication Engine 2010 (UPRE2010): this tool got a complete overhaul and was converted to PowerShell. It now allows you to replicate Profile and Social data between SharePoint 2010’s User Profile Application (UPA), as well as backward compatibility with SharePoint 2007’s SSP. You can replicate between SSP’s or UPA services, as well as across versions. (Note that only Profile data can be replicated across versions, as SSP contains no Social activity tracking).

The Security Configuration (SCW) Manifest: SCW is an attack surface reduction feature in Windows Server. This manifest adds roles for SharePoint 2010 Products to Windows Server 2008 with SP2 or Windows Server 2008 R2.

The Content Management Interoperability Services (CMIS) Connector: enables SharePoint users to interact with content stored in any repository that has implemented the CMIS standard, as well as making SharePoint 2010 content available to any application that has implemented the CMIS standard.

The Load Testing Kit (LTK): LTK generates a Visual Studio Team System 2008 (VSTS) load test based on Windows SharePoint Services 3.0 IIS logs. The VSTS load test can be used to generate synthetic load against Microsoft SharePoint Foundation 2010 as part of a capacity planning exercise or a pre-upgrade stress test.

The toolkit can be downloaded from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en

The toolkit documentation can be found here:

SharePoint Foundation 2010: http://technet.microsoft.com/en-us/library/cc508986.aspx

SharePoint Server 2010: http://technet.microsoft.com/en-us/library/cc508851.aspx

The BlackBerry Enterprise Server Express Edition offers businesses the ability to enable their staff to use BlackBerry devices to receive push-based email from an existing Microsoft Exchange installation – both standalone Exchange servers and the Microsoft Small Business Server product.
A free download from the BlackBerry web site, the solution is not limited to any set number of users and requires only that users have a BlackBerry data tariff on their SIM card with their network operator.
A 10,000 user CAL is supplied with the download by default:

Features

BES Express is based on the BES 5.0.1 MR1 code, and as such offers much (but not all) of the same functionality:

• Web-based administration
• 6 pre-defined administrative roles
• BlackBerry Web Desktop
• Over 35 IT policies for device management (see below), including device wipe
• HTML email support
• Flag emails for follow-up
• Mail folder management
• Remote email search
• Set out of office status and message
• Forward calendar appointments
• Open attachments in calendar appointments
• Free / Busy lookup
• Remote file access
• Support for audio (AWE, WAV, MP3, WMA) files

The following features are NOT available in BES Express:

• Cradle-less enterprise activation (when used with the BIS tariff on client devices)
• Ability to define multiple administrative roles
• BlackBerry Monitoring Service
• BlackBerry Enterprise Transporter Tool
• High Availability deployment options
• Support for BlackBerry Mobile Voice System (MVS)
• Support for enterprise instant messaging and social networking integration

At the time of writing, BES Express is only available in English.
BES Express is not compatible with Lotus Domino or Novell Groupwise installations.

System Requirements

Operating System

• Windows Server 2003 SP2 (32-bit or 64-bit)
• Windows Server 2003 R2 SP2 (32-bit or 4-bit)
• Windows Server 2008 SP2 (32-bit or 64-bit)
• Windows Small Business Server 2003
• Windows Small Business Server 2008

Microsoft Exchange Messaging Server

• Microsoft Exchange 2003 SP2
• Microsoft Exchange 2007 SP1
• Microsoft Exchange 2010 including Update Rollup 1

Microsoft Exchange System Tools

• (Exchange 2003) Microsoft Exchange 2003 SP2 System Manager or MAPI client and CDO 1.2.1 version 6.5.8039.0 or later
• (Exchange 2007) MAPI client and CDO 1.2.1 version 6.5.8067.0 or later
• (Exchange 2010) MAPI client and CDO 1.2.1 version 6.5.8146.0 or later

Hardware

(Up to 200 users)
• Single processor, 2.0GHz Intel Xeon (2 processors recommended)
• 2GB memory
• 2 HDDs, RAID 1

  (Up to 500 users)

• Two processors, 2.0GHz Intel Xeon
• 2GB memory
• 2 HDDs, RAID 1

  (Up to 1000 users)

• Two processors, 2.0GHz Intel Xeon
• 3GB memory
• 2 HDDs, RAID 1

Database

Any of the following database management systems are supported:

• MSDE 2000 SP3
• Microsoft SQL Server 2005 SP3 (32-bit or 64-bit)
• Microsoft SQL Server 2005 Express Edition SP3
• Microsoft SQL Server 2008 SP1 (32-bit or 64-bit)
• Microsoft SQL Server 2008 Express Edition SP1 (32-bit or 64-bit)

If using a database system earlier than SQL 2005 SP3, the following hotfix should be installed on the database server – http://support.microsoft.com/?kbid=960082

Miscellaneous

In order to provide support for audio attachments, Windows Media Player 9 or later is required on the BES.

Internet Explorer 6 or later is required to access the web administration console.

Firewall

The BES requires outbound-initiated, bi-directional access to the Internet on TCP port 3101 as well as access to DNS.

RIM recommend operating up to a maximum of 75 users if the BES Express software is being installed directly onto the Exchange server itself. On a standalone server, BES Express can support up to 2,000 users. Multiple BES Express servers can be deployed in the same BlackBerry domain.

Preparing an Exchange 2010 environment

NOTE – this article assumes an Exchange 2010 installation only. Visit the BES Express section of the blog for details on installing the solution against Exchange 2003 or 2007.

Ensure that Exchange 2010 Update Rollup 1 is installed on the Exchange 2010 server. This package is available here – http://www.microsoft.com/downloads/details.aspx?FamilyID=371add31-d7a0-4…

If installing the BES Express software on the Exchange server itself, the Exchange server should NOT itself also be a domain controller.

Create a domain user account called BesAdmin

On the Exchange server, in the Active Directory Users and Computers console, create a domain user called “BesAdmin” and assign it an Exchange mailbox. Set the user account password to never expire.

Send an email to the BesAdmin user to initialise the Exchange mailbox.

Assign the BesAdmin user local administrative rights

On the server that is to host the BES Express, make the BesAdmin domain user a member of the local administrator group. NOTE – the BES Express server will first need to have been added to the Domain if not done already.
To do this, on the BES Express server, right click on the icon for My Computer and select Manage. Browse to Local Users and Groups –> Groups –> Administrators and add the BesAdmin user:

Assign the BesAdmin user “log on as a service” rights

On the BES Express server, also assign the BesAdmin domain user account “log on as a service” rights. To do this, select Administrative Tools –> Local Security Policy –> User Rights Assignment –> Log on as a service and add the BesAdmin user:

Assign “Receive As” and “Administer Information Store” rights to the BesAdmin user

On the Exchange server, launch the Exchange PowerShell and issue the following command:

Get-MailboxDatabase | Add-ADPermission -User "BesAdmin" -AccessRights
 ExtendedRight -ExtendedRights Receive-As, ms-Exch-Store-Admin

Assign Exchange View-Only Administrator rights to the BesAdmin user

Still within the Exchange PowerShell, now issue the following command:

Add -RoleGroupMember "View-Only Organization Management" -Member "BesAdmin"

Assign “Send As” rights on the domain to the BesAdmin user

Within the Active Directory Users and Computers console, open the View menu and select the option to display Advanced Features.

Right click on the domain and select Properties. Click on the Security tab:

Click on the Advanced button:

Click on Add and type in the name of the BesAdmin user:

Select the option to Apply Onto User Objects.

Scroll down to the bottom and tick the option to enable Send As rights:

For good measure, also enable Send As rights on the Exchange server itself within the Exchange PowerShell. Launch the console and issue the following command:

Add-ADPermission -InheritedObjectType User -InheritanceType Descendents -ExtendedRights
Send-As -User "BesAdmin" -Identity "CN=Users,DC=domain,DC=com"

(where “domain” and “com” should be substituted for your specific domain details, eg: DC=brightpoint,DC=co,DC=uk and so on)

To force all of the above changes to take effect on the domain, it may be worth running a group policy update. On the Exchange server click Start –> Run and issue the command “gpupdate /force”

Turn off Exchange 2010 Client Throttling

Exchange 2010 uses client throttling by default to protect the Exchange server from excessive user demands. RIM recommend turning off this feature as it can have an adverse affect on the performance of the BES solution. This is done within the Exchange PowerShell console.

Launch the console and issue the following command to get the “Identity” of the default throttling policy”

Get-ThrottlingPolicy | Where-Object {$_.IsDefault -eq "True"} | FL Identity

the Identity will be displayed:

Now issue the following command:

Set-ThrottlingPolicy -RCAMaxConcurrency $null

You will be prompted to enter the Identity to apply the policy to, enter the result returned above:

Increase the maximum number of connections to the Exchange Address Book Service

On the Exchange Server (or specifically the Client Access Server in a multi-box deployment), browse to C:\Program Files\Microsoft\Exchange Server\V14\Bin and locate the file “microsoft.exchange.addressbook.service.exe.config” and open it in NotePad:

Locate the line “MaxSessionsPerUser”:

Increase the value to 100000. Save the file then restart the Address Book Service:

Install the Exchange MAPI CDO 1.2.1 package

The Microsoft Exchange MAPI CDO 1.2.1 package must be installed to provide the BesAdmin user a MAPI connection to Exchange mailboxes as well as access to calendaring information.

Download here: http://www.microsoft.com/downloads/en/details.aspx?FamilyId=2714320D-C997-4DE1-986F-24F081725D36&displaylang=en

Run the installer and accept the license agreement:

Now you’re ready to install the BES Express software.

Installing the BlackBerry Enterprise Server Express software

LOG INTO THE BES EXPRESS SERVER AS THE BESADMIN USER!

Launch the BES Express installer, you will be prompted to confirm that you are indeed logged in as the correct user:

Click Continue Installation:

Choose your country and read the license agreement. Select the option to accept if you agree to the terms and conditions:

Select the option to Create a BlackBerry Configuration Database:

Select the option to install a BlackBerry Enterprise Server:

Verify that all pre-requisite checks are completed successfully, paying attention to any warnings or failures:

In this article I am allowing the BES Express installer to install a local copy of SQL Server Express, if you intend to use a dedicated SQL Server, select this option and enter the details of the server address:

Enter the password for the BesAdmin account and enter in a name for the BES Express server: this name can be a ‘friendly’ one and is used to identify it in the Web Administration interface:

If you are warned that the server does not have sufficient free disk space available, free up some space before continuing:

A summary of the installation options will be displayed:

Click Install, the required components will now be installed, this process may take a while. When complete you will be prompted to reboot the server:

Click Yes. Once rebooted, log back in as the BesAdmin user. The installation will resume automatically:

Enter a name for the Configuration Database – this should ideally be left at the default unless specifically required. Click Next:

You will be prompted to create the database, click Yes:

When created, click OK:

Enter in the 10,000-user CAL, SRP key and SRP authentification key you were supplied along with the BES Express download. Verify connectivity to the RIM Relay on TCP port 3101. Click Next:

The MAPI connection settings will now be required, enter in the name of the Exchange server as well as the BesAdmin user account mailbox. Click OK:

Enter in the name you wish to use for the Administration web site. Again this should be left at the default if you are unsure as to what this means. Any name you choose should be resolvable via DNS if not using the default option.

Enter in a password for the SSL certificate – this is generated automatically by the installer and assigned to the Apache-based administration web site (the site does not run within IIS). The certificate is generated based on the name entered.

By default the administration web site runs on port 3443 – this can be altered if desired but again leave this value at the default unless specifically required. Click Next:

Enter in the details of the BesAdmin user account again and click Next:

Specify whether you wish access to the administration web site to be authenticated based on Active Directory credentials, or whether you want to use the built-in BlackBerry Administration Service authentication. If you select the second option, enter in a password for the default admin account.

NOTE – if you select BlackBerry Administration Service authentication, the default admin username is “ADMIN”, NOT “BESADMIN”.

Click Next:

Select the option to Start Services and verify that all services start successfully:

Click Next:

You will be reminded what the address is to access the administration web site. Click Finish.

The software is now installed and ready to use. To access the web administration site, a link will have been added to the Programs folder on the Start menu:

Selecting the link will launch the default browser on the server (which needs to be Internet Explorer 6 or later):

Log in ether as the BesAdmin user (using Windows authentication) or as the Admin user (using BlackBerry authentication):

Add the web site to the Trusted Sites group in the Internet Explorer security options area:

And add the web site certificate to the trusted certificate authority folder:

Adding Users

In the Administration web site, select the option to Create a user:

Selecting Search will display a list of all available users:

Tick the user(s) you want to add and click Continue:

Select the BES Server the users should be added to (you’ll only have one option) and click Next. The users will now be added to the BES Server.

To associate a device to a user, the BlackBerry handheld itself can be connected directly to the BES Express server via USB. In the Administration web site browse to Devices –> Attached Devices –> Overview:

When the device is connected, its PIN details will be displayed:

Select the option to Assign current device to a user. Select the user you want to associate the device with:

The device will now be associated to the user and will automatically activate itself and begin to download user mailbox data.

Troubleshooting

If you encounter any problems adding or activating users, first verify that all BlackBerry services have started and are running correctly:

Exchange Permissions

The commonest cause of problems when troubleshooting issues with a BES installation is that the correct permissions have not been assigned to the BesAdmin user on the domain and the Exchange server as detailed above.

Included with the BES Express software is a utility called “IEMSTEST” which can verify the BesAdmin user’s access to specific user mailboxes.

The utility lives in the C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility folder and needs to be run at the command line:

Select the BlackBerryServer MAPI profile when prompted:

Select the user account you wish to query:

The permissions will be tested:

As you can see from the above screenshot this test has indicated that the BesAdmin account does not have Send As rights on my James Liddiard user account. Once I verify my permissions, re-running the test indicates that all test have passed successfully:

‘Fatal error C0000034’ on boot after Service Pack 1 for 64-bit systems install

After Installing Windows 7 Service Pack 1 for 64-bit systems on my laptop after it appeared on Windows Update. The install seemed to go alright, however, when I restarted the computer at the prompt of Windows Update, it gets as far as the Starting Windows screen, before throwing ‘Fatal Error C0000034 applying update operation 282 of 114599 (_00000…)’

At this point, the start-up sequence hangs and go’s no further. I restarted again by switching off at the mains, and this time was prompted to run Start-up Repair. I tried this, however the Start-up Repair program hung (I left it for several hours with apparently no effect). I then proceeded to try the following things:

-Boot in Safe Mode
This led to the start-up to hang at the ‘Loaded: CLASSPNP.SYS’, ‘Please wait…’ stage. Again, left for several hours, no progress.

– Run the recovery CD to restore from a System Restore point.
The program hung at the restoring system stage – again, left for several hours, nothing happens.

– Booting from last known good configuration
This just resulted in the same error as when I boot it normally

The Following is how to fix this issue.

It essentially involves doing a manual system restore.

– Open the recovery console – To get to the Windows 7 recovery Console Press F8 at system restart before it trys to load Windows, and you are presented with the following menu:

When the recovery console has loaded select Command Prompt from the menu options:

When the command prompt is open complete the following:

– Change working directory to whatever the root folder of the Windows install is (might be D: or some other letter for some people):
cd /d C:\windows\system32\config

Rename the following files by typing the following:

ren default default.old
ren sam sam.old
ren security security.old
ren software software.old
ren system system.old
– Change the working directory:
cd regback
– Copy the files from this directory to the previous directory as follows:
copy default c:\windows\system32\config
copy sam c:\windows\system32\config
copy security c:\windows\system32\config
copy software c:\windows\system32\config
copy system c:\windows\system32\config

– Having done this, I restarted my computer, and it booted all the way with no errors. However, it seemed somewhat unstable, so I booted into Safe Mode and ran CHKDSK (chkdsk /B) and conducted a normal system restore to before the service pack install using the normal method. To fix remaining problems, I ran sfc /scannow. My computer now seems to be running as well as ever.

 

I am trying to perform a database attach upgrade to SharePoint Foundation 2010.

At this point I am trying to attach the content database to a Web application by using Windows Powershell:

Mount-SPContentDatabase -Name -DatabaseServer -WebApplication [-Updateuserexperience]

I am following the directions from this TechNet article: Attach databases and upgrade to SharePoint Foundation 2010.  When I go to mount the content database I am receiving this error:

Mount-SPContentDatabase : Could not connect to [DATABASE_SERVER] using integrated security: SQL server at [DATABASE_SERVER] has an unsupported version 10.0.2531.0. Please refer to “http://go.microsoft.com/fwlink/?LinkId=165761” for information on the minimum required SQL Server versions and how to download them.

At first this did not make sense because the default SharePoint Foundation 2010 website was running just fine.  But then I realized that the default SharePoint Foundation site runs off of SQL Server Express and that I had just installed SQL Server Web Edition (since the database is greater than 4GB) and restored the database to this version of SQL Server.

Checking the documentation link above I see that SharePoint Server 2010 requires a 64-bit edition of SQL Server with the minimum required SQL Server versions as follows:

SQL Server 2008 Express Edition Service Pack 1, version number 10.0.2531

SQL Server 2005 Service Pack 3 cumulative update package 3, version number 9.00.4220.00

SQL Server 2008 Service Pack 1 cumulative update package 2, version number 10.00.2714.00

The version of SQL Server 2008 Web Edition with Service Pack 1 (the version I installed on this machine) is 10.0.2531.0.

SELECT @@VERSION:
Microsoft SQL Server 2008 (SP1) – 10.0.2531.0 (X64)   Mar 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation  Web Edition (64-bit) on Windows NT 6.1 (Build 7600: ) (VM)

But I had to read the article several times since the minimum version number for SQL Server Express is 10.0.2531.0.  At first I thought I was good with the version of SQL Server 2008 Web that I had installed, also 10.0.2531.0.  But then I read further to see that there is a cumulative update (hotfix) for SQL Server 2008 SP1 (NOT the Express edition) that is required for SharePoint 2010 and will bump the version number to 10.0.2714.00.

So the solution was to install the Cumulative update package 2 for SQL Server 2008 Service Pack 1 on my SQL Server 2008 Standard Edition to allow SharePoint 2010 to work with SQL Server 2008 (other than the SQL Server 2008 Express version).

SELECT @@VERSION (After installing Cumulative update package 2):
Microsoft SQL Server 2008 (SP1) – 10.0.2714.0 (X64)   May 14 2009 16:08:52   Copyright (c) 1988-2008 Microsoft Corporation  Web Edition (64-bit) on Windows NT 6.1 (Build 7600: ) (VM)

 

SharePoint Server 2010, like its predecessors, includes indexing and search capabilities. But what doesn’t come out of the box is the ability to index and search for PDF documents. PDF is a format owned by Adobe, not Microsoft. If you want to be able to find Adobe PDF documents, or have the PDF icon appear when viewing PDF files in a SharePoint document library (see image above), you will need to set it up for yourself. This post describes how to.

1. Download and install Adobe’s 64-bit PDF iFilter*¹ – http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025
   
2. Download the Adobe PDF icon (select Small 17 x 17) – http://www.adobe.com/misc/linking.html
   1. Give the icon a name or accept the default: ‘pdficon_small.gif’
   2. Save the icon (or copy to) C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES
3. Edit the DOCICON.XML file to include the PDF icon
   1. In Windows Explorer, navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML
   2. Edit the DOCICON.XML file (I open it in NotePad, you can also use the built-in XML Editor)
   3. Ignore the section and scroll down to the section of the file
   4. Within the section, insert attribute. The easiest way is to copy an existing one – I usually just copy the line that starts <Mapping Key=”png”… and replace the parameters for Key and Value (see image below)
   5. Save and close the file
      
4. Add PDF to the list of supported file types within SharePoint
   1. In the web browser, open SharePoint Central Administration
   2. Under Application Management, click on Manage service applications
   3. Scroll down the list of service apps and click on Search Service Application
   4. Within the Search Administration dashboard, in the sidebar on the left, click File Types
   5. Click ‘New File Type’ and enter PDF in the File extension box. Click OK
   6. Scroll down the list of file types and check that PDF is now listed and displaying the pdf icon.
   7. Close the web browser
5. Stop and restart Internet Information Server (IIS)*² Note: this will temporarily take SharePoint offline. Open a command line (Start – Run – enter ‘cmd’) and type ‘iisreset’
6. Perform a full crawl of your index. Note: An incremental crawl is not sufficient when you have added a new file type. SharePoint only indexes file names with the extensions listed under File Types and ignores everything else. When you add a new file type, you then have to perform a full crawl to forcibly identify all files with the now relevant file extension.

That’s it. If you now perform a search, PDF files should be displayed in results where they match the search query, along with the PDF icon on display in results. The icon should also be visible in any document libraries that contain PDF files.

 

PROBLEM !!! – What Problem

I am using SharePoint 2010 server.

I tried to uploaded documents to SharePoint my site Shared Document Library, and got the following error,

Your changes could not be saved because this SharePoint Web site has exceeded the storage quota limit.
You must save your work to another location.  Contact your administrator to change the quota limits for the Web site. 

I run SharePoint Central Administration Tool, selected the web application from the dropdown listbox,  I changed the Quota limit, created Quota template, assigned the new Quota template. But no matter what I did, It seems the quota did not changed

When I go back to my site I still getting the above error. Anyone can tell me what I did wrong?

Fortunately there is a FREE and very useful tool from CodePlex that will take the pain away from managing Quotas on Mysite….. the tool looks like this:

Application for change user profile site disk quota, if you have too much my site web.

Because SharePoint implicitly cannot change my site quota templates for all my site web at once, you can use this applications.

This project is beta version. You can read more on this blogs.

There are three requirements before you publish:

– Run only on server with SharePoint Portal Server 2007 / 2010
– Run under SharePoint Farm system account

To Download the tools go to the following link: http://spmysitequota.codeplex.com/

or if you like the STSADM tool try the following command:

stsadm -o gl-syncquotas -scope webapplication -url http://mysites -quota “Personal Site” –setquota

 

STSADM is a SharePoint administrative tool which generally resides in the  “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN” folder within the SharePoint 2007 environment and in the “C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN” folder in a SharePoint 2010 environment.

This tool is to be run on the same server of SharePoint by people who are member of Administrators group. In this section we are going to see how this tool can be used to export a site, library or list and import it back when required. These are the general command formats to export a site, library or list and import it back:

stsadm -o Export -URL -Filename -Quiet -Overwrite
stsadm -o Import -URL -Filename -Quiet

The Overwrite switch is required to overwrite a file if it is already existing on the specified location during an export operation whereas the Quiet switch is used to suppress the detail messages generated on the screen during the command execution. Similar to PowerShell cmdlets, you can specify the parameters for including security related detail and all the versions of the documents or lists with the STSADM tool as well. To learn about complete syntax, click here.

The first command, given below, will export the contents of all sites of the specified site collection.

The second command will export the contents of the specified site only.

TThe third command will export the content of the Shared Documents library of the specified site.

stsadm -o Export -URL http://mktaraliw2k8r2:8081 -Filename \\MKTARALIW2K8R2\SharePointBackupFolder\STAllSites.cmp -Overwrite -Quiet
stsadm -o Export -URL http://mktaraliw2k8r2:8081/hr -Filename \\MKTARALIW2K8R2\SharePointBackupFolder\STHRSite.cmp -Overwrite -Quiet
stsadm -o Export -URL “http://mktaraliw2k8r2:8081/hr/Shared Documents” -Filename \\MKTARALIW2K8R2\SharePointBackupFolder\STSharedDocuments.cmp -Overwrite -Quiet

The first command, given below, will import contents of all sites available in the exported file to the specified site collection.

The second command will import the contents to the specified site, and in this case the site must exist and the contents will be overwritten.

The third command will import the content to the specified site and document library, in this case the contents of the specified library will be overwritten.

stsadm -o Import -URL http://mktaraliw2k8r2:8081 -Filename \\MKTARALIW2K8R2\SharePointBackupFolder\STAllSites.cmp -Quiet
stsadm -o Import -URL http://mktaraliw2k8r2:8081/hr -Filename \\MKTARALIW2K8R2\SharePointBackupFolder\STHRSite.cmp -Quiet
stsadm -o Import -URL “http://mktaraliw2k8r2:8081/hr&#8221; -Filename \\MKTARALIW2K8R2\SharePointBackupFolder\STSharedDocuments.cmp -Quiet

Notes

• While you can still use the old STSADM tool to perform content export and import, it is recommended not to use this tool (unless you are forced to use it for backward compatibility) as this tool has been deprecated and provided in SharePoint 2010 only for backward compatibility.
• The SharePoint 2010 Central Administration UI provides a way to export a site, library or list but not for importing it back. You need to use PowerShell cmdlets or old STSADM tool for importing it back.
• A log file gets created after an export and import operation (with this name : .export during export and .import during import), which contains all the details about the operation execution.
• The granular backup/export and restore/import operations are more processing and read-intensive, as it uses Transact-SQL queries as opposed to farm backup.
• If your SQL Server version supports database snapshot (Enterprise and Developer editions) , it is recommended to use UseSqlSnapshot parameter with Export-SPWeb command for a more consistent backup.
• Workflows are not included when we export/import contents of sites, libraries, or lists.

In outlook 2010, the .nk2 file is replaced by Suggested Contacts.

To import .nk2 files into Outlook 2010, follow these steps:

1. Make sure that the .nk2 file is in the following folder:
%appdata%\Microsoft\Outlook

Note The .nk2 file must have the same name as your current Outlook 2010 profile. By default, the profile name is “Outlook.” To check the profile name, follow these steps:

a. Click Start, and then click Control Panel.
b. Double-click Mail.
c. In the Mail Setup dialog box, click Show Profiles.
2. Click Start, and then click Run.
3. In the Open box, type outlook.exe /importnk2, and then click OK. This should import the .nk2 file into the Outlook 2010 profile.

Note After you import the .nk2 file, the contents of the file are merged into the existing nickname cache that is currently stored in your mailbox.

After the import is finished the .nk2 gets renamed with an . file name extension on the first start of Outlook 2010. Therefore, if you try to re-import the .nk2 file, remove the . file name extension.