How to Use and Configure Device Channels

SharePoint 2013: How to Use and Configure Device Channels

Browsing the web on a mobile device is now so common that a SharePoint site must be optimized for readability and ease of use on smartphones and other mobile devices such as tablets. With device channels in SharePoint 2013, you can render a single publishing site in multiple ways by using different designs that target different devices. This article can help you plan for using the device channels feature in SharePoint 2013.
Device channels are available only for SharePoint 2013 publishing sites. Before you implement device channels, you should already have a general understanding of the parts of a SharePoint site, how a SharePoint page is put together, and a general understanding of design manager. For more information about the SharePoint page model, including master page and page layouts, see Overview of the SharePoint 2013 page model  .
A device channel is part of the SharePoint 2013 publishing infrastructure that enables you to render certain site content, style your content, and even change images—while maintaining the same URL across a pool of different devices. Compared to the desktop version of the SharePoint site, a mobile rendering can be formatted with a smaller width, have better navigation with wider touch targets, and show a reduced amount of information for better usability. You can create a single site, and author and edit the content a single time for all your different mobile devices. When a user browses a SharePoint site from a mobile device such as a smartphone or tablet, the mobile browser submits to the site an HTTP GET request that includes a user agent string. This string contains information about the type of device that is trying to access the site. Based on that device substring, the device browser can be redirected to a specific master page view. For example, if you have a collection of Windows Phone and iPad devices, you can provide each pool with a unique rendering of the SharePoint publishing site by using device channels. These device channels can each be given a different master page and thus CSS file to give users a more optimal viewing experience. Figure 1 shows the use of two device channels to provide two unique site renderings for a phone and tablet device.

 

Configuring Device Channels

 

Before configuring anything on our SharePoint site, we have to be sure that the publishing feature is activated on our Site Collection Level. We are going to do a test now for 2 different browsers and see if tDevice Manager can make the difference and apply different masterPages.

 

Go to your Site Settings and select Design Manager.

 

 

We have to create a new Device Channel, so click on Manage Device Channels.

 

 

And now on Create a Channel

You can go now on http://whatsmyuseragent.com/  and take a look to your browsers information. Please copy the same on SharePoint Device Channels. You should create one for IE and one for Chrome.

 

 

 

When finished with creating with your Channels, go to Look and Feel and select Master Page.

For each Channel that we created, provide a (custom) MasterPage.

Thats it, you can now browse to your site with IE or Chrome and you should see for each version another MasterPage.  

What is a Device Channel?

What is a Device Channel?

A device channel is part of the SharePoint 2013 publishing infrastructure that enables you to render certain site content, style your content, and even change images—while maintaining the same URL across a pool of different devices. Compared to the desktop version of the SharePoint site, a mobile rendering can be formatted with a smaller width, have better navigation with wider touch targets, and show a reduced amount of information for better usability. You can create a single site, and author and edit the content a single time for all your different mobile devices. When a user browses a SharePoint site from a mobile device such as a smartphone or tablet, the mobile browser submits to the site an HTTP GET request that includes a user agent string. This string contains information about the type of device that is trying to access the site. Based on that device substring, the device browser can be redirected to a specific master page view. For example, if you have a collection of Windows Phone and iPad devices, you can provide each pool with a unique rendering of the SharePoint publishing site by using device channels. These device channels can each be given a different master page and thus CSS file to give users a more optimal viewing experience.

Design Channel

To manage Device Channels you need to use the following steps. This step helps you to create the device Chanel at the batter way.

