System Center Virtual Machine Manager 2012 R2

install System Center Virtual Machine Manager 2012 R2
Step by Step

1. Introduction:

I was curious about SCVMM  recently and thought I’d share in my blog this article of step by step installation notes for Virtual Machine Manager 2012 R2.
I’ve installed SCVMM in my lab using 5 virtual machines, the operating systems are Windows 2012 R2 Server.  My lab consists of a Domain Controller with an isolated domain, an SQL server required for SCVMM, a server that I will be using for the SCVMM Management Server and two VMs with Windows server 2012 R2 for testing.

2. features:

SCVMM 2012 R2 drops support for particularly old versions of Microsoft virtualization software, such as Virtual Server 2005. SCVMM 2012 R2 supports the versions of Hyper-V that are included in the following versions of Windows:

•  Hyper-V Server 2008 R2
• Windows Server 2008 R2
• Windows Server 2008 with Service Pack 2

A lot of features that are included in SCVMM 2012 R2:

•     Provisioning of new Hyper-V hosts.
• Intelligent Placement. Helps administrators identify a host that’s suitable for a particular workload.
• Cluster enhancements
• Dynamic Optimization. Migrates virtual machines within a cluster in order to load balance workloads and ensure adherence to placement rules.
• Power optimization.
• Hypervisor support for vSphere/ESX and Citrix XenServer.

3. Prerequisite:

If you have SQL Server separated in other server, you need to install on SCVMM server these:

• Microsoft® SQL Server® 2012 Native Client, download from here.
• SQL Server 2008 R2 Command Line Utilities, download from here.

You need to install Windows Assessment and Deployment Kit (Windows ADK) 8.1, download from here:

4. Installation SCVMM:

Now, start the installation

5. Hosts:

Let's add two hosts with hyper-v installed:

In "Fabric", click on "Add Resources" and "Hyper-v Hosts and Clusters"

Select first option:

Enter the names of hosts

Now you can see the hosts.

My next post will show how to create a private cloud with System Center Virtual Machine Manager 2012 R2.

Installing Power View SharePoint 2013 SP1 Step by Step

Installing Power View SharePoint 2013 SP1 Step by Step

1. Architecture:

I built up a demo environment for BI with Windows Server 2012 R2, SQL 2012 SP1 and SharePoint 2013 SP1.
This is primarily to take advantage of the new Power View enhancements that came out with SQL 2012 SP1.
What follows is a general guide, providing an overview of the main steps and links to other information where necessary.
I am focusing on the SQL and SharePoint install here.

Prerequisite steps that I performed were:

• Created a Virtual Machine (VM) Domain Controller.

• Created a VM Sharepoint 2013 server SP1.
• Created a VM SQL Server 2012.

• Joined the SharePoint 2013 and SQL 2012 VM to the domain.

• Understand how to deploy a tabular model to an Analysis Server 2012 machine because you will need to have an Analysis Services Tabular database for Power View to use as a source.  My blog post here can be used to help with SSAS Tabular.
• Create a user for install (it's recommended to create 4 users: one for SP install, two for SQL, three for sharepoint farm and four for sharepoint services). Here I'll use only one user for all, just to not be confused.

2. Installing SQL Server 2012:

Begin the installation by executing the setup from SQL Server installer:

Now, SQL Server is installed, we need to upgrade our server to SP1. You need to download the update "SQLServer2012SP1-KB2674319-x64-ENU.exe" from here.
After completing the download, execute your update program.

 

Our SQL 2012 Server is upgraded to SP1. Now we need to download "Cumulative update package 6 for SQL Server 2012 SP1" from here.
Again, execute the Cumulative update package 6 for SQL

Now, we are finish with SQL Server.

3. Installing SharePoint 2013 SP1:

Before begin the installation, make sure you're installing SharePoint 2013 SP1 on Windows Server 2012 R2-based environment , otherwise you'll get errors during installing prerequisites, see this article.
You must have Internet connection because SharePoint needs to download packages and configure them later.





3.1. Setting up a farm:
Execute SharePoint 2013 SP1

Create a new Farm

 

Enter the name of the Database Server. Specify the username/password (A user who has access to Database read/write)

 Entre a "Passphrase"

 

Now enter to"Central administration"

Problem and solution:

First time when you access to "Central administration" you can see "Manage service application" in "Application Management" but after reboot your server, it will be gone. So the cause is Windows Security, you need to run Internet Explorer as Administrator each time you want to get in. The solution is not recommended but if you want to open IE without asking "As administrator" you need to do this:

Go to "Control Panel" - "User Accounts"

"User Accounts"

"Change User Account Control settings"

Change it to "Never notify"

You need to restart your server.

3.2. Setting up an application web:

In "Central Administration" go to "Configuration Wizards" - "Launch the Farm Configuration Wizard"

Click on "Start the Wizard"

Specify the managed account and select the services you need on your application web

Enter a Title and URL, Choose the template: Enterprise - Business Intelligence Center 

Now, our web application is installed

3.3. Installing Reporting features

In SharePoint 2013 Server, execute the setup of SQL server 2012

Choose "Shared Features" 

• Reporting Services - Sharepoint
• Reporting Services Add-in for Sharepoint product

Now we are going to update SQL 2012 to SP1
Execute the update package you download it before in SQL Server "SQLServer2012SP1-KB2674319-x64-ENU.exe"

We need now to install "Cumulative update package 6 for SQL Server 2012 SP1". We already download it in SQL Server

3.4. Installing SQL Server Reporting in Sharepoint:

launch "SharePoint 2013 Management Shell" and execute these two commands:

Install-SPRSService
Install-SPRSServiceProxy

3.5. Configure SQL Server Reporing in Sharepoint:

In "Central Administration", go to "System Settings" - "Manage services on server"

Scroll down the page and start "SQL Server Reporting Services Service"

In "Central Administration" go to "Application Management" - "Manage service Applications"

Open "New" and select "SQL Server Reporting Services Service Application"

Enter a name to the application, create a new application pool, enter a name to the database and don't forget to check the Web Application Association.

Go to "site content" - "Site Settings"

In "Site Collection Administration", click "Site collection features"

Search for feature "Power View Integration Feature" and activate it.

Go back to Site Content

Click "Files" - "Report Data Source"

Select "Data Source Type" - " Microsoft BI Semantic Model for Power View"
Enter the Connection String:

Data source=SQL2012;Initial Catalog= AdventureWorksDW2012Multidimensional-EE;Cube='Adventure Works'

in "Credentials", select "Stored credentials", put the username/password of user who has access to the cube. Check "Use as Windows credentials"

Click "Test Connection"

Before creating a Power View report, you need to install Silverlight here. 

Double-click on Data Source Report created, you'll see power View interface. Now you can create your reports

Problem and Solution:

Many users ask why "Data Source Report" is missing in "Files". Because When you install RS SharePoint Add-in feature to your Web Front end using the SQL Server 2012 and Service Pack 1 media you wont see any errors about the content types not installing correctly.
We are going to install it manually, so follow the instruction carefully:

Execute the update package SQL Server SP1

See that the package in folder "c:\b050cfb28c1dcbeefb"

Go to this folder

Search for " rssharepoint"

Copy the folder in new location

Open a cmd command, go to "rssharepoint.msi"
Execute: Msiexec.exe /i rsSharePoint.msi SKIPCA=1

In cmd go to the "TEMP" folder

Execute: rsCustomAction.exe /i

Installing will begin

Finally "rssharepoint" is successfully installed

Now you can create a "Data Source Report"