Migrate SharePoint OnPremise solution to SharePoint Farm

Hi,
I've some couple of queries regarding SharePoint solution migration from SharePoint premise to online.
1) We've some customs solutions which is developed using sandbox and the content database size upto 1TB. Can we able to migrate to SharePoint online. If it is possible how to migrate the content and what licensing model supports?
2) I've some 10,000 users in my SharePoint site collections. What is the best way to migrate users from on-premise to SharePoint online?
Balaji -Please click mark as answer if my reply solves your problem.

Hi Viet,
Have you used https for your SharePoint 2010 environment? or using AAM?
If yes, please check if you add the root certificates of the SSL certificate to the SharePoint 2010 per the following article.
http://karthickmicrosoft.blogspot.com/2012/10/https-site-infopath-issue-you-do-not.html
If not, please check and mark sure the below InfoPath service options are checked from Central Administration site and test again.
https://technet.microsoft.com/en-us/library/cc262263(v=office.14).aspx#authenticate
Allow user form templates to use authentication information contained in data connection files
Allow cross-domain data access for user form templates that use connection settings in a data connection file
If there is any further assistance needed, please feel free to post.
Thanks,
Daniel Yang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Daniel Yang
TechNet Community Support

Similar Messages

What is the best approach to migrate SharePoint farm from one data center to other datacenter

We have two web front server and one application server and two instances for database server and we have to migrate complete farm from one data center to other data center with minimal downtime and end user impact.
Please provide your best input on this.
Thanks in advance.

Create a new farm in the secondary Data Center at the same patch level with the desired configuration. Replicate the databases using the method of choice (Mirroring, AlwaysOn, etc.). Create a downtime window where you can then attach the databases to the
new farm's Web Application(s)/Service Application(s).
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Migration from Sandbox solution to SharePoint apps

Hi,
We have a requirement that we need to migrate SharePoint Sandbox Solution to SharePoint Apps. Few things which I would like to know that if the Sandbox solution has some custom code / server based code then how we have to migrate into Apps. Because
Apps only support client based. And in some cases, sandbox has no code solution. In that case, how we can migrate into Apps..
Recently, many companies are trying to migrate from Sandbox solution to apps becuase microsoft depreciated sandbox in SharePoint 2013. In future, they may stop to support sandbox solution. Please share your views on how to proceed on migration code
and without code based solution to Apps...
Balaji -Please click mark as answer if my reply solves your problem.

HI Balaji,
I assume you are having on premise Farm not office 365 so in that case
http://msdn.microsoft.com/en-us/library/office/fp179887(v=office.15).aspx
http://msdn.microsoft.com/en-us/library/office/fp179930(v=office.15).aspx
you have the following options for code:
1- SharePoint Hosted Apps: you will write Javascript code and use Javascript to access client object model
http://msdn.microsoft.com/en-us/library/office/fp142379(v=office.15).aspx
2-Provider Hosted Apps: you will write 2 parts , the first one is an application that will be deplpyed to SharePoint server the second one is a web site (asp.net or mvc) that can be hosted on the SharePoint server or on a separate Application server and
here you you can put all the logic of your .net code and you can have remote event recievers
http://msdn.microsoft.com/en-us/library/office/fp142381(v=office.15).aspx
for non code option what you will be doing is using SharePoint designer but mostly you will still to have SharePoint hosted apps
some codes
https://apps.codeplex.com/
https://corporatenewsapp.codeplex.com/
Hope this is clear and helpful
Kind Regards, John Naguib Technical Consultant/Architect MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation

How to migrate sharepoint 2010 onpremise to sharepoint online?

Hi,
I've seen many forums to migrate sharepoint 2010 to office 365. Everywhere they're pointing to use some third party tools. Actually, I am having the requirement that I've around 100-120 site collections and 1TB content database and many workflows
and 20-30 custom solutions etc. I want to migrate the entire solution to office 365. Can you please guide me how to implement this.
Balaji -Please click mark as answer if my reply solves your problem.

