New answers tagged

0

What kind of performance issue you are seeing, did you check your 2013 farm, i.e ram usages, database performance, are u using the Cache i.e object cache? There are many things which can cause the upgrade Performance issue. Orphan items /List/ Sites Orphan Users and others Cache Settings Solution / Customization deployed in 2007( not compatibile to 2013) ...


0

I think the above link is fixed now, I tried to download it and it take me to the download page and once i enter the required information, within 5 min, I get the download link in the email. this link See the link. If you still getting the error, try from different computer.


0

You can download the same CU from below mentioned link. As I am able to download it from this link. December 9, 2014 Cumulative Update for SharePoint Server 2013 package Important notes about the cumulative update package The Microsoft Office 2013 hotfixes are now multilingual. This cumulative update package contains updates for all languages. This ...


-1

The use of XSLT has been replaced by Display Templates in SharePoint 2013. This means almost all your branded Web Parts, Content Query styles will no longer work after migrating to SharePoint 2013.


0

Even the XSLT feature deprecated in SharePoint 2013 but still has Backward compatibility. But your testing will prove it. Check this post for more information


2

If you migrate content only with the tool, yes you might bypass the warning messages you get when doing a database attach migration. You may still encounter problems depending on what these customizations did. In our experience with using a third party tool to go from 2010 to SPO, all of the customizations we knew of were not carried over (obviously) and ...


-1

SharePoint 2013 has a new configuration option called "licensing". You can enable and disable license-depended features for a group of users. My Idea: Install your SharePoint 2013 environment with an Enterprise License key. Enable licensing via PowerShell. Assign only Standard-Licenses to your users Migrate your content database according to Microsoft's ...


2

It is a site collection level feature so you can not do it on site-level. Site Collection Upgrade: One the benefits of upgrading to SharePoint 2013 is that it all happens behind the scenes. This means that your site collection administrators can upgrade the look and feel – not to mention, handle the change management – on their own ...


1

This is not an easy job as it is not supported path of Migration. In your situation, I highly recommend using the 3rd party tools(ShareGate, Metalogix etc). Another Option, I am thinking( complex, required a lot of work). Build a new 2010 std farm. Deactivate ent features from current 2010 farm detach Content Db from Prod 2010 and attach to 2010 Std ...


1

You can not directly upgrade from SharePoint 2010 Enterprise to SharePoint 2013 Standard as mentioned in MSDN link given below. Please find table under Supported editions for upgrade in below given link. Review supported editions and products for upgrading to SharePoint 2013 If you want to upgrade from SharePoint 2010 to SharePoint 2013 than please follow ...


1

Sharepoint 2010 to SharePoint 2013 inplace upgrade is not supported. I'd try to carve out a separate server for the time being in order to install SharePoint 2013 and pull over your content databases after you create a farm. https://technet.microsoft.com/en-us/library/ee617150.aspx?f=255&MSPPError=-2147217396


0

Might be long back you have asked this but future reference purpose, I had same issue couple of weeks back, turned out to be that I had more than 20 sub sites. To resolve change the default "Maximum number of dynamic items to show within this level of navigation:" to 30 on the site collection. This worked for me. Had same issue for me. Try this. For me this ...



Top 50 recent answers are included