• To manage the device channel the site collection must be either have publishing portal site template or activate the publishing Infrastructure feature at the site collection level as well as the web level.
• Navigate to the Site Settings under Look and Feel section Design Manager.
• You need to identify the type of
• Identify the type of device your site going to run.
• When you create a device channel, you specify the user agent substrings for the devices that you want the channel to target. This gives you fine-tuned control over what devices (or browsers) are captured by each channel. Then you assign a master page to that channel; in turn, each master page links to its own style sheet where the layout and styles are optimized for that type of device.
• To Check the Agent Information “http://www.useragentstring.com/pages/useragentstring.php” site give you the information about the user agent.
• Navigate to the device Manager and Click to “Manage Device Channels”. Click “Create a Channels” to add new channel. For change the order of the channel click “Edit or reorder existing channels”.
• Click “Create a channel” you will see the below screen. It has the “Name” , “Alias” , “Description” and “Device inclusion rule” fields. Below table shows the fields name and it req. value and value of that filed.

Field	Req. Value	Value
Name	Yes	This is the name of your design channel. It can be a friendly name to identify the channel.
Alias	Yes	The alias name enables you to identify your device channel in code, device channel panels (discussed later in this article), previews, and other contexts. Note: If you later change the channel alias, you'll have to manually update master page mappings, device channel panels, and any custom code or markup.
Description	No	A field for supplying a general description for the device channel.
Device Inclusion Rules	Yes	A field for supplying the user agent substring such as Windows Phone OS. Device redirection to a specific master page depends on what is entered for this value.
Active	No	Selecting this check box activates your device channel. If you are working on a live site, you should not activate the channel before you have finished designing it. For testing, you can use the query string ?DeviceChannel=alias within a browser to preview your site for a specific channel.

Design Manager: IE Device Channel Settings (Create New Device Channel)

• I have entered all the required information for “Internet Explorer”. I have enter Name as “Internet Explorer”, Alias without any special character and Space I give it a name “IE10”, Description give it about the channel, Device Inclusion rule I grabbed from this “http://www.useragentstring.com/pages/Internet%20Explorer/” URL and last Mark “Active” checkbox and save the settings.
• For Google Chrome device setting see the below screenshot.
• For iPhone device setting see the below image for the same.

• After a device channel is created and activated, device redirection to a specific master page, for example a mobile version, is possible. The next step is to specify what master page should be displayed for mobile devices at the site level, through either the Site Master Page Settings or by using the Publish and Apply option in Design Manager.

Set Master Page

To Change a Device Channel

Use this procedure to create a new device channel.

1. Start Design Manager. (For example, on the Settings menu, choose Design Manager.)
2. In the numbered list, select Manage Device Channels.
3. On the Design Manager: Manage Device Channels page, choose Edit or reorder existing channels.
4. In the Device Channels list, select the device channel that you want to change, and then, on the ITEMS tab, choose Edit Item.
5. To change the name of the device channel, enter a new name in the Name text box.
6. To change the alias of the device channel, enter a new alias in the Alias text box.
7. Note: If you change a device channel's alias, you must manually change the alias in other places where you use it. For example, you must manually change the alias in custom code or markup, and you must manually change the mappings between the device channel and master pages.
8. To change the description of the device channel, enter a new description in the Description text box.
9. To change the device inclusion rules, edit the strings in the Device Inclusion Rules text box.
10. To make the device channel active, select the Active check box. To make the channel inactive, clear the Active check box.
11. Choose Save.

Delete a Device Channel

Use this procedure to create a new device channel.

Note: you cannot delete the default channel.

1. Start Design Manager. (For example, on the Settings menu, choose Design Manager.)
2. In the numbered list, select Manage Device Channels.
3. On the Design Manager: Manage Device Channels page, choose Edit or reorder existing channels.
4. In the Device Channels list, select the device channel that you want to delete.
5. On the ITEMS tab, choose Delete Item.
6. Choose OK.

To reorder the Device Channel

Use this procedure to create a new device channel.

1. Start Design Manager. (For example, on the Settings menu, choose Design Manager.)
2. In the numbered list, select Manage Device Channels.
3. On the Design Manager: Manage Device Channels page, choose Edit or reorder existing channels.
4. On the ITEMS tab, choose Reorder Channels.
5. On the Device Channel Reordering page, choose the channel whose order you want to change, and then select Move Up or Move Down.
6. After the channels are ordered the way that you want them, choose OK.

 

 

 

 

