Upgrade from SharePoint 2010 to SharePoint 2013

The upgrade from SharePoint 2010 to SharePoint 2013 can only be done using the Database-Attach method. 
The upgrade process is composed by three steps : 
  • Prepare for upgrade
  • Upgrade Database
  • Upgrade Sites

Click here to view the SharePoint 2013 Upgrade process



PREPARE 2013 FARM (See msdn)

Phase 1 of the upgrade process: Create SharePoint 2013 farm


  • Upgrade services applications to SharePoint 2013 (See msdn)
  • Upgrade Content database (See msdn)
  • Verify upgrade for databases (See msdn)
  • Migrate from classic-mode authentication to claim-based authentication (See msdn)


Installing my SharePoint Server 2013 Farm – Part 2/6

Installing the Farm Domain Controller (AD DS)

This tutorial is the part 2 of the series « Installing my SharePoint Server 2013 Farm ». The series is as follow :
In this tutorial we will install the Farm’s Domain Controller. In the previous post we’ve created a virtual machine that we’ve called “AD-VM-SV01”. We will use it to install the “Active Directory Domain and Services” Role.
The steps bellow will guide you to install the AD-DS role.
-        Start the virtual machine “AD-VM-SV01”
-        Open the “Server Manager” then click on “Local Server”
-        Click on the current computer Name, the “System Properties” window will display
-        Click on “Change” button
-        The “Computer Name/ Domain Changes” window appears.
-        Enter “AD-VM-SV01” in the computer name text box.
-        Restart the virtual machine when asked to.
Before starting the AD-DS role installation, you have to set a static IP address for the network card. Open the “Network and sharing center” , click on you current “Active Connections” and then set an IP address.  In the DNS field put
In previous versions of Windows Server we used to use the DCPROMO command in order to install a new “AD-DS and DNS”. In Windows Server 2012 this has been made easier using the “Roles and Features” setup screen.
-        Once the machine started, open the “Server Management console” and click on “Add Role and Feature” under the “Manage” button.
-        As we’ve seen in the previous tutorial, you have to select “Role based or feature based installation” and then choose the target machine which is your local server.  This server will be promoted as domain controller.
-        In the role list, check “Active Directory Domain and Service” role. A new dialog will appear to install dependent features. Click “Add Features”
-        The Active Directory Domain and Service page will appear in which you’ll get the summary of the role.
-        Click “Next” and you will get a screen to begin the “Installation Process”
-        Click “Install”
After the installation process finishes, a new link will appear “Promote this Server to a Domain Controller”. Click on the link to make the server a domain controller.
-        The “Active Directory Domain and Service configuration Wizard” appears. We have to choose a deployment configuration. Since this server is the first Domain Controller in your virtual environment, we’ll select “Add new forest”. A textbox will appear to set the root domain name. In this tutorial I’ve used “factory.local”
In the Active Directory directory service, a forest is a set of naming contexts (NCs) consisting of one schema NC, one config NC, and one or more domain NCs. Because a set of NCs can be arranged into a tree structure, a forest is also a set of one or several trees of NCs. (see msdn)
-        Click “Next” to move to the “Domain Controller options” screen.
-        You have to select the “Forest functional level” and the “Domain functional level”. In both lists we will select “Windows Server 2012”
The fact that this server is the first domain controller in a new forest explains why the “Global Catalog GC” is checked and the “Read Only Domain Controller RODC” is unchecked as well as why both of them grayed.
The global catalog is a distributed data repository that contains a searchable, partial representation of every object in every domain in a multidomain Active Directory Domain Services (AD DS) forest (see technet)
-        Make sure to check the “Domain Name System DNS Server” to install the DNS Role on the same machine.
-        Type and confirm a password for the active directory restore mode.
-        Click “Next” to move to the DNS options page. A warning will appear indicating that a delegation for the DNS Server cannot be created. Don’t worry about that, this is because DNS Service is not installed yet.
-        Click “Next” to move to additional options page. In the NetBIOS textbox type “AD-VM-SV01” and click next to move to the AD DS files locations page.
-        Keep files locations as they are. You can change them if you want. Click “Next”
-        The “Prerequisites” page appears. Some warnings appear in the results view, just check at the top of the screen if a successful message appears “All prerequisites checks passed successfully, click “Install” to begin the installation.
Once installation finishes, restart the computer and logon using the account: factory\administrator
Now you have successfully installed your farm domain controller. Next step is to add the SQL and SharePoint machines to the recently installed domain controller.

Installing my SharePoint Server 2013 Farm – Part 1/6

Creating the Farm virtual machines

This tutorial is part of a series to be published progressively and that i’ve called « Installing my SharePoint Server 2013 Farm »
The purpose of these 6-parts tutorial series is to install sharepoint 2013 server farm following the best practices.
The series will be as follows:
In all these tutorials i’ll use a « Lenovo ThinkCenter » desktop which has the following configuration :
  • 500 GB HDD
  • 16 GB RAM DDR 3
  • Core I5 CPU @ 3.2 Ghz