Use 3rd party tools! And your custom solutions will have to become either sandbox solutions (deprecated) or SharePoint Apps.
I would talk to a Microsoft Partner about this, as this is a complex undertaking.
Trevor Seward, MCC
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint Farm Solution Deployment without Downtime

Hi,
We are looking for a solution to deploy SharePoint .wsp in the farm without taking any downtime.
Load balancer is in place and there are more than 1 WFE, App and Search servers in the SharePoint farm.
If you have worked on similar solutions before or have any ideas/views regarding the same, also the pros and cons.
Request you to share the same.
Thanks & Regards,
Sudheer
Thanks & Regards, Sudheer

Since you have load balancer and more than one WFE, you may be able to deploy solutions first on one WFE and then on other WFE thereby preventing the outage. Check these posts for more info:
http://blog.ithinksharepoint.com/2012/07/16/deploying-sharepoint-wsp-solutions-without-downtime/
https://social.technet.microsoft.com/forums/sharepoint/en-US/fb4820b1-aca8-464e-a1ff-656c62c756a8/install-solution-packagewsp-with-no-downtime
Blog | SharePoint Learnings CodePlex Tools |
Export Version History To Excel |
Autocomplete Lookup Field

Delete the existing sharepoint farm it is a development machinie and re create again in same server

Hi
i want to
delete the existing sharepoint farm it is a development machinie and re create again in same server.
because i am facing issues to configure user profile service,
the user profile syncronisation service starting and after some time its stopped.
while i am reading http://www.harbar.net/articles/sp2010ups.aspx
in current farm i given ip address for sql server while installing sharepoint
you have not used a Fully Qualified Domain Name or IP Address when specifying
the SQL Server when running the SharePoint Configuration Wizard (PSConfig). Using either is strongly discouraged,
if i recreate the farm is it creates new databases in sql srver?
adil

1. Uninstall any custom / third party solutions deployed in server.
2. from central admin, delete web applications along with DB.
3. delete all service applications.
4. From the program settings, un-install sharepoint.
5. Go to SQL and delete if any DB from SP is left.
6. Uninstall SQL, if you see any issue.
These are high level reverse steps of the installation.
Thanks, Ashish | Please mark a post helpful/answer if it is helpful or answer your query.

Struggling to migrate sharepoint sites developed on dev or qa over to production

So, user 1 comes along and wants to put together a new site. He wants to use SharePoint Designer to set up pretty colors, create a new theme and use it, create a series of custom lists, etc.
Meanwhile, on these same machines, there is a variety of InfoPath development occurring by developer 2. The development is going on in a different site collection than user 1 is using.
User 1 gets to the point where he wants to migrate the minty fresh sharepoint site from dev to production.
He creates a template with content.
He copies it over to the production system. When he attempts to use it, he gets an error saying that Feature '{gobblidy gook}' is not found.
We look at features turned on, and the out of the box features are the same.
HOWEVER, the dev system has quite a number of dev instances of the InfoPath apps as they have gone through the "code, test, fix" cycle.
It appears to me that the issue is that the template is listing every one of those InfoPath forms as a requirement.
There's no way that I am interested in broken or incomplete InfoPath features being installed into production.
It appears to me that the user is stuck recreating the dev site on production.
That seems terribly inefficient to me. The entire template concept is pretty screwed up if templates uploaded to one site collection become required in another.
I presume that one or more of us - user 1, developer 2, or myself - is missing some critical bit of information that would make these things work.
Or is this really the kind of limitation by which others using InfoPath are hindered?