Why Design manager?

Why Design manager?

1. SharePoint Designer 2013 is no longer the preferred tool. There is no longer a “Design” view for pages. It is only available in CODE View.
2. With Design Manager, you can convert an.html file into a SharePoint 2013 master page, a .master file. After the conversion, the HTML file and master page are associated, so that when you edit and save the HTML file, the changes are synced to the associated master page.
3. This tool’s purpose is to give users a new and easy way to brand SharePoint. The goal was to allow designers to create the look and feel for a SharePoint site using the tools they are most comfortable with like Dreamweaver or Visual Studio.
4. In SharePoint 2013, Design Manager can help web developers and designers build and export the visual design of a SharePoint site collection as a package. This package can easily be distributed to customers, or other designated groups, for installation on their site collections. This new feature reduces the complexity of transporting designs, and makes it easier for customers to outsource the visual design of their sites.
5. Device Channels that are part of the Design Manager now. The ability to have multiple designs based on browsers or devices. Ensure a consistent visual experience across all device platforms in your organization.

The Look and Feel Section in SharePoint Site Settings

Look and Feel Section.

 

• Title, Description, and Logo is where you can change the title of your site, add or edit the description, and insert a logo. Just changing the title and logo is often enough to make a business site your own. With this simple change, your site looks professional and unique to your team or organization.
• Quick Launch enables you to configure the navigation on the left side of the page. You can add headings, links, and change the order.
• Top Link Bar enables you to configure navigation at the top of the page.
• Tree View is where you enable or disable the Quick Launch (left navigation) or turn on a special type of navigation on the left side that shows a tree of the site’s content.
• Change the Look is where you choose the colors and design of the site. There are some exciting and outrageous looks such as Sea Monster and Immerse. The looks available to choose from are in the Composed Looks gallery.
• Design Manager is a web-based tool that you can use to create your own SharePoint site designs. The tool is wizard based and walks you through uploading design files, editing your master page, changing page layouts, and publishing and packaging your design.
• Device Channels enables you to specify certain characteristics of your site based on the device used to view the site. A channel can be optimized for the device to display the site in a specific way.
• For example, you can set up a channel for smartphones (such as an iPhone or Windows Phone). You could set up a different channel for the iPad or Surface tablets. And finally, you can set up a channel for laptops and desktop browsers.
• Import Design Package enables you to import a design package developed by a third party or in-house designer.

• Navigation enables you to manage navigation links and also change how the navigation behaves. You can configure global navigation (top of page) and also current navigation (left side of page). The Navigation settings page also enables you to change the sorting order of the navigational links and show and hide the Ribbon.
• Master Page is where you choose which master page the site uses and which master page the system uses. The system master page is for pages used by the system, such as when you view an app.
• Page Layouts and Site Templates enables you to control which page layouts and site templates are available for users of the site. All the page layouts are contained in a gallery. This settings page enables you to limit the page layouts and site templates that users of the site can use.
• Welcome Page is the landing page for a publishing site. You can use this settings page to determine which page should be used for the landing page.
• Image Renditions is where you determine how images and video should render. You can choose a particular width and height for each type of image or video.

Overview of the SharePoint 2013 page model

Introduction to the page model

---

Before you design or brand a SharePoint site, you need a basic understanding of the parts of a SharePoint site and how a SharePoint page is put together. This article gives you a visual overview of the pieces to think about as you plan how to brand your site. This article applies specifically to publishing sites in SharePoint 2013.

Master pages, page layouts, and pages

---

SharePoint uses templates to define and render the pages that a site displays. The structure of a SharePoint page includes three main elements:

• Master pages define the shared framing elements—the chrome—for all pages in your site.
• Page layouts define the layout for a specific class of pages.
• Pages are created from a page layout by authors who add content to page fields.

