Showing posts with label Version. Show all posts
Showing posts with label Version. Show all posts

Sunday 20 April 2014

Backup and Restore Site Collection in SP2013

Overview:  I have seen several customers us Backup and restore to help speed up the development process and have the ability to deploy between DTAP environments.  So the basic premise is create the site collection on dev/a and use backup and restore to promote the site collection including customisations and code in the next environment.

SharePoint 2010:  In SP2010 this worked assuming the env you are going to has a higher patch level than the source environment.  So if you went from SP2010 + cu to SP2010 + SP1 in production backing up and restoring the site collection works.  The trick was to package all assets into the site collection and to ensure all environments were on the same edition/patch level (or at least the destination farm was patched to a higher level than the source farm).

SP2013:  You can use PS backup and restore to move site collections but it is further restricted.  The source and destination environment need to be the same edition.  My issue is I can't move a troublesome production environment back to UAT as my UAT has been patched and is a later/newer version of SP2013 on prem.

I learnt this when restoring the site collection from 15.0.4481.1005 (SP2013 + Mar CU) on the source and trying to go to 15.0.4569.1000 (SP203 + SP1) y destination farm.

Restore-SPSite : 0x80070003
At C:\Users\SP_install\AppData\Local\Temp\5ae5fd1c-86ac-4032-8975-c739f39b6f36.ps1:3 char:1
+ Restore-SPSite –Identity "http://uat.futurerailway.org" –path "C:\Software\Deplo ...
+ CategoryInfo : InvalidData: (Microsoft.Share...dletRestoreSite:SPCmdletRestoreSite) [Restore-SPSite], DirectoryNotFoundException + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletRestoreSite  

Conclusion:  To move Site collection between farms or to different content databases, the SP farms need to be using the exact same version of SP.

Tuesday 17 September 2013

Retrieveing Versions

Overview:  I repeatedly need to determine versions of software and patches so this post holds common requests to verify versions that I need.

.NET framework versions installed:
Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -recurse | Get-ItemProperty -name Version -EA 0 | Where { $_.PSChildName -match '^(?!S)\p{L}'} | Select PSChildName, Version


Version of Powershell on a machine:
$psversiontable.psversion



Version of your SharePoint farm:
 PS> (get-spfarm).buildversion

Version of Office Web Apps 2012/WCA:
The easiest way to get the OWA version is to make an http/https request to your WCA server and the version number is returned in the response header.
I use IE and fiddler so I can view the traffic to the url https://wca.demo.dev/m/met/particiapant.svc, you will get a 302, but your can see the version return in the https response header.
15.0.4481.1005 is WCA 2013 with the March 2013 CU.
15.0.4420.1017 is WCA 2013 RTM.

The approach below does not work:
PS>
((Get-ChildItem hklm:\software\microsoft\windows\currentversion\uninstall | Where-Object {$_.PSChildName -Like "*WacServer"}) | Get-ItemProperty).DisplayVersion

from http://blogs.technet.com/b/sammykailini/archive/2013/09/20/how-to-find-the-version-or-build-number-for-an-office-web-apps-2013-farm.aspx

It should show version 15.0.4481.1005 for me.  Note: I upgraded an original WCA RTM install.

A good PS approach:
 

Monday 20 February 2012

Determine SP2010 & SP2013 edition & patching Level

Problem: You go to a client to work o the farm and you need to know what the production farm is running i.e. SP2010 version and patching.  This also applied to moving data and features from QA to production.

Todd Klindt keeps a list of SP & OWA version numbers for SP2013.

Initial Hypothesis:  Use PowerShell to determine which edition of SP2010 is installed and the patching level.

Resolution:
PS> (get-spfarm).buildversion
PS> get-spfarm | select Products
OR Central Admin > System Settings > Servers on farm
Update 27 July 2013: Build 15.0.4481.1005 is SP2013 with the PU March 2013 (This PU is required before you install any subsequent CU's).  Build 15.0.4420.1017 is SP2013 without PU or CU's.
 
 
SP2013 with PU march 2013 and CU June 2013 shown below:
 
 
Product GUID Titles:
BEED1F75-C398-4447-AEF1-E66E1F0DF91E: SharePoint Foundation 2010
3FDFBCC8-B3E4-4482-91FA-122C6432805C: SharePoint Server 2010 Standard
D5595F62-449B-4061-B0B2-0CBAD410BB51: SharePoint Server 2010 Enterprise
B2C0B444-3914-4ACB-A0B8-7CF50A8F7AA0: SharePoint Server 2010 Standard Trial
88BED06D-8C6B-4E62-AB01-546D6005FE97: SharePoint Server 2010 Enterprise Trial
BC4C1C97-9013-4033-A0DD-9DC9E6D6C887: Search Server 2010 Trial
08460AA2-A176-442C-BDCA-26928704D80B: Search Server 2010
926E4E17-087B-47D1-8BD7-91A394BC6196: Office Web Companions 2010
Source: http://altamodatech.com/blogs/?p=405

Http header version unrelability post
PS script to check SQL and SharePoint. 
 
Reference List of SP2013 versions