Well, before continuing let me tell you that if you are here, at this point, opening the post in order to install WAP, it's because you have previously deployed the needed components such as Hyper-V host, SCVMM 2012 R2, Fabric and SPF (You can find out how to do it in my previous posts). Otherwise, don't go ahead because it doesn't make sense and you may not find it very exciting.
Windows Azure Pack is a set of web pages and Azure technology, which integrates with System Center 2012 R2 and Windows Server 2012 R2 in order to provide management for the Private Cloud. This allows us to use the same interface as Microsoft Azure on the Public Cloud and, most importantly, the same operating model for customers with plans, fees, etc.
There are two types of installation:
- Distributed Deployment, which installs all components on multiple machines.
- Express Deployment, which installs all components on a single machine.
For today's scenario, we will use an Express Deployment. Let's start with requirements.
Requirements
In my case, I will use a virtual machine with these minimum requirements:
Hardware
- 8GB RAM
- 40GB Hard Disk
Software
- Windows Server 2012 R2
- Microsoft Web Platform Installer 4.6
- .NET Framework 3.5 SP1
- IIS 8.5
We need also to have a SQL instance to hold the WAP configuration database. I had installed it previously on that machine. Just install SQL as you usually you in your deployments.
You will also need an AD account to run the SQL instance. In my case, I have used "CASURO\wap_sa".
Now let's continue with the installation.
Installation
Run the Express Installer.
Click Install.
Accept the prerequisites.
Choose your option. Click Next.
Component installation starts.
Click Continue.
Click Finish once the installation is completed.
The installation launches the WAP configuration webpage (So far, we don't have a certificate, so you will be warned about it. Just click Continue to this website against recommendations).
Introduce hostname with port, select SQL Server Authentication and introduce the credentials for the "sa" user which you established during SQL installation. In my case, "wap_sa" credentials.
Select your option and click Next.
Click checkmark button in order to start the installation.
Click Checkmark button to finish the installation.
Awesome! You've done it! You just got an Azure interface for your Private Cloud and that's going to be the coolest thing you have shown to the LOB lately. Just kidding!
In the next post, I will configure and connect WAP to VMM in order to get the complete functionality.
See you soon!
You might find misconceptions in this blog. If so, please feel free to reach out to me and I will be more than happy to discuss about it.
No comments:
Post a Comment