Figure 1. Master page, page layout, and page

Master pages

A master page defines the chrome (the shared framing elements) of your site. These elements may include the header and footer, top navigation, breadcrumbs, search box, site logo, and other branding elements. The master page remains consistent as visitors navigate through your site.

Figure 2. Master page

A master page also defines regions called content placeholders that are filled in by content from matching regions on page layouts. Most commonly, the body of a master page contains just a single content placeholder (named PlaceHolderMain, which is created automatically), and all of the content from a page layout appears inside this one content placeholder (the PlaceHolderMain content placeholder is outlined in red in Figure 3).

Figure 3. Master page with page layout outlined

When you preview a master page in Design Manager, you see the following message. This <div> resides inside the main content placeholder. Put simply, the master page defines the chrome of a page, and the page layout defines the body contained in the main content placeholder.

Figure 4. Master page preview message

Page layouts

A page layout is a template for a specific type of page in your site, such as an article page or a product details page. Just like its name implies, you can think of a page layout as defining the layout or structure for the body of a page.

Figure 5. Page layout

Page layouts define regions or content areas that map to content placeholders on the master page (outlined in red in Figure 6). Again, the most common scenario is that a page layout defines a single content region that maps to the single content placeholder that is created automatically on a master page.

Figure 6. Content region and content placeholder

Page field controls

