#PowerShell #SCOM Preserve/Update Created By/Modified By

This example shows how to use SharePoint Client Object API through PowerShell to create a list item with specific Author and Editor. Useful if you want to preserve identities while moving the SharePoint items. $siteUrl = “http://mysite&#8221; $listTitle = “My List” $user = “9;#domain\user” cd “$installFolder” Add-Type -Path .<PATH>\Microsoft.SharePoint.Client.dll $ctx = new-object Microsoft.SharePoint.Client.ClientContext($siteUrl) $web =

Enable SQL protocol by using PowerShell

A stand-alone installation of SharePoint usually utilizes SQL Server Express. The instance name is SHAREPOINT. (This is true for SharePoint 2013). You must enable TCP protocol to access the SharePoint back-end. PS> function EnableSQLProtocol($instance, $proto) { [reflection.assembly]::LoadWithPartialName(“Microsoft.SqlServer.Smo”) | out-null [reflection.assembly]::LoadWithPartialName(“Microsoft.SqlServer.SqlWmiManagement”) | out-null $smo = ‘Microsoft.SqlServer.Management.Smo.’ $wmi = new-object ($smo + ‘Wmi.ManagedComputer’). $uri = “ManagedComputer[@Name=’$(hostname)’]/ServerInstance[@Name=’$instance’]/ServerProtocol[@Name=’$proto’]” $p

SharePoint 2013 on Windows Azure VM five times more expensive than on AWS instance

Something wrong with Windows Azure! I decided to run a SharePoint 2013 on Windows Azure. Just to give Azure a chance;) But! What is going on there? Does someone really use it? SharePoint 2013 requires minimum 8GB of RAM. AWS $0.066 Azure $0.32