1. Major Sponsors Minor Sponsors

2. http://o365.net.au
gristy@gmail.com
http://cube4.com.au

3. Background on the project
Methods we used
Lessons we learnt
Session Agenda

5. SharePoint 2010 Enterprise Environment on SQL
2008
Several Web Applications
Three Server Farm (WFE, APP, SQL)
3rd Party Solutions.
Nintex, Axceler, Kaboodle, Macroview and Custom.
15 Site Collections running under /sites/ path
Separate content database for each site collection
What we had (SharePoint 2010)

6. Windows Server 2012, SQL Server 2012
Single Web Application for Content
One Site Collection per Content Database, URL
Four Server Farm
(WFE,APP,SQL, Workflow/OWA)
Keep 3rd Party Functionality
SSL throughout
What we wanted (SharePoint 2013)

7. Issues with 2010 farm
Beach generally early adopters Lync and Exchange
migrations were already underway
New features
So I could play with the new stuff 
Reasons to upgrade

8. In-Place Upgrade is NOT Supported
Database Attach is the only supported MS upgrade
option
Only the following databases can be upgraded:
3rd Party Migration Tools
Options for upgrade

9. Migration tools were not quite ready so decided on
database attach
Decided early on to not upgrade SA databases
MMS and UPA were not heavily used
Only upgrade those SAs that have critical data in
them. If you haven’t invested anything into UPA or
the Managed Metadata store, simply create new
ones in SP 2013.
This will keep the process simple.
A content-only migration can be made relatively
simple by following this rule
The approach we took

10. Took our time with the upgrade due to the new
design of a single URL for each site collection we
were able to stage the upgrade
Did a couple of site collections at a time
Made sure environment was stable adding more
site collections every few days
Left biggest site collections until last (worst
weekend ever)
Left the root site collection until last
Custom navigation built for SharePoint 2013
The approach we took (cont)

11. Four Web Applications
HNSC for all sites
What we have today

12. Out of the box branding (end users did not really
care)
What we have today (cont)

13. Customised (Security Trimmed) suite bar with each
site collection
Built using a delegate control
See me after to learn the technical details
What we have today (cont)

14. SharePoint 2010 Environment was all
Classic Authentication
Did not RTFM on how to overcome
hurdle and ran into issues with
permissions
Recommendation from MS is to convert
SharePoint 2010 Web Apps to Claims
before upgrade.
We tested this approach and ran in to issues
with custom branding, InfoPath forms and
other bits.
Decided to incorporate the conversion with
our upgrade.

15. SharePoint 2010 Classic to Claims
http://old.companyabc.com
COMPANYABCSHAREPOINTADMIN

16. SharePoint 2013 Classic to Claims

17. Path based for example is
http://myserver/sites/site
HNSC for example is
http://site.mydomain.com/
The only out of the box approach to
switch between the two which is
documented on TechNet is to complete a
backup and restore.

18. Step 1: Create a class mode web application in
SharePoint 2013
Step 2: Mount the SP2010 Content Database
Step 3: Convert web application to claims
My upgrade approach five steps

19. Step 4: Backup Site Collection
Step 5: Restore Site Collection
My upgrade approach five steps
(cont)

20. demonstration

21. Issues connecting to webservices such as
GetUserProfileByName
Hunt in the logs shows requests are
prefixed with claims 0#.w| which were
being rejected
Solution is to move the data connection
to the secure store
Now web service authenticates as secure
store account
Fixed with some InfoPath Rules!

22. This is the hero button:
If it looks like this drag and drop will not
work
Big issue we had, button would not work
on Form library's if drag and drop would
not open.
Two Options to stay Microsoft and get
drag/drop working
Install Office 2013
Install IE10

23. App Model URLs are in the following
format:
https://app-{guid}.app.beachenergy.com.au
RFC restrictions means a
*.beachenergy.com.au SSL certificate will
not be valid
To overcome this we will be purchasing a
new *.app.beachenergy.com.au certificate
and have to create a separate web
application just for apps (if/when they
take off)
Note: Access Runs as a App

25. May be a showstopper for some of you
Used in some of our upcoming
development so not a big deal at the
time
Good news: confirmed fix to ship in
August CU
Broken in Office 365 too… bad luck until
they fix it

26. gristy@gmail.com
http://cube4.com.au

27. Major Sponsors Minor Sponsors