Where can I find those best practices?
Before we started using SharePoint, we always had at least dev, qa, and production machines where things being developed would start out and migrate through.
I suspect there would be a lot of resistance to giving all users their own VMs as well as their own SharePoint farms to work under, and I expect that attempting to move InfoPath apps from an individual's environment would have the exact same problem as we
are encountering - a developer wants to iterate through a series of unit testing before they consider an application (ie InfoPath form) stable enough to undergo testing by a group of stakeholders. Thus things created on the dev machine will have dependencies
on "features" (aka the individual test versions of the InfoPath form) that would not be installed on the stakeholder's test machine, and the last stable version on the test machine would have dependencies on versions that would not be promoted to
production.
developing on production has the issue of having to work in parallel with the previous stable version of the application, without causing the users of the stable version issues.

How-To: Restart the Database Server (SQL Server) in SharePoint Farm safely ?

Hello,
My farm has 4 SharePoint servers: 2 Application-Servers, and 2 WFE-Servers.
Each WFE-Server is running Distributed Cache service which means, I have 2 Distributed Cache service.
I must restart my SQL Server, But, How can I do that without losing the Cached data?
I can use Stop-SPDistributedCacheServiceInstance -Graceful which will move the cache from one server to another, But, what to do with the other one then?
I am really concerned because TechNet says: "Stopping the cache results in partial data loss. The Feed Cache depends on the Distributed Cache service.
Tags and document activities are saved only to the Feed Cache.
Tags and document activities are not persisted to content databases."
https://technet.microsoft.com/EN-US/library/jj219613.aspx#startstopcache
What can be done ?

Hi,
In my opinion you do not need to stop the distributed cache service.
You are correct the graceful shutdown will work if you want to stop a cache host. it is graceful because it should move the cache data to the other host(s).
I believe that the SQL is not hosted on SharePoint server?
My opinion is that no data should be lost if the SQL is not available for a limited period of time. The Distributed Cache is in memory cache.
You will however have downtime in case you are not using any High Availability solution for your SQL.
In case the period of maintenance on your SQL is longer you should plan it better and maybe stop the SharePoint Farm as described here
https://technet.microsoft.com/en-us/library/cc512725.aspx?f=255&MSPPError=-2147217396 (Move all databases section).
Ivan Yankulov
SharePoint Admin/Consultant
http://spyankulov.blogspot.com/
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft

Reconfigure DPM after migrating Sharepoint to another SQL Server

How can I Reconfigure DPM after migrating Sharepoint to another SQL Server?

Hi,
I have tried this.
When I removed the SharePoint datasource from Protection group there was no option to keep or lose data.
I ran ConfigureSharePoint -EnableSharePointProtection and ConfigureSharePoint -ResolveAllSQLAliases , then refreshed view in DPM console and added SharePoint back to protection group.
The modify protection group screen showed success. looking in Monitoring, I see Consistency check failed with this error "DPM cannot continue protection for SharePoint Farm Sharepoint Farm\sqpl2008srv1\SharePoint_Config on spwfe1.internal.ermanz.govt.nz.
(ID 30184)" this followed with Recovery point failing as well and description was same error (as above).
I then removed the datasource again and created a new Protection Group and added SharePoint, but got same result. When creating the PG, it did not format space or do initial copy and CC's and RP's failed as before.
When DB's were moved to another SQL Server, SharePoint retained the same SQL name as before (uses aliases)

Error while adding a WFE to a Sharepoint farm