The primary purpose of a page layout is to arrange page fields. When you design a page layout, you insert, position, and style elements called page field controls. These controls will eventually contain content when an author creates a page based on that page layout. In addition to page fields, page layouts can also contain Web Part zones, to which content authors can add Web Parts. (Master pages can't contain Web Part zones.)
With a page field control, you can define the styles used by the content. Authors can add content to a page, but the designer has ultimate control over how that content is rendered through CSS applied to those controls.

Figure 7. Page layout with page field controls

Every page layout is associated with a content type in the Pages library of a site. A content type is a schema of columns and data types. For any page layout, the page fields that are available for that layout correspond directly to the columns defined for that page layout's content type.

Relationship of master pages and page layouts

Together, a master page and a page layout create a content page.

Figure 8. Master page with page layout

The master page defines the chrome for all pages in the site so, often many page layouts (and therefore many pages created from those page layouts) are associated with one master page.

Figure 9. One master page tied to three page layouts

But, your site will likely use multiple master pages. For example, in addition to the default master page, you may have one or more master pages that target specific devices such as smart phones or tablets. In this case, one page layout is used by many master pages (see the section about device channels).
You can use one master page per channel per SharePoint site.

Pages

Authors can create pages and add content to the page fields, and they can add Web Parts to any Web Part zones or Rich Text Editors. Pages are structured so that content authors cannot make changes outside of page fields.

Figure 10. Page with authored content

The rendered page is what site visitors see. When a page is requested by the browser, the master page is merged with a page layout to create a content page, and the content for that page is merged into the page fields from that page in the Pages library.

Figure 11. Rendered page in browser

Figure 12. Master page, page layout, and page

Search-driven Web Parts and display templates

---

The previous section explains the SharePoint page model in terms of master pages, page layouts (with page fields), and pages. These elements are the most common in a publishing site in which authors regularly create and publish new content. When it comes to surfacing that content on your site, though, a couple more elements come into play. Whether you have connected to an external catalog or simply want to show a particular set of search results, search-driven Web Parts can help you achieve your goal.
In the search-driven pages scenario, a SharePoint page contains these main elements:

• Master pages
• Page layouts:
  
  • Regular page layouts that you created for specific content types, as described previously in this article
  • Category and item details page layouts that are created through cross-site publishing of a catalog
• Pages
• Search-driven Web Parts, such as the Content Search Web Part
• Display templates to control which managed properties appear in the search results of a search-driven Web Part, and control the styling and behavior of those search results:
  
  • Control display templates, which control the layout of search results and any elements common to all results such as paging, sorting, and other links
  • Item display templates, which control how each search result is displayed and repeated for each result

Figure 13. Master page, page layout, and page with Web Part

Search-driven Web Parts

With search-driven Web Parts, you can dynamically present information stored in the search index. The presentation of data in the Content Search Web Part is controlled by display templates, which reside in the Master Page Gallery alongside master pages and page layouts.
SharePoint Server 2013 includes several ready-to-use display templates such as lists and slideshows for your Content Search Web Parts. When you configure a Content Search Web Part in the browser, you choose which display templates to use.

Figure 14. Tool pane of Content Search Web Part

Content Search Web Parts use two types of display templates, control and item. As part of the design or branding of your site, you can create custom display templates that use layouts, styles, and behaviors that you define.

Figure 15. Two diagrams of Content Search Web Parts

Control display template

The control template determines the overall structure and layout of how you want to present the search results, such as a list with paging or a slideshow. Each Content Search Web Part uses one control template.
The control template also includes functionality common to all the search results, including paging, sorting, view options, and separators.

Figure 16. Control template outlined on Web Part and webpage

Item display template

The item template determines how each result in the set is displayed, and the template is repeated for each result. An item template can display an image, an image with text, a video, and other content.
The item display template also determines which managed properties and values are displayed by the Content Search Web Part. In this example, the item template displays three managed properties: a small-sized image, a product name as a hyperlink, and a brief text description.

Figure 17. Item templates outlined on Web Part and webpage

Device channels and device channel panels

---

In SharePoint 2013, you can use device channels to render a single publishing site in multiple ways by using different designs that target different devices. You create a single site and author the content in it a single time. Then, that site and content can be mapped to use different master pages and style sheets to target a specific device or group of devices.
When you design for more than one device, consider these elements:

• Device channels:
  
  • By using different master pages and CSS per channel, identical page content can be presented in different ways for specific devices (for example, Windows Phone) or groups of devices (all smart phones).
• Page layouts:
  
  • If the content does not change, you use the same page layouts for all device channels, though they can be styled differently based on the CSS of the different master page for each channel.
  • If you want to include content only for specific devices, use device channel panels.
• Pages

Device channels

When you create a device channel, you specify the user agent substrings for the devices that you want the channel to target. This gives you fine-tuned control over what devices (or browsers) are captured by each channel. Then you assign a master page to that channel; in turn, each master page links to its own style sheet where the layout and styles are optimized for that type of device.

Figure 18. Two device channels with separate master pages

You can accomplish a great deal using only CSS. It is possible for the master pages for two different channels (for example, desktop and phone) to be identical except that they link to different style sheets. The CSS files simply use different styles for the same page elements.

Relationship of master pages and page layouts

Unlike master pages, you do not specify different page layouts for different device channels. All page layouts work with all channels that you create. Thus, one page layout applies to many device channels and master pages.
This is one of the primary benefits of device channels: the design changes (the master page and CSS), but the content stays the same (page layouts and pages). But, you can vary what content from a page layout is displayed across different channels by using device channel panels (see the next section).

Figure 19. One page layout working with two master pages

Device channel panels

A device channel panel is a control that you can add to a master page, page layout, or display template to control what content is rendered in each channel. A channel panel is basically a container that specifies one or more channels; if one or more of those channels are active when the page is rendered, all of the contents of the channel panel are also rendered. A channel panel can include any type of content, including a link to a CSS file or a .js file, and is an easy way to include specific content for specific channels.
Perhaps the most common scenario for using channel panels is to selectively include parts of a page layout for specific channels. For example, you may have a page layout with separate text fields for a long greeting and a short greeting. By placing the page fields inside channel panels, you can display the short greeting only to phones and the long greeting only to desktops. The content of a device channel panel is not displayed to channels that it doesn't include—and the content inside that device channel panel is not rendered at all, which prevents bytes from going across the wire.

Figure 20. Page layout with channel panels

You can also use channel panels on master pages. For example, if you have a master page that can accommodate two different devices (or two different browsers) with only minimal changes, you can use channel panels to hold the content on the master page that is specific to each of those devices.
Or, you can use a channel panel inside the item display template of a Content Search Web Part, to display additional managed properties for that item from the catalog only for desktops and not for phones.

Figure 21. Page layout and item templates with channel panels

Navigate up (breadcrumb)

Navigate up (breadcrumb)

 

To add this one to your SP2013: edit the master page (or actually the html). Look for a div with the css class ‘ms-breadcrumb-top‘.

 

 

For some reason this ‘PopoutMenu’ control has the  attribute ‘visible’ set to ‘false’. Remove the complete attribute or replace the visible=”false”  by Visible=”true”

The result will be an icon that when clicked results in a breadcrumb pop out.

 

 

 

Install and Download SharePoint 2013 prerequisites offline

This article applies in a situation when you don’t have internet access in your SharePoint server , I have placed all the direct download links for the installers you might need.

This article assumes you are having a new fresh installation of windows server 2008 R2 SP1
If you tried to run the installer , The following should be installed (but you cant install them directly from here since you don’t have internet)


in this case  you can download and install SharePoint 2013 Prerequisites offline and run them manually as below:
I have placed what needs to be installed on a clean Window server R2 SP1 , you should not need more than this:

Prerequisite	Direct Link
Microsoft .NET Framework 4.5 (Full Stand alone package)	http://go.microsoft.com/fwlink/?LinkId=225702 Or Download tFx45_Full_x86_x64.exe from stand alone section from http://msdn.microsoft.com/en-us/library/5a4x27ek.aspx
Windows Management Framework 3.0	http://www.microsoft.com/en-us/download/details.aspx?id=34595
Microsoft SQL Server 2008 R2 SP1 Native Client	Download 1033\x64\sqlncli.msi from http://www.microsoft.com/en-us/download/details.aspx?id=26728
Windows Identity Foundation (KB974405)	http://go.microsoft.com/fwlink/p/?LinkID=226830
Windows Identity Extensions	http://go.microsoft.com/fwlink/?LinkID=252368
Microsoft Sync Framework Runtime v1.0 SP1 (x64)	http://go.microsoft.com/fwlink/p/?LinkID=224449
Windows Server AppFabric	http://go.microsoft.com/fwlink/?LinkId=235496 (Note: don’t install WindowsServerAppFabricSetup_x64_6.1 this is not the correct version that SharePoint installer seeks) Download it but don’t install it by yourself since it needs configuration, hence install all other prerequisites in this article (except this one) then let the prerequisite installer to install AppFabric and configure it manually for you by running the following command from command prompt: prerequisiteInstaller.exe /appfabric:[Full AppFabric Installer path] D: is the CD drive where SharePoint installer is placed
Microsoft Information Protection and Control Client	http://go.microsoft.com/fwlink/p/?LinkID=219568
Microsoft WCF Data Services 5.0	http://www.microsoft.com/en-us/download/details.aspx?id=29306
Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB2671763	Download AppFabric1.1-RTM-KB2671763-x64-ENU.exe from http://www.microsoft.com/en-us/download/details.aspx?id=29241 You need to Install AppFabric from above first then run this update, dont run this update if appFabric above is not installed yet

Cannot display the webpage while creating a Web Application in SharePoint

Cannot display the webpage while creating a Web Application in SharePoint

I was creating my fifth Web Application in our SharePoint 2013 test environment when I received the following error during creation:
“Internet Explorer cannot display the webpage”

Microsoft has published an article related to this issue in SharePoint 2010 http://support.microsoft.com/kb/2543306.
Cause (from Microsoft)
As more and more web applications are created, the time in which it takes to create a web application increases. As part of the creation process, IIS is reset and by default, the application pool allows 90 seconds for the connections to close off before forcibly shutting down. When the number of web applications grows above 10, 90 seconds is not enough time for the provisioning to finish. Resolution (from Microsoft) The solution to this is to allow the process a longer amount of time before it is forcibly shutdown.

• On the server(s) hosting Central Admin, open IIS manager.
• In the tree view, expand the server name and click on Application Pools.
• Locate the SharePoint Central Administration v4 application pool. Right click on it and choose Advanced Settings.
• In the Process Model section, set the Shutdown Time Limit to a greater value. As an example, 300.
• Restart IIS.

install and configure SharePoint 2013

TechNet articles about how to install and configure SharePoint 2013

The following articles about how to install and configure SharePoint 2013 are available to view online. Writers update articles on a continuing basis as new information becomes available and as users provide feedback.

Content	Description
Install SharePoint 2013 on a single server with SQL Server	Describes how to install SharePoint 2013 on a single server. This deployment uses SQL Server and can easily be scaled out to create two- and three-tier farm topologies.
Install SharePoint 2013 on a single server with a built-in database	Explains how to install SharePoint 2013 on a single server. This deployment uses SQL Server Express and is typically used for evaluating SharePoint 2013.
Install SharePoint 2013 across multiple servers for a three-tier farm	Describes how to install SharePoint 2013 on multiple servers. This deployment uses SQL Server and the resulting three-tier topology provides the foundation for implementing any solution.
Install and configure a virtual environment for SharePoint 2013	This article describes how to use Windows PowerShell to install SharePoint 2013 in a Hyper-V environment.
Install or uninstall language packs for SharePoint 2013	Describes language packs and how to download, install, and uninstall them.
Add web or application servers to farms in SharePoint 2013	Explains how to add a web or application server to a farm. The procedures in this article apply to a SharePoint 2013 farm that consists of at least two tiers. They should not be used for converting a single server deployment to a multiple server farm.
Add a database server to an existing farm in SharePoint 2013	Provides information about how to add a new database server to an existing SharePoint 2013 farm.
Remove a server from a farm in SharePoint 2013	Describes how to remove a web server, application server, or a database server from a SharePoint 2013 farm.
Uninstall SharePoint 2013	Describes how to remove SharePoint 2013 from a computer.
Install and configure a virtual environment for SharePoint 2013	Learn about permissions, accounts, security settings, and what you have to do to prepare your Windows Server 2008 Hyper-V environment for SharePoint 2013.

 

Install and Configure SharePoint Server 2013 Step by Step

1) Download : SharePoint Server 2013
2) Mount ISO file. and start installation process.

