Azure Pack configuration for Windows Server 2012 R2

So Microsoft has released the new wave of products into preview, including the next version of Katal (Azure Services) for Microsoft, called Azure Pack. This pack transforms your datacenter into Azure allowing users to sign up using plans and be able to use your infrastructure into a IaaS platform.

You can download the trial for Azure Pack here –> http://www.microsoft.com/en-us/server-cloud/windows-azure-pack.aspx

Now there are some prerequisites for using this pack.
You can read more about them here –> http://technet.microsoft.com/en-us/library/dn296442.aspx

But in order to integrate Azure pack with your on-premise solution it uses Service Provider Foundation (Which is included in the Orchestrator installation media)

image

Not that this requires the installation of SCVMM 2012 R2 Console on the same machine as SPF since it uses the VMM APIs to communicate with it.

It also requires some other prerequisites such as

image

WCF Data Services 5.0 can be found here –> http://www.microsoft.com/en-us/download/details.aspx?id=29306

.NET features 4.5 WCF is a part of .Net 4.5 which can be installed from Server Manager

Management ODATA IIS is also a part of 2012 R2 installation media

ASP.NET MVC 4 can be downloaded from here –> http://www.asp.net/mvc/mvc4

Next we configure a database for use for SPF

image

In this database the SPF stores information such as
Tenants
Usage Records
Gallery Items
Roles
Servers
And Tenants Stamps

Next we choose where to deploy the SPF files and what certificate we want to use.
In my case for this demo I used a self-signed certificate.

image

Next we define credentials for the admin web service

image

NOTE: If you choose Network Service here you need to make sure that the machine account is a VMM administrator

In my case I choose a Service Account and entered a domain user.
After that you are done with SPF

image

Next we move on to the Azure Pack installation
You can download the pack from here –> http://technet.microsoft.com/en-us/library/dn296435.aspx?CR_CC=200142594

All it does is download a profile which uses webdeploy.

image

Now by default it will install all the web roles on the same servere

image

Click I accept (ill come back to what the different roles do)
And Note this installing part may take some time.

After that is done, press Continue and ill will start the Service Management Configuration site.

image

It will open a browser window on the localhost on port 30101, and again we will have to define a Database and server for the Azure Pack.

Here you have the option to use a Windows user or a regular SQL user.
Remember that you have to enable Mixed Mode on the SQL server in order to use regular SQL users.

image

Make sure that you write down the passphrase. If you forget or lose this passphrase, there is no way to recover it. This is used to encrypt and decrypt the Configuration Store..

Next we define a FQDN for the host

image

After this is done it will start configuring the different roles on the Server

image

After that is done we continue on with the configuration

image

NOTE: You may need to log out of your system and log back in before you can access the management portal for administrators. This is due to Windows authentication and the need to add the security group to your security token.

If you continue to see an access denied error, even after logging back in, close all Internet Explorer windows, and run Internet Explorer as an administrator.

Now the setup will open a browser on port 30091 which is the default port for the management portal for administrators

image

 

Now you can see the difference between “Katal” and Azure Pack

Katal (The old version)

image

(Azure Pack the New one)

image

