Skip to content

This site is automatic translation of, original in portuguese

Let’s Talk about the Microsoft Honolulu Project?

The Honolulu project was heavily commented on some time ago and linked to a new Windows graphical interface or functionality.

Now on December 01 came a new Preview and documentation version of Honolulu and is already well mature and with final architecture defined.

What is the Honolulu Project?

It is a new MANAGEMENT interface for Windows Server.

This is not a replacement for Windows Server 2012/2016 Server but rather an interface based on new protocols for access and ease of use, in addition to management capillarity.

What are the advantages of Honolulu over Server Manager?

Server Manager is a very good tool, but it is based on local protocols (RPC, WinRM and others) and is based on a GUI that needs to be installed.

Honolulu is 100% web-based for data access and uses WinRM, WMI and PowerShell for server administration.

With Honolulu it is possible to do things that Server Manager does not do, such as running scripts, Windows Update, administering and monitoring VMs, etc.

On the other hand, Honolulu does not manage as many services as Server Manager, such as File Server, DHCP, DNS, etc. that continue to be managed by the MMC tools.

How to install Honolulu?

The installation is very simple, but you have to define the architecture.

Basically we can use installed on a single server and bind others in administration as nodes, or else install a server as Gateway to access others and facilitate traffic when we have many servers in a farm:


In general for these tools the ideal is to create a server with little memory and processing power (in the figure the second model) not to burden servers with other functions, since it creates a service for the Honolulu:


To download Honolulu, because it is still an Preview, you need to use the Windows Server product evaluation page at

How to manage a server with Honolulu?

Let’s go the basic screens. First we insert a server in the list and from there it is possible by any browser to see usage graphs, configure items, make remote connection, execute PowerShell commands, etc.

First, let’s add new servers, clusters or even Windows 10 Client:


In sequence simply indicate the user and choose the server / cluster you want to view:


The level of detail ranges from HW items to detailed graphs for each of the server / client ritual items being monitored:


Even some items such as physical disks, volumes and Storage Space can now be administered in Honolulu:


An interesting feature is that you can manage Windows Update remotely:


Managing VMs in a Hyper-V is also one of the highlights by the level of detail and the intuitive interface:



Finally, follow the Honolulu technical documentation link:


Azure Stack 1-Understand Solution

Now available in most countries of the world where Microsoft has Datacenters, the Azure Stack became a constant theme.

But first you need to understand the focus and composition of the solution.

How is composed?

The Azure Stack is a rack of servers with sizes and settings pre-determined, today available from Dell, HP, Lenovo and Cisco.


The HW manufacturer was approved and standardized, which ensures updates direct from the Azure Stack for both software and hardware.

Does that mean that I can’t use my own settings? Exactly, to ensure that the system updated and the hyper-converged work the drivers have to be type-approved and tested.

It is important to understand that all the Azure Stack is based on the hyper-converged, IE are used the technologies of SDN (Software Defined Network) and SDS (Software Defined Storage) or SDx in General as they are called.

That is, there is no dedicated storage. Each server has a part of 15 k SAS disks and SSD discs, with the Storage Space Direct (S2D) enabled. This allows the servers have their stores added to the share each other volumes.

To guarantee data with the S2D is guaranteed by the distribution of data between servers, as does the VMWare vSAM or Nutanix.

For whom?

Unlike what many people think, the Azure Stack does not target the customer who thinks Microsoft Azure expensive and yes it has limitations in relation to public clouds.

For example, some cases in Ignite were of Swisscom and KPMG of Sweden.

KPMG the scenario was the legislation and the requirement of some customers who didn’t want their audit data in public cloud for more that try to justify the given security. The solution was the Azure Stack where KPMG would have the same services used by other branches in the world, but on-premisse.

Already the case of Swisscom was to be a local Datacenter as the Azure has no one in the country. So, those customers who want to use public cloud services using private cloud Azure Stack to host their local services.

That is, the main customers are, among others:

  • Countries where there are no restrictions about legal store data in other countries
  • Data centers interested in offer services to your user the same interface of the Azure, but locally, for example in Brazil only have one DC Microsoft Azure and a traditional provider could use the Azure Stack as Avaliability point Group
  • Companies with high usage of computer resources based in IaaS and have own Datacenter
  • Companies with tradition on-cause you don’t want to view your data out of the environment but wish to use the Cloud model Publishes “in place” with easy maintenance and high level support

And that customer who thinks the Azure expensive, worth using the Stack? At the tip of the pencil, not because we need to remember that it is a rack and need cooling, energy, high floor and all the other costs involved in a physical DC.

How much does Azure Stack?

You must first view the cost of Hardware that can be sold differently by each of the 4 current manufacturers.

For example in the case of the Dell configurations start at 20 CORE servers 4 and 4.1 TB and can reach 12 servers per rack, and the maximum capacity of 4 Racks with 12 servers each.

In addition, we have the servers Low, Mid and High profille, where a rack with 12 servers High Profile capacity is 336 Core 6.1 TB RAM, 138TB, cache, 1.2 PB of disk!!