Hi,
I am getting an error while trying to add a WFE to a sharepoint farm.
Below is the script I am running in the WFE server
Connect-SPConfigurationDatabase
-DatabaseServer $DBServer -DatabaseName
$DBName -Passphrase (ConvertTo-SecureString $PassPhrase
-AsPlainText -Force
Below is the error
I had done a lot of other tests to check whether the connection between the WFE and sharepoint farm is valid or not. For eg:
- Was able to create a configuration database in sharepoint farm from WFE server using New-SPConfigurationDatabase script. By this I was able to setup central admin in WFE.
The only problem is I am not able to connect to an existing configuration database. Please help.

Yes I tried adding in SQL alias and executed the sharepoint wizard, but I am still getting the same error.
"Failed to connect to the configuration database.
An exception of type System.ArgumentNullException was thrown. Additional exception information: Value cannot be null.
Parameter name: service
System.ArgumentNullException: Value cannot be null.
Parameter name: service
   at Microsoft.SharePoint.Administration.SPServiceInstance..ctor(String name, SPServer server, SPService service)
   at Microsoft.SharePoint.Administration.SPFarm.Join()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()"

Can you install Workflow Manager 1.0 on Central Admin App Server Machine in 3-tier SharePoint Farm?

Hi,
I have just realised when looking at doing a Workflow that 2013 Workflows not available (you need to install Workflow Manager Farm). I understand why from a tenant installation perspective, but we are on-premise.
Can someone tell me if I can install Workflow Manager 1.0 (seen you have to now install WM 1.0 Refresh version) on the Central Admin App Server Machine in a 3 tier SharePoint farm. 3 WFE, 4 APP Servers, 1 DB Server and 1 DB Analysis Services Server.
I did test on a test farm 1WFE, 1 APP Server (with CA) and 1 Database Server. We are getting issues with the WFE Server having issues booting up or losing connection - possibly faulty network card. This may in no way be related to the install,
but just in case.
Any help appreciated.
Thanks.
John.

Yes, you can install WFM on any server in a SharePoint farm.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Best way to migrate SharePoint 2003 data into SQL Server 2008

Hi Experts,
I am planning to migrate data from SharePoint 2003 into SQL Server 2008. After the migration SharePoint site will be deleted in couple of months and then that data will be feed into .Net Front end application
1) What is the best and easy way to do it?
2) Is there any way to automate the migration process? i.e. If a new record gets entered into SharePoint it should be populated into SQL Server 2008.
3) Any other suggestions
Thanks,
John