New stuff is including
Reporting provider (This is also a feature that is on the Orchestrator installation media)
Service Bus Clouds (Read more about setting up service bus here –> http://msdn.microsoft.com/en-us/library/windowsazure/dn282152(v=azure.10).aspx )
Automation (This requires Service Management Automation web service)

So in my case I define the Service Provider Foundation endpoint for Azure Pack
And then Go to VM Clouds and connect to my VMM Management Server.

Add some bugs when connecting to my cloud but after a IISreset it worked just fine

image

This gets the cloud container from VMM, from here I can view resources in my cloud

image

Now for the end-user I can sign up using the tenant portal.
Which is on the same server you installed Azure Pack only on port 30081 remember thou that you need to create a plan and publish it in order for users to subscribe to that plan.

Here I signed up with a regular user account

image

Choose Add Plan and select a public plan which was created on the management portal.
Note thou that here we have external users created we can also use AD authentication

For the tenant portal you can configure this using ADFS here –> http://technet.microsoft.com/en-us/library/dn296436.aspx#WAP_AddADFSAuth

Note when you sign up for a plan you need to go back to the administration portal and approve the subscription.

Now If I want to automate a task associated with VM create I can do this in the management portal

image

All for this time, all dive in a bit more when I got the time Smilefjes 
Stay tuned

#active-directory, #azure, #service-provider-foundation, #system-center-2012, #windows-server-2012, #windows-server-2012-r2

System Center 2012, SCCM part 1

Phuh! This easter has been alot to do, reading for my MCP exam and setting up my new home lab enviroment. So far I have setup most of the servers, they consist of:
1: AD + DNS
2:  SQL w/Reporting Services
3: SCCM w/DP, MP, Application web site point, PXE role, Reporting point (all in one)
4: SCVMM Management + Self Service Portal
5: SCOM w/Management Server
6: SCSM

So im going to start with the innstallation of SCCM 2012. I presume that you have a basic understanding of what SCCM is, if not I suggest heading over to Microsoft -> http://www.microsoft.com/en-us/server-cloud/system-center/configuration-manager-2012.aspx In short it is a system management framework, used to manage computers (Software deployment, patching, OSD, AV, Baselines and compliance, reporting ++++ )
Before we start with the installation be sure to check that you have either of these versions of SQL server installed.

  • SQL Server 2008 SP2 with Cumulative Update 9
  • SQL Server 2008 SP3 with Cumulative Update 4
  • SQL Server 2008 R2 with SP1 and Cumulative Update 4
  • The instance of SQL Server in use at each site must use the following collation: SQL_Latin1_General_CP1_CI_AS

To check what version of SQL server you have installed start SMSS, and then click About on the Help menu.
sccm1-sql
You can download the SCCM 2012 RC from here http://www.microsoft.com/en-us/server-cloud/system-center/configuration-manager-2012-trial.aspx

And then the Server that  is going to have SCCM installed needs
.Net 4.0 (http://www.microsoft.com/download/en/details.aspx?id=17851)
.Net 3.5 SP1 (servermanagercmd -install Net-Framework)
Remote Differencial Compression (Servermanagercmd -Install Rdc)
WSUS 3.0 SP2 If you are going to use it for Patch Management (Which im going to do )You also need to do some changes in Active Directory (You need a user with domain admin access to change this )  This is because SCCM will publish information in AD that the clients will access later (more info on that later). (You don’t have to to this if you want to but it makes it easier for the clients to find what server the agent should communicate to)

Perform this on a  Active Directory Domain Controller as a Domain Administrator

Open ADSI Edit, click on Action, Connect To and click Ok, Double Click on Default Naming Context and the DC= that appears below it. Click on the + and scroll down to CN=System.

Right Click on CN=System and choose New, Object
sccm-ad1

Choose Container from the options,
sccm-ad2
click Next and enter System Management as the value.
sccm-ad3
Click Next and Finish .Open Active Directory Users and Computers. Click on view, select Advanced Features.Select the System Management Container, and right click it, choose All Tasks and Delegate Control
sccm-ad4
When the Welcome to Delegation of Control Wizard appears click next, then click Add. click on Object Types, select Computers. Type in your SCCM server name and click on Check Names (It my case my server name is SCCM (I changed it later to configmgr) so therefore enter the name of your server here)
sccm-ad5

Click Ok, then Next. Choose Create a Custom Task to Delegate, click next, make sure This folder, existing objects in this folder and creation of new objects in this folder is selected.
click next, select the 3 permissions General, Property-Specific and Creation-deletion of specific child objectsare selected then place a check mark in FULL CONTROL, and click next then Finish.
If you don’t do this, you will recive some errors from the SCCM server and the agents  (Since by default SCCM tries to publish its information to AD)
Next we need to extended the AD schema, do this on your Active Directory server as well, browse the network to your sccm server \\sccm\isodrive$ and locate the folder where you uncompressed SCCM 2012 and find \SMSSetup\Bin\x64\Extadsch.exe, right click and choose Run As Administrator,
sccm-ad6
sccm-ad7
 
after you have done this there will be generated a log file on your c:\ ExtADSch.log so please check this for error before continuing, if it is successful it should look like this.
sccm-ad8

Now when you start the wizard, you have the option to download the prerequisites,  I suggest you start by download those to a local folder on the server since we need them later in the setup. 
sccm2

After they are downloaded continue with the install.

Since this is a new install, We choose the Install a Configuration Manager primary site (The other option, install Configuration Manager Central administration site also known as a CAS is used to centrally manage multiple CM sites. more on that later)
sccm-setup2
Since I don’t have a product key I choose evaluation
sccm-setup3
Accept the license terms
sccm-setup4
Accept more license terms
sccm-setup5

Browse the path to the previous downloaded prerequisites
sccm-setup6

I choose english here

sccm-setup7-language

Same here

sccm-setup8-language

Here we enter a site code, which consists of 3 letters, this site code is used as a boundary so the clients know that when it belongs to that particular site it should contact these servers. Much like when you live in Oslo, you know that you need to contact the local police station in case something happens 🙂
In the site name just type something relevant, this information will also appear in the application web portal we are going to install later.

sccm-setup9

Next I choose, install the primary site as a standalone site ( Since this is a singel domain )

sccm-setup10

Now enter the name of the SQL server (Need to make sure that port 1433, and 4022 is open in order for it to work ) (Also you need to give the computer account administrative access on the SQL server and on the server you are installing SCCM on. )

sccm-setup11-dba

 

review the SMS provider settings,

sccm-setup13

Client computer communication settings, select Configure the Communication method on each site system, since I don’t have a Root CA I need to choose http,

sccm-setup14

Next I choose to install a Management Point & Distribution Point on this site, that will communicate via http

sccm-setup15

Now you get the summary screen just doublecheck that this is correct and continue,

Next, now its going to check the prerequisites.  This consists of checking if the server has rights to publish information to AD, if the AD schema is populated with the new SCCM schema, if the SQL server is responding, if WSUS and/or AIK (You don’t need to have these installed since you might be using some other solution for patch management, so these will just give you a warning if you don’t have it installed) + some more. You can check the setup log file on C:\ drive and you can see what checks the setup does.

In my case I forgot to install WSUS, and I forgot to give the server administrative rights on the server, so I need to fix that before we continue (As you can see, we can’t continue until we fixed the problems that are listed as critical, you can have multiple warnings but still continue with the install )

sccm-setup16
sccm-setup17

Now that I’ve the previous steps, we only got some warning messages, So I continue with the installation (Since my SQL server is running on a low specced Virtual machine I get those error messages)

Voila, installation if complete, if I check in Active Directory now you can see that it has automaticly published information about that site.
sccm-setup19
sccm-setup20

PS: IF something went wrong during the installation doublecheck the log C:\ConfigMgrSetup.log it might contain information what went wrong.
In case you might want to install cmtrace which is a log viewing tool which resides on the installation media of configmgr under Tools.

Now I can open the console so we can continue with the configuration, so stay tuned for part 2 of this SCCM blogathon.

#active-directory, #configmgr2012, #microsoft, #sccm, #sql, #systemcenter, #wsus