Now let’s talk about the cost of Software. It is important to remember that the Azure Stack has no software cost, or whether billing as a service, which includes:

  • Updates of the Software Stack
  • Driver updates and logical components
  • Pre-configuration of the provision and components and templates
  • Microsoft Azure support is the same as answering Azure Stack

That is to say, the Azure Stack has a cost for consumption, not with licensing, in “Pay-As-You-Use”, based on the table below:



Based on that, we have for example a VM A2 which costs U $130/month in Microsoft Azure, in the Azure Stack goes for $40/month.

Of course you must include the TCO Datacenter infrastructure, warranty and support of HW, and electric power administration in Microsoft Azure does not have.

Even so, large environments that already have the Datacenter becomes advantageous option for already include many of these embedded costs.

And if the customer does not want to pay for consumption?

It is also possible to get the cost per CORE, but personally I see no advantage because the cost increases for the following reasons:

  • The template variable “Pay-As-You-Use” scalability also reflects on the price decrease when the load
  • The disconnected model it is necessary to pay separately the Windows and SQL licensing in the model “Pay-As-You-Use” is built
  • In the disconnected model annual payment is upfront


All Azure services are available in the Azure Stack?

Not yet. As you can see in the table of prices the most important Yes.

For example, some types of VMs as G could not run on the Stack and the same with some high-capacity services such as Machine Learning and Cognitive Services.

It is possible to create plans and join different solutions to create complex workloads, as documented in


Azure became the flagship product of Microsoft and Stack integration between public and private clouds actually becomes a unique experience!

Visit the link and learn product details:

Azure Reserved Instance Available for purchase

In a post at the beginning of the month we comment on the Azure Reserved Instance on

Now it is available for purchase and also on the calculator of Azure (Azure Pricing Calculator) to estimate the economy so much just the VM and AHUB.

To remind, the AHUB is the feature that allows economy by using the licenses that you have acquired Software Assurance

Using the calculator

Visit the Azure cost calculator and adding a VM will see the option to include the AHUB also laughs at 1 or 3 years.

Below are the pictures demonstrating how to choose and the possible reduction of $102 to a normal, $58 in a VM laughs at 3 years and joining the AHUB to U $24!!!!!




And finally with the AHUB option:


Buying Reserved Instance in the Azure Portal

RI purchase the portal requires that first enabled the offer in the signature.

It is important that subscriptions to MSDN or benefit and Dev/test not have RI because it comes at a cost of 40 to 60% lower in the VMs.





Conclusion: We Now have a VM with more than 80% off joining the offers of RI and AHUB!!!

Cost reduction with Azure Reserved Instance

A few months ago, in July, we discuss the use of licensing alternatives ways to reduce costs with the Azure using CPP and AHUB at

The CPP (Compute Pre-Purchase) is a very good resource for allowing to buy a package of hours for a particular instance type of VMs in Azure.

But Microsoft surprised a few weeks ago the Group of MVPs and commercial team with information about a new offer, the Reserved Instance:


The following is a summary that I put together to explain the main differences between the models:


Stay tuned to the GA of the Reserved Instance by using the link at the beginning of this article.

Acquiring and licensing the Azure who – Operations Management Suite

We present many times to the client this solution, which runs on Azure brings benefits too great for it’s it administrator.

