Tag Info

New answers tagged

0

You need to use the Restore command instead of New. here are the steps i want to metnion: Backup the Search Service Application admin database from SharePoint 2010 environment and restore on SharePoint 2013 database server, preferably by the name as "Search Service Application_ AdminDB" Now, login to your SharePoint 2013 App server, and create the ...


0

From your question and comments we conclude that you are stuck from migrating SharePoint 2010 to SharePoint 2013 using Database Attach Upgrade Process. And you migrating your SharePoint to a new domain, since you mentioned this "(OldDomain\account1 -> newDomain\account1)". Now I would like you to check and go through these articles and perform the steps. ...


0

Typically developers don't clean up after themselves on feature deactivation as this can lead to a loss of data. Even Microsoft doesn't clean up after themselves when disabling Publishing features. If there are instances of the lists and libraries remaining, they should be deleted from the site(s) and those errors should go away.


0

You can remove the feature from Content Database, and then try upgrading Remove-SPFeatureFromContentDB -ContentDB "WSS_Content_Communities" -FeatureId "a5b72e0e-edbd-458d-8957-16f4653b5060"


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 ...


0

You cannot migrate directly a DB with RBS enabled, You have to move all the files inside the DB then you can use backup & restore method. The steps you need to follow are: Stop Content Db to use RBS and Move in all the Files inside the DB from Blob Folder. Verity that files are inside Sql DB by running query. Test by uploading file to Site and verify ...


0

In Office 365 customers are responsible for the content validation and functional testing. As you are moving from 2003 to SharePoint online(2013), which required to good test plan. So you should check the following things. Custom code that needs to be ported,Custom list templates, Custom site templates, Custom web parts Third-party web parts Feature ...


0

You need to concentrate on following Find the customization made on 2003 Find workflow's used Collect various data stored in the site. Business processes that are automated in 2003 Once you have this information you can test those in particular. Basically you can avoid testing SharePoint features like adding list items etc.


1

You can convert content database from classic authentication to claim authentication using below mentioned Poweshell commands. $wa = Get-SPWebApplication http://yourWebAppUrl $acc = 'domain\user' $arguments = New-Object Microsoft.SharePoint.Administration.SPWebApplication+SPMigrateUserParameters #based on scenario above, content DB 0 is the one that was ...


0

SharePoint 2013 uses App Model for development. So you need to take a decision what approach you should follow. Also SP 2013 encourages using CSOM as opposed to Farm Solutions. If you have only limited time, then I think you can directly deploy 2010 solution and test what functionality is breaking, then try to fix only that.


1

There is no OOTB/simple way to move the site collection in the Office 365. I am thinking two possible way. Option 1 You are able to manually save the sites as the templates and import to the new tenant as a workaround, it will not break the files and the structure in a site except the permissions.( One thing, if your site collections is publishing then you ...


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 ...


0

Great news: You can just create a new workflow and copy and paste all the steps from the old one to the new one. (This assumes you have the old and "new" workflows on the same version of SharePoint designer, likely). The workflow steps can be copied one stage at a time. As an additional note, it's best to start from the last stage and work your way back. ...


0

I'd build a new farm too. Update to the same patch level as used in the current farm. Enable the same services Use the same functional accounts Set database to read-only Copy to the new farm and attach them there After checking logs and everything works fine, change DNS to the IP-Address of the new farm/web frontend Simply copying the server images and ...


0

Moving the SharePoint farm from one domain to other, or moving from virtual to physical really not easy job. I would prefer the Backup and restore appraoch. Build a new farm, then restore the farm backup. Another approach is: Install SharePoint on the new physical app servers and update it to the same patch level as the rest of the farm, join them to ...



Top 50 recent answers are included