Dear John,
If it's just a few lists, and you just want to import them "as-is" then it should be possible to do so ... and survive to tell the about it ;-)
Generally speaking, You will need to write a small process (program or script) to read/parse each list and check if the item(s) are in the target table (I assuming that there is a distinct table as target
for each list, and that each list has 'something" you can use to distinct each row), if it's not there, the just add them according to your needs.
Then just rerun the process periodically and it would keep your databases up to date (you could even set ti up to update those records that have changes, but that would delay your process significantly)
What i just described is doable, and not TOO complicated, it could be done i a lot different ways, and with different alternatives of programming/scripting languages. for sure you can do it in any flavor
of .net language, and even powershell.
As I mentioned, this is speaking in general, the actual implementation would depend on your specific needs and the kind of data that you have/need to keep.
Best Regards / Saludos, Marianok
Disclaimer: This post, and all included code and information is provided "AS IS" with no warranties or guarantees and confers no rights. Try it at your own risk, I take no responsibilities.
Aclaración: Esta publicación, y todo en código e información en la misma, es provista "AS IS" / "Como Está" sin garantía alguna y no le confiere ningún derecho. Pruebelo su propio riesgo. No asumo responsabilidad alguna.

Use Microsoft Online Directory Services as a user authentication provider for our own SharePoint farm?

Hi,
I've managed to configure my farm so that Microsoft Online Directory Services (Office 365 etc.) can be used for STS authentication, but what I'm actually trying to do is allow user authentication - that is, I'm hoping to be able to use the user's
O365 credentials to authenticate them in my own farm so they can view certain parts of it. If I need to write my own login form or authentication provider or whatever that's fine, as long as the user doesn't need to enter anything when they access my farm
(provided they already have cached O365 credentials in their browser session).
FWIW I actually need to be able to support the possibility that users are coming from multiple O365 tenancies, whereby each site collection will be configured to allow users from a different O365 tenancy (more or less).
If it's not possible to do with my own development farm on a PC, it is possible if the farm is hosted in Azure?
Thanks
Dylan

Hi Dylan,
According to your description, my understanding is that you want to use Microsoft Online Directory Services as a user authentication provider for your SharePoint farm.
For your demand, you can configure a hybrid topology for your SharePoint farm:
http://technet.microsoft.com/en-us/library/jj838715(v=office.15).aspx
http://technet.microsoft.com/en-us/library/dn197168(v=office.15).aspx
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Eric Tao
TechNet Community Support

Error in migrating SharePoint 2010 list fields to Office 365 list [CSOM]

Hi,
I am trying to migrate a SharePoint 2010 list to Office 365. I created a new ListCreationInfo for a new list in O365. But when i am to trying add fields from SP2010 list, its giving me an error after list.update() -
A duplicate field name "fa564e0f-0c70-4ab9-b863-0177e6ddd247" was found.
if (!l.Hidden)
ListCreationInformation creationInfo = new ListCreationInformation();
creationInfo.Title = l.Title;
creationInfo.TemplateType = l.BaseTemplate;
List list = web.Lists.Add(creationInfo);
//Fields in the list
ctxOnPrem.Load(l.Fields);
ctxOnPrem.ExecuteQuery();
foreach (Field f in l.Fields)
list.Fields.AddFieldAsXml(f.SchemaXml, true, AddFieldOptions.DefaultValue); list.Update();
Note- l is the SharePoint 2010 List.

Answer given on StackExchange -
http://sharepoint.stackexchange.com/questions/128875/error-in-migrating-sharepoint-2010-list-fields-to-office-365-list-csom/129015#129015
Thanks,
Thomas

IP addresses are going to be changed for SharePoint farm servers(App, WFE, DB)

Hello,
We had multiple SharePoint Farms, and we would like to changes the IP address of all the servers in farm(because of changing the Datacenter). will I get any issues, if, how can I take it forward. Need suggestions.
Thank You
NARLA

As Vivek says it won't break anything, as long as you fix DNS.
SharePoint checks the database server by server name or alias, which both use the computer name, so no IP addresses are directly used there.
So these should be the steps:
1. Change your DNS records to point to the new IP address for all Web Applications
2. Change the IP addresses for the SQL Server and SharePoint
3. Check IIS on your SharePoint Server(s) to see if the new IP address is correctly configured for all Web Applications on all the servers in your farm.
4. Test everything :)
Happy SharePointing!
Nico Martens
SharePoint/Office365/Azure Consultant

I want to create a medium SharePoint Farm

Hi All,
I want to create a medium SharePoint Farm, i am having below three servers
1)Web Server
2)Application Server
3)Data Base Server
Now, what i have to install on Web server, application server and data base server.
How to make a relation between each server.
Can any one help me on the same.
Thanks in advance!

Hi Anil,
Thanks for posting your query, Kindly browse the below mentioned URL to setup Small farm with three servers step by step
http://sharepointrayyan.blogspot.in/2012/04/sharepoint-server-2010-step-by-step.html
Also, you can checkout the below mentioned URLs to fix this issue
http://www.endusersharepoint.com/EUSP2010/2010/06/09/how-to-install-sharepoint-2010-on-small-farm-part-1-full-installation-on-small-farm-up-to-managing-service-applications/
https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0CCoQFjAC&url=http%3A%2F%2Fsprider.files.wordpress.com%2F2011%2F07%2Fsharepoint-server-2010-step-by-step-small-farm-3.docx&ei=cWZeVLbiHM6juQSc5oCYCg&usg=AFQjCNELVS8AW3BowIA6f4KcVFFYhW6rmg&sig2=WLOuB4a8TRBZQjaE7p0gmg&bvm=bv.79189006,d.c2E
I hope this is helpful to you, mark it as Helpful.
If this works, Please mark it as Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog : http://sharepoint-community.net/profile/DharmendraSingh

Migrate SharePoint OnPremise solution to SharePoint Farm

Similar Messages

Maybe you are looking for