Has been much talked about the who, originally called System Center Advisor, after Log Insights (Using the Azure Log Analytics (OMS) and the SCOM on Same Machine and

I’m very fond of showing the Health Check solutions (Active Directory and SQL) and Change Log:


But many do not understand how the licensing to purchase this solution.

What are the possibilities to acquire?

First is good to remember the basic levels that a management space (as they are called the "tenants") can be:


  • Free – Useful for testing because it does not limit to only a few of the packages, but the collection is limited to 512 KB per day of logs and only 7 days retention
  • Standalone -allows you to collect without restriction of size and retention of 30 days (can be customized), has no price per server/node for storage consumed. However, it does not allow to use all the solution packages that need to be acquired in packages E1 or E2
  • Standard and Premium -allows you to collect without restriction, retention of 365 days and allows use of solution packages, depending on the chosen level
  • Who – this is the bundle E1 or E2 that can be purchased on an as-needed basis, with price per managed nodes and that includes System Center licensing and other services
Which of the models worth?

If your intention is to use the counters and how Healthy Check solutions and some analysis, you can select the Standalone plan where you can use several solutions paying only the log store so much.

But with the Standalone cannot evolve into other solutions, such as network traffic analysis and mapping solutions.

Due to this limitation, the ideal is to have the bundles of who where you will be able to choose the solutions and also include a number of services and built-in consumption, besides all the Licensing System Center.

Who packages E1 and E2

Without doubt the best option for companies, where you get services and packages with System Center included (or via Add-on if you already have) and you can use other services already included in the price.


As we see in the image above, the bundles are composed of management packs (image below), services such as Backup and Recovery Site and the licensing of System Center.

This is very interesting when we compare the costs of each of the services and what they include:


Just compare the cost of each Management Pack with the value of E1 and E2 to notice that it’s not worth a Standalone acquisition/Standard/Premium, only the cost of the Protection/Recovery is already practically the bundle value E2.

What if I already have the System Center or licensing Windows CIS (Cloud Infrastructure Suite)?

In this case do not have to pay twice the System Center, because as the E1 and E2 already include can acquire by add-on, or be added to the package that already has and may choose to continue renewing the CIS/Licensing System Center or converting to who:


Personally I think it’s good for this case continue with the System Center licensing/CIS, since I use some nodes with who and some don’t depending on the model of monitoring that wish to adopt.

How can I estimate and compare and decide these costs?

Microsoft has a calculator where you select the services and receives the comparison between the bundles who E1 and E2 or standalone purchases:


System Center Configuration Manager (SCCM)–Release 1706

Released the two weeks, the new update has many new features:

Some are important because they solve problems and previous demands but the new features are also of interest:

  • Support for SQL Server Always ON (asynchronous backup mode only in this release)
  • Integration with Azure AD for authentication that allows you to install the agent for non-LAN user
  • Improved integration with both Windows Intune 10 as mobile devices (iOS, Android)
  • Ability to import scripts (!!!)
  • Support for the new Windows Update for Business 1703
  • Integration with Operations Manager Suite (OMS)


Software Asset Management (SAM)-Converting licensing for Azure

This topic is relevant at a time when we’re migrating to Cloud Publishes in many companies.

Update: Microsoft create other campaign:

Continuing the series on SAM, let’s get some other topics and give attention to Azure. To view the list of subjects we’ve covered visit

1-Using the Normal Licensing for Windows VMs (SPLA)

To create virtual machines in the Azure is already set that the operating system is Windows and pay licensing embedded as part of the service.

This licensing model is called the SPLA and allows a provider (not exists only in Azure) license VMs as services billed instead of customer purchases the perpetual license as in online environments cause.

The cost of that licensing is measured by comparing values of the same with Windows and Linux VMs in and

The day I rode this post the hour value of a VM D2 v2 Linux is U $0.159 and the same VM with Windows U $0.251. That is a difference of 43% in the price of the VM.

For this price difference we have options to use other forms of licensing we will discuss below.

2-Using AHUB (Azure Hybrid Use Benefit)

The AHUB is nothing more than using your license already bought on contract with Software Assurance (SA) in Azure and pay the SPLA Licensing.

Note however that your license should have SA hired, namely the right to upgrade, and virtualization. If you don’t know the SA see the post where we have a topic on this.

In the case of using the AHUB the price difference calculated in previous item does not exist, since the licensing is now done in recruitment in Enterprise Agreement, MPSA or even OPEN. The contract type depends on the value and is acquired by a Microsoft licensing partner (LSP).


Microsoft already provides the templates for VMs AHUB but is also possible to use PowerShell with the –licencetype parameter. In case if you use the portal, simply create the VM stating that:


However it is important to note that the AHUB is a Windows machine created with the price of Linux and it’s not possible to make the change through the gate. That is, you must re-create the VM if it already exists in the normal template.

Of course there are easier ways:

  1. Delete the VM, but not delete the disk
  2. Create a new VM as AHUB
  3. Attach the VM disk that was deleted
3-Using CPP (Compute Pre-Purchase)

The CPP is an old acquaintance who uses AWS, with the name of RI (Reserved Instance), but with a difference. See the following link, but he doesn’t have many details:

While at AWS customer buys a given type VM/layer, the CPP of Azure the customer buys compute hours of given type/VM layer, following some rules:

  • Equivalent buying 744 hours of a determined based on type of VM
  • Are purchased for 12 months regardless of the anniversary of the contract (no-rata)
  • Are not linked to a VM specifies, works as a reduction in the total hours
  • May not be used or relocated to other types of VM as if it were proportional
  • Is paid upfront, that is the value of 12 months

The cost reduction is significant, but the value depends on the type of contract that the customer has and the level of discount, in some cases reaches 60% to customers and.

To understand the calculation, let’s use a simple table of HYPOTHETICAL cost:


More a time it is important to note that these VMs cannot be assigned to another type, the CPP covers for 12 months 744 hours monthly from a determined based on type of VM.

However, some customers use the CPP to upgrade since it allows cost reduction with the same value already provisioned for Azure 2 up to 3 layers the existing VMs!

4-Using CPP + AHUB

It is possible to combine the CPP with AHUB? YES!!!

Taking into account that the above calculation of the CPP was hypothetical, we use the value U $0.251 reference for Windows VMs in CPP with $0.16 U value, namely a VM with Windows SPLA Licensing.

Join the discount that the proportional AHUB, you can buy Linux VMs and use licensing that already has under contract, for example the value of the same VM D2 v2 of U $0.159 Linux would fall to U $0.12 with Windows using the existing licensing.


With PPC you can save 25 to 60% without having to make any effort, and with the AHUB you can create much more VMs account using the existing contract with Windows.

Clear that the CPP is much more attractive, since it does not require change in VM template, but both the AHUB as the CPP must be included in licensing agreements.

Now have fun, see licensing your partner and see how much you can save with these two licensing options!