CheckIn Documents Using Powershell
Virtual Migration Environment for Project Server 2010
The Virtual Migration Environment (VME) Guide for Project Server 2010 is available in Microsoft TechNet. The VME is a virtual Project Server 2007 migration environment that can be restored to a virtual machine in Hyper-V Manager in Windows Server 2008 R2. This guide describes how to use the VME to migrate your Project Server 2003 data to Project Server 2007, which is required for upgrading your data to Project Server 2010. This guide provides the following information:
- Overview of the VME
- How to restore and configure the VME on a virtual machine
- Pre-migration tasks
- Migration tasks
- Post-migration tasks
- How to plan to upgrade your data to Project Server 2010 after completing the migration on the VME
The VME also provides useful migration scripts that can assist you in the migration process.
The VME image is available for download from the Project Server Virtual Migration Environment download package page in the Microsoft Download Center.
Lightening Conductor 2010 Express Web Part - SharePoint 2010
PDF for SharePoint 2010
•Convert Microsoft Office files to PDF
•OCR (Optical Character Recognition) scanned document images to make them text-searchable
•Combine multiple documents with table of contents, indexes, page numbers, watermarks and timestamps
•Rapidly deploy using out of the box rendering workflows
•Create flexible document transformation business processes based on metadata
Webinar: Go with the Workflow: PDF for SharePoint 2010 from Adlib Software on Vimeo.
List Bulk Import
- Import both metadata properties and attached documents.
- Allow users to map fields between source and destination lists.
- Provide value mapping for choice and lookup fields (i.e. source:Yes = destination:True).
- Import Excel, CSV or text delimited files.
- Import data into existing lists that already have data.
- Check for duplicate existing records, then skip the duplicated record or update with new data.
- Works with many lists including Document and Picture Libraries.
- Automatically import sub folders and create same hierarchy in the target document library.
- The ability to automatically rename files to avoid overwriting of existing files.
- Import parameters can be saved and re-used for subsequent import runs.
- Option to run in the background with scheduled intervals.
- Post-import log file provides summary of success and failure records.
- Import one SharePoint list to another, even across sites, and from MOSS/WSS v3 to SharePoint Server 2010/Foundation 2010.
- Import data from a database table or view into a SharePoint list.
- Import versions of Issues Lists and Document Libraries.
- Import files from network folders into SharePoint Document and Pictures Libraries.
- Supports ASP.NET 2.0.
- The Bamboo Attachments Clean Up Application allows you to automatically clean up attachments that are deleted during a normal import update process. Primarily for those users using Bulk Import as a syncing tool, this application moves them from the primary recycle bin to the secondary recycle bin, keeping your database from growing due to large deleted items.
- Now supports importing from MOSS/WSS 3 to SharePoint Server 2010/SharePoint Foundation 2010.
- Now supports import to and from Hyperlink (URL and Description) and Image column types.
- Automatically empty the SharePoint list you are importing to before importing.
- http://store.bamboosolutions.com/sharepoint-list-bulk-import.aspx
Common Engineering Criteria Scorecards
Microsoft server products comply with the common engineering criteria.
Scorecards report each server product’s compliance status for the established common engineering criteria.
8 Features in SharePoint 2010
1 -- Business Connectivity Services.
The Business Connectivity Services (BCS) used to be called the Business Data Catalog (BDC). It provides access to your external data sources such as databases, external business systems and web services. Using BCS, External Content Types can be created that allow read/write access back to the external data sources. External lists, which operate much like normal lists can be created in SharePoint from these External Content Types so you can have access to these external systems right inside of SharePoint.
Client applications such as office or third party applications can also connect to the external data source using the ECT without writing any proprietary code. There is also an offline caching mechanism, to enable offline access to External Content Types.
2 -- List Validations.
List validations are a very powerful way to validate not just documents but any content before it goes into a list. This feature improves column property entry, which in the Document Imaging is called indexing or in the collaboration world, often called tagging. List Validations were very limited in SharePoint 2007, but have major improvements in SharePoint 2010 that can be leveraged:
- Hidden Columns – This setting is unique per content type, not just by the site column, which makes is very granular.
- No Duplicate Values – This will enable lists to act like databases, forcing items to be unique.
- Column Validations – Column validations will force column data to meet conditions before content is added to SharePoint.
3 -- Enterprise Managed Metadata.
The Enterprise Managed Metadata Service allows you to centrally define taxonomies that can be leveraged across farms to quickly classify and find content. There are two main features of the service, the first being the ability to publish content types to other site collections and farms and the other being the taxonomy term store.
The Taxonomy Term Store allows two new columns to be used in lists. The first being terms allows a static list to be created and used to validate during data entry. The second is managed keywords, which allows freeform entry of multiple values using existing keywords as suggestions.
4 -- Search.
Search has certainly evolved since SharePoint Portal Server 2003 as the scalability of the architecture has improved. You can have multiple index servers and index partitions can represent a portion of the index and live on the query server. Partitions can be spread across multiple query servers but can also exist on multiple query servers for redundancy and load balancing. SharePoint 2010 can scale to 100 million documents and FAST search will take us beyond 100 million!
5 -- Remote Blob Storage.
External BLOB Storage (EBS) has evolved into Remote Blob Storage (RBS), and helps provide a more scalable architecture. RBS allows BLOBS (documents) to be stored in external systems in order to keep the database size smaller and more manageable. Transactional consistency allows for update capabilities and allows Write Once Read Many (WORM) mode devices to deny a delete or modify operation. RBS is completely transparent to the SharePoint API so existing custom and third party code will continue to function as expected.
6 -- Audit Trail.
Audit trails are not just for workflow anymore as they were in SharePoint 2007. The audit trail functionality applies to most events pertaining to documents and it is extensible. The audit trail can be used to track all scanning events so documents will have a consistent audit trail from the moment of capture until they are archived.
7 -- Document IDs.
Document IDs is a new capability that assigns a unique identification number to a document. It is embedded with a special URL and can be used to retrieve a document regardless of where it is moved within a site collection. This is very useful because in many third party scenarios it was very difficult to create links to documents as there was no permanent ID attached to content in SharePoint unless you added the data yourself or used searching scenarios.
8 -- Document Sets.
A Document Set enables grouping of documents belonging to a workflow, project or other similar group together into a single working set. Document sets allow these documents to have one consistent set of meta data, can be downloaded as single ZIP file and can be work flowed as one unit.
SharePoint 2010 PowerShell Commands
1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell
Note : You should have SharePoint_Shell_Access role on the configuration database and you should be a member of the WSS_ADMIN_WPG local group on the computer where SharePoint Server 2010 is installed.
Some of the Common Commands and Operations are:
Create Web Application Variable
$webapp = Get-SPWebApplication "http://WebapplicationUrl"
Create SharePoint Site Variable (Instance of SPSite)
$siteurl = "http://MySharePointSite"
$Oursite=new-object Microsoft.SharePoint.SPSite($siteurl)
Here we have created a variable Oursite, which contains an instance of type SPSite. Now you can use it to display all webs in the site collection.
$Oursite.AllWebs more // List all Webs in the Site
Create Service Application Variable
$spapp = Get-SPServiceApplication -Name "ServiceApplicationDisplayName"
Create a Webapplication:
New -SPWebApplication -ApplicationPoolName
Delete WebApplication
Remove-SPWebApplication –identity -URL
Create\Delete a Site Collection:
Create a Site collection:
Get-SPWebTemplate
$template = Get-SPWebTemplate "STS#0"
New-SPSite –Url "
Here $template is a Variable to store the type of template we want to use while creating a site collection.
Delete a Site Collection:
Remove-SPSite –Identity
Here
Back\Restore a content database
To Backup :
Backup -SPFarm -Directory
Backup folder - is a folder to save your backup.
BackupMethod – Can Specify between Full or Differential.
To Restore:
Restore -SPFarm -Directory
If you don’t know the BackupID you can display all the backups using the below command and get the GUID of the Backup.
Get-SPBackupHistory -Directory
You can check all the Backup-Restore Operations Here
Deploy WebPart Soluiton Package
Install -SPWebPartPack -LiteralPath "PathToCABorwspFile" -Name "NameOFWebPart"
PathToCABorwspFile- is the full path to the CAB file that is being deployed.
NameOFWebPart- is the name of the Web Part that is being deployed.
Install Activate and Deactivate Feature using Windows Powershell
Install Feature :
$MyFeatureId = $(Get -SPFeature -limit all where {$_.displayname -eq "myfeatureName"}).Id
Install -SPFeature $MyFeatureId
Activate\Enable Feature :
$singleSiteCollection = Get -SPSite -Identity http://MySingleSiteCollectionURL
Enable -SPFeature $MyFeatureId -Url $singleSiteCollection.URL
Deactivate\Disable Feature :
$singleSiteCollection = Get-SPSite -Identity http://MySingleSiteCollectionURL
Disable -SPFeature $MyFeatureId -Url $singleSiteCollection.URL
Command TO List all the PowerShell Commands
Get-Command –PSSnapin “Get-Command –PSSnapin “Microsoft.SharePoint.PowerShell” format-table name > C:\SP2010_PowerShell_Commands.txt
Permission to embed a Webpart or any Custom Solution
PowerShell Location
PowerShell Script to Deploy Components in SharePoint
Cmdlets
Differenciate - PowerShell & STSADM
Windows PowerShell
Export a Site or List in SharePoint 2010
Through Central Administration(Granular level Back-up) a SharePoint Administrator can configure a backup of a subsite or list. An Administrator can choose a site and a specific list to be exported.The administrators can also choose to export security and select the different versions that will be exported with the list.
Methods of Backup and Recovery in SharePoint 2010
SharePoint Server 2010 uses two different tools to configure backup and recovery.
1. Central Administration : Central Administration provides a user interface where SharePoint Administrators will be prompted via menu structures to select the information that needs to be backed up. (see the Image below)
2. Windows PowerShell : Windows PowerShell is a command line tool that provides SharePoint administrators a way to perform backup and recovery with additional options such as file compression or working with SQL snapshots.
Posts