Before starting installation SharePoint Server, need to install software prerequisites.
So click on Install software prerequisites.
Note : you need active internet connection.Because it downloads updates from Microsoft Download Center.

Accept and terms and licence agreement and go next.

Once installation of Prerequisite is done. Click on Install SharePoint Server
 
Enter product key and Continue.
Accept Terms and Continue.
Keep Path of Server as it is and click on Install Now
l
This will install SharePoint Server on your machine.

Next step is to Run the SharePoint Configuration Wizard

By clicking on Close button, Wizard will run. If you want to run it later you can find it in start menu.

Click on Next.

Click on Yes.

Select Create a new server farm. and click Next
Enter Database server name (Server name on which SQL Server is installed).
Username : zsdev\svcSPFarm (which I’ve created in Active Directory) This Service Account will have full access on
SharePoint Config Database
Password : (Password set for svcSPFarm account)

 

SP13 is the server name where SQL Server is installed. click Next
Enter Passphrase. and don’t forget it. because next time when you will need to reconfigure farm at the time of update installation. It will ask you for Passphrase.


Specify Central Administration Portal port. you can change it if you want.
keep authentication provider : NTLM


I’ve change port number to 34000 from 17685.

Click Next.



and Configuration is completed.

Click on Finish button. This will open Central Admin web page.



Click on Cancel button for SharePoint Configuration Farm. It will redirect you to Central Administration.