Tag Info

New answers tagged

1

You need to make sure the web applications and customizations are in place before you mount the content database to the web application. The full process is described in the article Upgrade content databases to SharePoint 2013: Create Web Applciations Create a web application for each web application that existed in the SharePoint 2010 Products ...


0

I dont see any impact /side effect on SSRS while Updating the SharePoint farm to SP1. But the only way you can see any potential issue you have to apply the CU in lower farm(test/dev) first, then test it. I would recommend move the production data in dev farm and then apply the CU and do the testing. This will give you maximum comfort.


1

This involves first upgrading Secure Store Service Application and then upgrading Business Data Connectivity Service Application You can follow steps outlined in this article https://technet.microsoft.com/en-us/library/jj839719.aspx


0

In the process of migrations from 2010 to 2013, you need to apply configuration and customizations on the web app before you mount the 2010 content database. That means you need to add and install the solution containing the site definition (stp). You can always extract the wsp from your 2010 farm and try to deploy it in 2013. From my experience it usually ...


0

Move current Web app to our NEW SharePoint server (the same version 2007 with current server) to prepare for upgrade process? Yes! If you have created a backup and restored the entire farm with its service applications, you are on your way to backup restore and restore web applications. See Back up and restore Web applications by using built-in tools ...


1

Yes you need the November CU after installing the LPs Because CU contains the fixes for Language packs and it update the language related files as well. Their is no separate CU for language packs, Only SP1 are separated. So, when you running the Nov CU then you dont need to worry about the override thing. Language Pack for SharePoint 2013 with SP1 (DE) ...


0

I am sure no 3rd party tool supporting the custom solution migration. 3rd party tools help to directly move the content from 2007 to 2013(almost all OOTB stuff). Now you have two options. Option # 1 Re do your custom code in Visual studio and compile it as per the 2013. Use the tool to move the content Option # 2 (Dont use the 3rd party tool) You ...



Top 50 recent answers are included