$webapps = Get-SPWebApplication foreach($app in $webapps) { $siteCollections = $app.Sites
foreach($sc in $siteCollections) { $loc="c:\Backups_sitecolls\"+$sc.Url.Substring(7).Replace(':','')+".bak"; $loc=$loc.Replace('/','_'); "backing up " + $sc.Url Backup-SPSite -Identity $sc.Url -Path $loc -Confirm -Force -NoSiteLock
} }
This script clears the http:// section of url and replaces and replaces / with _ in the file name of site collection.
This needs a folder "c:\Backups_sitecolls\".
Replace : before port number with empty character.
I assume that you all know that all the list items can be retrieved from SharePoint List using
SPList.getItems(SPQuery)
And returns all the items based on user permission and Filter that were specified in query. The columns that it return by default (For a document library) are
FileLeafRef Title ID ContentType Created Modified _CopySource _CheckinComment LinkFileNameNoMenu LinkFilename DocIcon FileSizeDisplay ItemChildCount FolderChildCount Edit _UIVersionString ParentVersionString ParentLeafName CheckoutUser Editor
And Author.
The reason why i mentioned Author separately is because GetItems() method return Author Filed only for SiteCollection Admins and application pool admins.
Regual user like site administrator, modifiers, visitors will not get that column.
If you are trying to get datatable from GetItems() method and use a custom column that shows Author (created By) column make sure to user elevated privileges based on your need.
If any one of have problem compiling the SharePoint 2010 Workflow (Sequential and State Machine) in you Dev Server. And if the Error is this
Even for the empty workflow its giving this error.
Error1The "CompileWorkflowTask" task failed unexpectedly. System.NotSupportedException: The given path's format is not supported. at System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean needFullPath) at System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[] str, Boolean needFullPath) at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList) at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath) at System.IO.Path.GetFullPath(String path) at System.CodeDom.Compiler.TempFileCollection.EnsureTempNameCreated() at System.CodeDom.Compiler.TempFileCollection.AddExtension(String fileExtension, Boolean keepFile) at System.Workflow.ComponentModel.Compiler.CompileWorkflowTask.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Boolean& taskResult)stateWorkflow1
Two days back i got access to my Office 365 SharePoint site. It is so amazing. I am really excited with this new cloud computing feature. I started using it for my new business.
However it has a drawback. That is, lack of a feature which i expected to have. That is Incoming Email for Lists and Libraries.
Hi all,
I found a new Microsoft artcile to find out different way to Migrate/Upgrade WSS3.0 to SharePoint Foundation 2010. This is very helpful take a look at it.
Please follow this link: http://www.sharepointproconnections.com/article/sharepoint-server-2010/Eric-Swift-on-SharePoint-2010-s-Value-for-Developers-and-Admins.aspx
SharePoint 2010 has a new feature for grouping and managing documents, called Document Sets. We have all experienced a need to work with a “group” of documents. When a company hires a new employee, there are ususally dozens of forms that need to be filled out – hence a New Employee Document Set. The challenge is that prior to this version of SharePoint there was no way to keep track of the documents together other than metadata. It acts like a folder, but is not a folder. It is a container however, and that container can have policies, workflows, metadata that applies to the entire set of documents within the container. Let’s use the example of the New Hire process. When a new employee starts working for your company they have to fill out their standard forms, Personal Information, Emergency Contact, W-2, etc. Instead of emailing the employee the documents and then have them exchange emails back and forth, you can use Document Sets to collect all the documents, display the review status for each of the document, create a nice Welcome Page that summarizes what the document set is about, and even use a workflow to streamline the review process. This eliminates the frequently asked question of “Is this the latest version?”, “Is this the right information?”, “Is this complete?”. You Should Know There is no limit on the number of documents that can exist in a Document Set. Metadata can be shared across the Document Set. Document Sets are based on Content Types. Docment Sets can be versioned. Workflows can be associated with the Document Set. Permissions can be defined per Document Set. Folders are not allowed in document sets. Metadata navigation cannot be used in a Document Set. To get a better understanding, here’s a great video.
