Migration of SP2010 Foundation Path Based to SP 2013 Enterprise Host name site collections

Greetz!
Need some sanity checking here. We have an existing intranet that uses SP 2010 Foundation (all out of the box) using SQL Express. We are standing up a brand new 2013 Farm on new hardware in a new network which will use host name site collections.
According to
TechNet this is a supported upgrade path.
My thought is to do a database attach method from the old farm to the new one to get the product edition upgraded. Then to convert path-based site collections to host-named site collections I would need to follow the method described
here which is to backup and restore to the hnsc of my choice.
Something seems off about this though. Can I just attach to the new SQL instance and run the Mount-SPContentDatabase or is there something about the backup-spsite and restore-spsite commands that does a conversion??
Thanks!
Love them all...regardless. - Buddha

You need to do the Mount-SPContentDatabase to upgrade the schema of the database from 2010 to 2013. Then you'll need to do the backup and restore to change the sites over to Host Named Site Collections. Both steps will be required to accomplish
what you want since you can't backup a 2010 site and restore it to a 2013 farm.
Paul Stork SharePoint Server MVP<br/> Principal Architect: Blue Chip Consulting Group <br/> Blog: <a href="http://dontpapanic.com/blog">http://dontpapanic.com/blog</a><br/> Twitter: Follow <a href="http://twitter.com/pstork">@pstork</a><br/>
Please remember to mark your question as "answered" if this solves your problem.

Similar Messages

Managed path for host named site collection is farm level or web application level?