Lets start with the first Tutorial which is : « Installing Hyper-V Server and creating virtual machines ».
Prerequisites :
-          Windows Server 2012 Standard Edition.
At the End we’ll get :
-          A Windows 2012 Host Machine with Hyper-V Role installed and running 3 Child Machines
The Hyper-V Virtualization in Windows Server 2012 uses a  type 1 Virtualization in which the hypervisor interacts with the machine’s hardware. The Host machine OS and the Child Os runs at the same level with a difference ; the Host machine is running the Hypervisor stack to be able to create and manage child virtual machines.
Hyper-V Role is only available in « Standard » and « Datacenter » Editions of Windows Server 2012.
Before Installing the Hyper-V Role make sure that your computer meets the following requirements
X64 Processor that supports Hardware virtualization such as (Intel VT or AMD-V)
The machine BIOS Supports Hardware virtualization and make sure you enable it
Enable the Execute Disable bit (XD bit on Intel) or  Enable the no execution bit (NX bit on AMD)

Installing Hyper-V Role

To install the Hyper-V Role just follow the steps bellow :
  •     Click on Server Management Icon at the bottom of the screen
  • Click on « Manage » then « Add Roles and features »
  • Click « Next » in the first Screen
  • Select  « Role based or featured-based  installation »
  • Select your server from the server pool
In windows Server 2012 you can install role and feature on an offline Windows Server 2012 VHD.  In this tutorial we will select the server from the server pool.
  • Select the « Hyper-V » from the server roles list
You will be asked to install additionnel features that are required to manage the Hyper-V role. Click on « Add Features »  and then click next to open the selection features list
  •  In the « Create Virtual Switches» page, select the network card you want to use.  Click next.
  • The « Virtual Machine migration » page opens, click next.
  • The default store page opens. You can specify where you want to store your virtual disks and the machines configuration files.
  • Click « Install » to start installation of the Hyper-V Role. Now you have to restart the machine.
Once Hyper-V role is installed, we can start creating our virtual machines. We have to create 3 VM for our SharePoint Server Farm.
  • 1 VM : Domain Controller
  •  1 VM : SQL Server 2012
  •  1 VM : SharePoint 2013

Creating virtual machines

We can now start creating the Domain Controller Machine.
To create a new Virtual machine open the Hyper-V manager console
On the « Action » pane in the Hyper-V manager console click on
  • New -> Virtual Machine
The virtual machine creation wizard opens, follow the steps bellow to create the first machine
  • Click « Next » in the first screen of the wizard
  • A new screen shows up to specify the name of the virtual machine
Once you specify the name, click next.
  • The memory assignation screen appears. In this screen you have to specify whether the memory is static or dynamic, the memory amount that you want to use for it based on the physical machine memory. After creating the virtual machine you are also able to change the amount of assigned memory.
Choosing dynamic memory will let the hypervisor decide of the amount of memory assigned to the machine depending of the machines demands and the memory available in the shared memory pool. The startup Memory is the memory allocated for the machine when it starts. If you use a dynamic memory allocation , you can set the value of the startup memory equals to the minimum memory allocation. We will choose the « Use Dynamic Memory for this virtual machine ».  After you create the virtual machine you can open the machines’s settings interface  and change the « Minimum Ram » and the « Maximum Ram ».  The maximum Ram cannot be greater than 64 Gb. 
We will not use Dynamic Memory for SharePoint Server 2013 since it is not supported in all SharePoint features. (see Technet
  • Click « Next » to go the Network configuration screen
  • In the Network configuration screen you can choose which network card you will use in the virtual machine. Select a network card and then click « Next »
  •  The Hard disk creation/selection interface appears. In this screen you can
    • Create a new virtual disk with dynamic space allocation « vhdx »
    • Attach an existing virtual hard disk
    • Attach a virtual hard disk later
You can also choose to use a pass-through disk which is a virtual disk that points to a  physical machine disk. This disk should be taken offline in order to use it.
We will choose to create a virtual hard disk having the size of 60 GB for this domain controller machine.
  • Click  «Next » to select an installation options.
  • If the Windows Server 2012 DVD is in the physical machine optical drive, select the drive letter from the list « Physical CD/DVD drive » and if you have an iso file you can browse for it when selecting « Image File (.iso) » option.
  • Click « Next » and then « Finish » to close the wizard
Now repeat the same operations for the 2 remaining machines (SQL and SharePoint).  When you finish you will have the following VMs
Machine Name           Startup Ram       Minimum Ram        Maximum Ram     Disk space
AD-VM-SV01                 800 Mo                   800 Mo                       2500 Mo                 60 GB
SQL-VM-SV01               2500 M0                 2500 M0                    8000 M0                127 GB
SP-VM-SV01                  8000 M0                                                                                  127  GB