Questions and Answers during the Webinar
Can you tell me the release date of full version of SharePoint
It is already released. You can refer the following link.
Can you elaborate on Storage infrastructure improvements?
refers to SQL Server 2012 for performance and scalability.
Therefore, you can take the advantage of its storage
infrastructure. SharePoint 2013 supports Shredded storage and RBS
Why has Web Analytics been removed in SharePoint 2013?
Web Analytics in SharePoint 2010 was having performance issues
in large enterprise so it has been discontinued. But this component
is still existing in SharePoint 2013 and it is available in Search
Service. It is improved in terms of performance and scalability. It
lists the content in the search index and user actions that are
performed on SharePoint sites.
Does SharePoint 2013 support External BLOB Storage?
No. This feature is deprecated. SharePoint 2013 only supports
Remote BLOB Storage. During the migration from previous version of
SharePoint to SharePoint 2013, if you are using the EBS then you
need to migrate from EBS to RBS then migration to SharePoint 2013
will be possible.
What would be the Permission level on the site if I Migrate
From SP2010 to SP2013? Would it be there? I have the Active
It will remain same unless you are referring different Active
Directory then you need to manage the permission level manually or
by using any third party tool. You also need to ensure the
supported permission architecture of migrated sites as it happens
sometimes that they will not work properly.
What is the best way to get the backup of the SP2010 Content
Database either using PowerShell or some other way?
You can use PowerShell commands for taking backup of Content
Databases. You also have the option to use SQL Server Management
Studio as it enables the GUI.
Can we use 2013 license to install 2010. I do not follow how to
migrate to 2010 with 2013 license
No. SharePoint 2010 and SharePoint 2013 have different licensing
What happens when we test database and upgrade is not ok, is
there any indication of what to do?
It will return a list of errors while you execute the
Test-SPContentDatabase and while upgrading, it will log all the
errors in .upgrade file because of the broken links within the
content and environment.
Is it possible to migrate user profiles just by attaching the
Yes, it is possible.
I found one new feature in SP2013 i.e. workflow management
service. After migrating SharePoint 2010 designer workflows, those
workflows will work or not?
Yes, they will work as SharePoint 2013 supports both workflow
Can we migrate from 2007 to 2013 without installing 2010 in the
Yes, because SharePoint 2013 supports SP Mode 14 and SP Mode 15
simultaneously. Therefore, you need to install and configure the
SharePoint 2013 farm, first you need to migrate from MOSS 2007 to
SP Mode 14 of SharePoint 2013 (i.e. SharePoint 2010) then perform
Visual Upgrade, and finally you can migrate to SP Mode 15 of
SharePoint 2013 (i.e. SharePoint 2013).
While upgrading from MSS to SP 2013, we have two environments
(MOSS & SP 2013). We migrate from 2007 to 2010 (14 mode in SP
2013) and then from 14 mode to 15 mode within SP 2013. So do you
mean that the 14 to 15 mode migration happens in the same
environment (i.e. The same server farm)?
Yes, it will happen in the same environment.
Regarding migration from MOSS to 2013, once we upgrade to 14
mode then do we have to uninstall SharePoint 14 and then install 15
No. Once you install SharePoint 2013, it will allow you to
create your sites in Mode 14 and Mode 15. Therefore, once you
migrate from MOSS 2007 to SharePoint 2013 Mode 14 then you need to
perform visual upgrade and then migrate to SharePoint 2013 Mode 14
to Mode 15.
What is the best approach for Migrating MOSS 2007 to SharePoint
First of all you need to create New environment for SharePoint
2013 then take a backup of your MOSS 2007 Content Databases and
restore them to new environments. After that Run the
Test-SPContentDatabase command to collect the pre-migration
information about each object in Content Database and fix the
issues regarding to customizations if any. Later execute the
SP-MountContentDatabase command to migrate to SharePoint 2013 SP 14
Mode and review and validate your first stage of migration. In the
last migrate from SP 14 Mode to SP 15 Mode but before that do not
forget to apply visual upgrade to SP 14 Mode site.
After migrating to 2013, What is going to happen to those sites
currently using MOSS 2007 UI in SP 2010? What about those sites
that are working right now with MOSS 2007 UI in SharePoint 2010.
Are those going to be upgraded to SP2010 UI?
First, you need to do visual upgrade while you migrate from MOSS
2007 to SP 2010. Without visual upgrade, you cannot migrate to SP
2013. Therefore, you need change UI of MOSS 2007 first.
What is the better approach to migrate from 2010 to 2013
considering that you want to modify the permission structure in the
Assuming that you have new hardware to install SharePoint 2013,
first you need to take backup of your Content Databases and restore
them to the new environment. Afterwards, execute the
Test-SPContentDatbase and review the log for upgradable. If there
are no issues then you can execute the Mount-SPContentDatabase and
then perform differed site collection upgrade to take SP 2013 look
What is the better approach to migrate from 2007 to 2013? With
help of third party products? What do you think?
It depends upon the third party tools. You should also consider
the cost as well. You can also refer the following practice to
migrate from MOSS 2007 to SharePoint 2013:
Install and configure the SharePoint 2013 farm and first you need
to migrate from MOSS 2007 to SP Mode 14 of SharePoint 2013 (i.e.
SharePoint 2010) then perform Visual Upgrade and finally you can
migrate to SP Mode 15 of SharePoint 2013 (i.e. SharePoint
How to move manage metadata Taxonomy?
You can restore the Manage Metadata Service database to
SharePoint 2013 environment and perform the database attach
approach to migrate it. Once the migration has completed
successfully then all the Taxonomy will be available and
How to migrate project database?
The project Server
migration process is considered in two way phases - SharePoint
Upgrade Phase and Project Server Upgrade Phase. For SharePoint
upgrade, you can follow Database attach approach and for Project
- Convert to Project Databases to Project service database
- Attach project services databases to web application
- Test project service database for warnings and errors
- Upgrade project services database
- Mount Project Web app instance
- Test Project Web app instance for warnings and errors
- Upgrade Project web app instance
- Enable project web app features
In 2013 once deferred site collection upgrade is done, can't we
get the 2010 UI again?
Yes, once you migrated to SharePoint 2013 look and feel you
cannot revert to SharePoint 2010 UI.
If My Site in 2010 is using FBA and is migrated to 2013, what
are the steps to be taken care?
You can follow the standard steps for Database attach upgrade
approach. SharePoint 2013 supports the claims authentication as
Does any previous workflow built in 2010 need to be rebuilt
No. SharePoint 2013 supports both the workflow platforms.
Can we move from 2007 to 2010 before upgrade to 2013 using 2013
Yes, that is correct.
What happens to those sites that have the look and feel of MOSS
2007 on an upgraded SP2010 once we migrate to SP2013?
You need to do visual upgrade first before you migrate from
SharePoint 2010 to SharePoint 2013. It is mandatory.
What about FBA already implemented on SP2010? Is there going to
be any change? Can it be upgraded at once?
SharePoint 2013 supports Claims Authentication as default. So
while migrating Claims enabled sites, it will be migrated. Make
sure that before upgrading content database FBA provider needs to
be installed. Claims related issues would be tracked by
Could you please let us know the approach followed for user
To migrate User Profiles from SharePoint 2010 to SharePoint
2013, Database attach approach can be used. Please consider that
Profile and Social databases are supporting database attach
approach. Sync database is not supporting database attach approach
in V2V upgrade.
Is it compulsory to keep same port no. on SharePoint 2013?
No. It is not compulsory to keep the same port number. If a
previous version of SharePoint site is accessible by end users and
port number is included then it is not considered as best practice
to change the port number after migration. It could cause broken
links within the content and environment.