Hi,
I would like to get advice.
I created a webapplication for host named site collections.
these are my host named site collections (except http://sp2013) under my webapplication
Root Site Collection: http://sp2013
Site Collection: portal1.sg
Site Collection: portal1.sg/research
Site Collection: portal1.sg/intranet
research and intranet managed paths are farm level
all my host named site collection will be accessed by http and https except "intranet" site collection will be only accessed by https
so I changed the Intranet zone for site collection using Set-SPSiteUrl
Set-SPSiteUrl (Get-SPSite "http://portal1.sg") -Url "https://portal1.sg" -Zone Intranet
Set-SPSiteUrl (Get-SPSite "http://portal1.sg/research") -Url "https://portal1.sg" -Zone Intranet
Set-SPSiteUrl (Get-SPSite "http://portal1.sg/intranet") -Url "https://portal1.sg/intranet" -Zone Intranet
Now I need to create "search" site collection for "Enterprice Search Center"
My question is that for the "search" managed path ... should i use farm level or web application level?
"search" site collection will be will be accessed with both http and https also.
Thanks a lot!

managed path for HNSC is farm level and u can have 20 managed path
while managed path for path based is 20 per web application in your case if you are going to have a a separate web application for search then u will use web app
Kind Regards,
John Naguib
Technical Consultant/Architect
MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation
Please remember to mark your question as answered if this solves your problem

Migrating a Path Based Site Collection to a Host Named Site Collection where the content database is greater than 135 GB

Hi
I have a 136 GB content database which will not back up via Backup-SPSite ( Microsoft say you cannot backup more than 100GB).
So with out Backup / Restore how can I convert a Path Based Site Collection to a Host Named Site Collection with my 136 GB content database which incidentally uses Remote Blob Storage ?
Thanks
Nigel
Nigel Price NJPEnterprises

I see two options:
Make the Backup-SPSite work despite being over 100GB (that's going to be a supported limit rather than a hard boundary)
Externalise some of the content and then re-insert it after the move.

Migrating SP2010 host-named Site Collections

Hi all,
I'm currently having an issue when upgrading Host-Named site collections from SP2010 to SP2013. Once upgraded into SP2013 (Database attach), It keeps on prompting me for credentials, even after adding my user as a Web Application user.
Is there any resources or considerations when upgrading Host-Named sites?
Cheers

Loopback check is the most common cause of this behaviour:
http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx
To confirm, add a hosts file entry on a non SharePoint machine and then connect from there. It'll probably work.

Error Accessing Host Named Site Collections In SharePoint Foundation 2013

We have a new SharePoint Foundation 2013 server that has one web application two host named site collections. We get the "This page can't be displayed" message when we try to navigate to either of the site collections. Adding the server's IP to
the host file on the machine we are testing from doesn't help. We can ping the new sites from that machine. The web application does not have a host header.
Web application URL = http://servername
Site collection #1 URL = http://customer.company.com
Site collection #2 URL = http://vendor.company.com

Hi,
I recommend to verify the things below:
Check if site can be accessed with site collection administrator.
Add the SharePoint sites to a trusted zone to see if the issue still occurs.
As this issue can be caused by many reasons, you may check the ULS log for more detailed errors.
For SharePoint 2013, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Setup Team Foundation Server - Team Site Collection - SharePoint Web Application Settings failed with error TF205014, TF250025

Hi
I have TFS server installed and working with other SharePoint farm. (TFS installed, SharePoint extension installed and Granted Access for TFS.
When Setup TFS - SharePoint Web Application Settings, It ask for the three values:
Web Application URL:
Central Administration URL:
Default Location of team project collection sites:
What notice about the TFS sites that are working is that they are Path Based Site Collection. Created with SharePoint Web Application managed path (like
http://spserver/sites/tfs_site1) and so it easy to see it will work.
Web Application URL: http://spserver
CA URL :   http://spserver:portnumber
Default Location : Sites or any managed path
We start using Host Name Site Collection (HNSC) to get the benefit of multiple unique site name without having multiple web application for each. Work great but when we tried to setup and extend TFS service on the HNSC, we could
not get them to work and got errors when trying different variation of path URL.
After doing lot of searching on this, I came up pretty empty and I don't know if that is possible so my question is Have anyone able to setup TFS to work with SharePoint 2013 Host Name Site Collection?
If you have, a simple yes will be great but please share or even if anyone think it is possible or not possible, please share too.
Thanks in advance for any comment / suggestion.
Swanl

Hi Swanl,
I’m afraid that we cannot setup TFS to work with SharePoint 2013 Host Name Site Collection.
Also you can initial a new thread in Visual Studio Team Foundation Server forums：
Team Foundation Server – General: http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=tfsgeneral
More experts for Team Foundation Server will assist you, then you will get more information relation to your issue.
For integrating SharePoint 2013 with Team Foundation Server 2013 you can have a look at the following blog:
http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
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

Internet access to new sharepoint foundation 2013 site collection

I had sharepoint 2010 installed on my WHS 2011. I successfuly created a new web application and site collection. I created a new SP default site on a port different from 80 and restarted the WHS 2011 default site in IIS. I could
see both the WHS 2011 and SP 2010 default sites from the server, my client PCs, and from my office. Great!
I uninstalled SP Foundations 2010 and installed SP Foundation 2013. I successfully created a web application on the same port I had used for SP Foundations 2010 because the firewall rule on my server and the port forwarding on my router
where already in place. I again restarted the WHS 2011 default site in IIS. I can see the WHS 2011 and SP 2013 Foundation default sites from the server and my client computers. However, I can't see the SP Foundation 2013 site from anywhere outsite
of my home network.
Help someone?

1. I removed the IIS bindings to port 80 for the home server default site. Now, I can reach my share point default site remotely on port 80 by going to
http://x.home server.com and I can reach the home server default site by going to
https://x.homesever.com/remote on port 443.
2. Using Power Shell I created 3 host named site collections. I put the URLs to those collections in the server hot's file and disabled loopback. I can see the sites on hte server. However, how do I make my sites accessible remotely or maybe the correct
term is publicly on computers outside the network?
3. I started down the road of host named site collections because I want to make them accessible remotely or publicly without using the x.home server.com domain name. However, I am starting to think that I am missing an important piece to making this work.
Thanks

Migrate Server 2008 Certificate Authority To New Server Different Host Name?

Our internal CA is installed on one of our Exchange servers. Exchange is being migrated from 2010 to 2013, so all current Exchange servers will decommissioned and replaced with new new Hyper-V VMs with either Server 2008 R2 or 2012 R2 OS. The old VM
containing Exchange 2010 and the current CA will go away since we cannot afford to use the server resources and use up the required Windows license to keep that server running doing nothing but acting as a CA.
So, we will either need to move the CA to the new replacement Exchange 2013 server or some other existing server that's being used for something else (maybe one of the domain controllers).
What is the best way to handle this? I don't think the migration from Exchange 2010 to 2013 allows for reusing the same host name on the replacement server and if we move the CA to another existing server, it will also be on a server with a new host
name anyways.
Can we migrate the CA to a new server with a different host name?
What about reissuing all the active certificates from the current server to replace them with new certificates from the new server and then decommissioning the original CA? Can this be automated in some way?
Which way is best and how would it be done?

When following the instructions in the guide, I would also consider to switch to new "sanitized" URLs in certificates (CDP and AIA) in case you had used the default URLs now. That's what I did this when migrating W2K3 CAs (with default URLs) to W2K8 R2.
Per default, the LDAP and HTTP URLs point to the CA server itself (HTTP) or to an LDAP objects that has the same name as the current server.
Migrating to a new server, you need to make sure that CRLs will still be published to the old locations - thus the new CA server would write to the LDAP object that corresponded to the old server, and HTTP might be fixed by redirecting the DNS record. (Make
sure this is documented so that nobody thinks it might be a good idea to delete the old object as it "references a server that does not exist anymore".)
As you have to fiddle with URLs anyway, I would then add new URLs having neutral names - that is URLs not including the name of the CA server. The new CA instance would then 1) publish to the old locations but not add these to certificates anymore and 2)
publish to new sanitized locations and add them to CDP and AIA URLs.
Elke

How-To: Migrate Classic Path-based SP2010 Site Collection with OOTB/SPD Workflows = To: Claims Different Path-based SP2013 Site Collection ?

Hello,
I want to move an entire site collection from an old SharePoint 2010 farm to a new SharePoint 2013 farm. But there are a few requirements:
- The old SP2010 site collection contains multiple SPD Workflows and OOTB Workflows.
- URLs must be changes as the example:
Source Site Collection URL: http://OldWebApp.SP2010.com/sites/OldSiteCollection
Destination Site Collection URL shall be: http://NewWebApp.SP2013.com/projects/NewSiteCollection
- There are no custom solutions nor web parts.
How to accomplis this successfully ?
My steps would be:
1) Copying the content database from SP2010 SQL to the SP2013 SQL via: Copy-only backup feature, or the traditional Backup & Restore.
2) I have already the Web Application on the new SP2013 ready, So, I will just need to create the destination site collection in the SP2013 environment with the new desired URL: (http:\\NewWebApp.SP2013.com\projects\NewSiteCollection).
3) Remove the newly created Content Database of the new site collection in the destination environment.
4) Test-SPContentDatabase -name Old_Content_DB -webapplication http://NewWebApp.SP2013.com > C:\Issues.txt
My worry is that the SP2010 Web Application is Classic-based and I cannot change the entire Web Application to Claims-based as it hosts other running site collections !
Equally, My other worry is that the SP2013 Web Application is Claims-based and I cannot change the entire Web Application to Classic-based as it hosts other running site collections !
First-Question=> I cannot run Convert-SPWebApplication as I don't want to impact the entire source nor destination web applications - How to resolve this?
5) Mount-SPContentDatabase "Old_Content_DB" -DatabaseServer "DBServer" -WebApplication http://NewWebApp.SP2013.com
Second-Question=> As I mentioned above that my requirement is to migrate this old SP2010 site collaction to a totally new URL in SP 2013. My concern is that after completing step-5, the site
collection will overwrite the root new web application and it gets placed on: (http://NewWebApp.SP2013.com) ! I want it to be: (http://NewWebApp.SP2013.com/projects/NewSiteCollection) ? How to do this trick?
Third-Question=> Will all the SPD Workflows & the OOTB Workflows work correctly after the entire site collection has been moved from SP2010 to SP2013? I am asking this because I seen this:
(http://blogs.msdn.com/b/chandru/archive/2013/04/14/upgrading-spd-2010-workflows-to-spd-2013-workflows.aspx), and I got scared. What do you think ?
Could you please help me out in my three questions ?

Following are the steps:
Take the backup of the content database in SP 2010.
Create a classic based web application in SP 2013 using PowerShell.
New-SPWebApplication -Name "TestApplication" -ApplicationPool "TestApplicationAppPool" -AuthenticationMethod "NTLM" -ApplicationPoolAc
Create a content database in the web application created above.
Mount the database
Mount-SPContentDatabase WSS_Content_100 -DatabaseServer SQL2012Demo -WebApplication http://sp2013demo:100
Now convert the web application to use claims authentication:
Convert-SPWebApplication -Identity "http://sp2013demo:100" -To Claims –RetainPermissions -Force
Finally, migrate the users to use claims identity:
$w = Get-SPWebApplication "http://sp2013demo:100"
$w.MigrateUsers($True)
See these links for more information:
http://www.sharepointnadeem.com/2013/12/sharepoint-2013-upgrade-from-sharepoint.html
http://www.sharepointnadeem.com/2014/01/upgrade-from-sharepoint-2010-classic.html
Blog | SharePoint Learnings CodePlex Tools |
Export Version History To Excel |
Autocomplete Lookup Field

SharePoint 2007 (WSS 3.0) migration to SharePoint Foundation 2013

Hi
I have a requirement to migrate a SharePoint 2007 (WSS 3.0) farm to a SharePoint Foundation 2013 farm. The WSS 3.0 farm has SQL Server 2005 Standard running so no restrictions on the size of the content database. The SharePoint Foundation 2010 and 2013 farms
will share the same SQL Server 2012 Standard instance (as I know WSS 3.0 will have to be migrated to 2010 before 2013). I also have two other WSS 3.0 farms (so three WSS 3.0 Farms, lets call these A (250GB), B (90GB) and C (60GB)) that I need to migrate
into WSS 3.0 Farm A before the migration to SP 2010.
My question is, can I migrate a 400GB WSS 3.0 site collection to SP 2010 or will I have to split this into separate site collections? I have read that there is a best practice limit of 100GB per site collection but this does not stop a larger migration from
happening. Obviously over time when the migration has completed to SharePoint Foundation 2013 the single site collection will grow and grow so perhaps now is the right time to split this out into, say, year named site collections, but surely this will incur
an end of year process to create new site collections and a custom dev headache due to different locations to send newly created sites?
Thanks.

The answer is Yes, and you are correct about the best practice of a limit of 100GB,
although, document and record centers (e.g. non collaborative) can go much higher.
http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#ContentDB
That being what it is, your sites will perform better if you find a topology that allows the content databases to be under 100GB each. You can use Move-SPSite to accomplish that feat.
You'll want a separate instance for 2010 and a separate instance for 2013
and finally, put some quota's in place and then governance document\statement that informs users that 100 GB is the max for any given site collection that uses collaborative features (calendars, lists, workflows, etc.)
The simple path is explained on technet, go from 2007 to 2010 (you can inplace upgrade if you want) then go from 2010 to 2013, database detach and attach is only way.
please check the below link that explains more about the migration from share point 2007->2013.
http://technet.microsoft.com/en-us/library/cc262483(v=office.15)
Stacy www.sharepointpapa.com

Migrate SP2010 site collection to SP2013 site collection with a new URL - How ?

How to migrate Classic SP2010 site collection (http://OldWebApp.SP2010.com/sites/OldSiteCollection) to Claims SP2013 site collection: (http://NewWebApp.SP2013.com/projects/NewSiteCollection) ?
No custom solutions involved, But, The URLs must be different.
How to accomplish that ?

Following are the steps:
Take the backup of the content database in SP 2010.
Create a classic based web application in SP 2013 using PowerShell.
New-SPWebApplication -Name "TestApplication" -ApplicationPool "TestApplicationAppPool" -AuthenticationMethod "NTLM" -ApplicationPoolAc
Create a content database in the web application created above.
Mount the database
Mount-SPContentDatabase WSS_Content_100 -DatabaseServer SQL2012Demo -WebApplication http://sp2013demo:100
Now convert the web application to use claims authentication:
Convert-SPWebApplication -Identity "http://sp2013demo:100" -To Claims –RetainPermissions -Force
Finally, migrate the users to use claims identity:
$w = Get-SPWebApplication "http://sp2013demo:100"
$w.MigrateUsers($True)
See these links for more information:
http://www.sharepointnadeem.com/2013/12/sharepoint-2013-upgrade-from-sharepoint.html
http://www.sharepointnadeem.com/2014/01/upgrade-from-sharepoint-2010-classic.html
Blog | SharePoint Learnings CodePlex Tools |
Export Version History To Excel |
Autocomplete Lookup Field

SSIS - Loop through files from a file path based on the value in the variable

Experts,
I have a requirement where I'll be loading multiple files in to a SQL server table and archive the files when loaded. However, the challenge is , the file path should be dynamic based on the value of a variable (say, @ProductName).
For example: If I am running the package for variable @ProductName="Product", the file path would be "\\....\Src\Product", in that case the ForEachLoop will loop through all the files in that folder, load them to the table and Archive
the files to the "\\....\Src\Product\Archive" folder.
Similarly, if the @ProductName="Product_NCP", the foreachloop container should loop through files in the "\\....\Src\Product_NCP" folder, load them to the table and archive them to the ""\\....\Src\Product_NCP\Archive"
folder.
Any suggestions? I should be able to run the package manually just by passing the "@Product" value, create Archive folder if it doesn't exist, load the data and archive the files.

Yes
1. Have a variable inside SSIS to get folder path. Set path based on your rule using an expression
like
(@[User::ProductName] == "Product" ? "\\....\Src\Product" : (@[User::ProductName] == "Product_NCP" ? \\....\Src\Product_NCP:..))
similary archive
(@[User::ProductName] == "Product" ? "\\....\Src\Product\Archive" : (@[User::ProductName] == "Product_NCP" ? "\\....\Src\Product_NCP\Archive" :..))
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Issue in Custom Blog site definition based on SharePoint 2010 blog site definition after migrating the sites to SharePoint 2013 and site collection upgrade

I have created a custom blog site definition using SharePoint 2010 blog site definition with Configuration ID 31 in onet.xml (new value). This was working fine for SharePoint 2010.
We created new SharePoint 2013 farm and deployed the all Custom solutions in
14/15 folders. After migrating the sites to SharePoint 2013 using Content DB approach, site created previously using my custom definition are working fine.
But after running site collection upgrade these sites stop working. When I post a comment then comments not getting listed on post detail page. However comments are getting added to Comments List but
PostTitle column of Comment is not getting populated.
Also, when we create a new site in SharePoint 2013 using my custom blog template then that is also not getting provisioned. default.aspx and look-up between post and comment list are not working.
If any one has faced such issue then please share your findings and any solution to fix this.
Thanks in Advance :)

Hi ,
According to your description, my understanding is that the blog based on custom blog site definition didn’t work correctly after migrating custom blog site definition to SharePoint 2013.
If you customized the Onet.xml file in a previous version's site definition, you should modify some sections in the file to work in the current version, like <BaseTypes> and <ListTemplate> etc. More information, please refer
to the link below:
http://msdn.microsoft.com/en-us/library/office/aa543837(v=office.14).aspx
For that the PostTitle column of Comment is not getting populated, please try to modify the view, then compare the result.
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

SP2010 Foundation Post Install issues on development workstation - Database and Services

Just recently installed SP2010 Foundation for a development workstation. Platform isWin7 X64 pro, SQL 2008 (Developer edition)
(1) Looks like search has some configuration issues. This is in the Windows event log
The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID 38eefca2-d092-47f4-a833-23f8280c5f63) threw an exception. More information is included below.
The device is not ready.
(2) In Central Admin > Servers in Farm
Status - "Upgrade Available",
(3) In Central Admin > Manage Database Upgrade Status
Sveral of the Datbase(s) mention that upgrade is recommended, but one in particular mentions that the DB is too old?
WSS_Search_GHHTY
SPSearchDatabase
Database is too old and upgrade is required
Huh?
(4) Looking at my local SQL 2008 instance that SP2010 created, I see several DB's with "Config" in the name along with a guid on the end of the name. Is the result of re-running the configuration wizard several times while
I was correcting install issues?

here is question, i am assuming its fresh install not upgrade...
when you run the config wizard( you mentioned many times), which option you select from 2nd try to on ward....cannot disconnect this server from farm?
are you using any script to install ?
I would say run the config wizard without disconnecting and this server will host CA option.
from the central admin > manager server in farm...on top you will see farm version and config database name. note it
from the Manage database Upgrade status page note all the db names
now match it on sql and keep those and all other should gone now as a clean process.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Post Migration from SP2010 -Attach File Button not working in any list new/edit forms

Hi,
We have migrated the SharePoint 2010 farm to Sharepoint 2013 on last saturday and we are noticing an interesting issue after the migration .
On any custom list on any web application ,When we create a new item,if we click on attach file button in the ribbon,nothing shows up on the screen.
In the browser Dev Tools its showing an error message as "Cannot read Property style of null".
This is happening on a javascript (form.debug.js) on line No : 5276
(document.getElementById("partAttachment")).style.display = "block";
There is no element rendered in html with id "partAttachment",which is causing this error to happen.
Solutions tried are
1) Modified the List Advanced Settings to disable and enable the attachments ,which did not work
2) Ran the Sharepoint Configuration wizard which did not fix
3)Tried reset the site definition for all pages in the site from site settings
4) Deactivated and activated all the activated features in the site collection
Its an OOB List New Form,no customizations has been done.
Similar error occurring with List Edit form as well
when you click on the List Item in the List default view when you navigate to the list and when you click on attach file,a popup dialog to upload attachments appearing,However its not working when you
navigate into the list item and tried to upload attachment.
Please help if any Solutions / thoughts

Hi Christopher,
Thanks for your reply,
Farm Information
OS: Windows Server 2008 R2 SP1 Enterprise
SQL: SQL 2008 R2 SP2
SP -SharePoint 2013 with no CU applied
Method,we used is restored the content DB from SP2010 and attaching to SP2013 SQL Server
Site Collection is in 15 mode
It happens on new site collection even though its not migrated site.
Server is 16GB RAM 8Core Processor
If we create a new form from designer,attach file link is working
OOB New form.aspx is having List Form webpart
Custom New Form.aspx creaed with designer has data form webpart
if we create a new sharpoint site collection in 2010 mode,its working fine without any issues
Interestingly,all the javascript files loading were debug.js,Not sure how its loading all debug.js files

Migration of SP2010 Foundation Path Based to SP 2013 Enterprise Host name site collections

Similar Messages

Maybe you are looking for