Miro Consulting specializes in software license audit defense, license management, subscription management, and cloud services, for Oracle, Microsoft & IBM.

The 7 Most Common Oracle Support Management Mistakes

Managing Oracle Support contracts is costing your organization time and resources that may be better spent elsewhere.

1. Overpayment of fees

It’s easy to accidentally over pay for support fees if each line item isn’t carefully reviewed. Errors can be made in the costs from year to year. To avoid overpaying, organizations must meticulously check every detail of the contract.

2. Submitting incorrect contracts

There is no verification when uploading POs. This can lead to accidentally renewing a contract which needs revision. Organizations should carefully review all POs and contracts before anything is renewed to assure they are properly submitted.

3. Contract termination due to missed support renewal dates

Missing a renewal date can cause major issues and come with significant costs for an organization. Oracle can terminate contracts if they are not renewed in time. There are costly penalties to clients in the form of reinstatement fees. It is vital for IT asset management teams to assure contracts are renewed in a timely manner, or contract outside experts to manage the process.

4. Missed opportunities for additional discounts, migration and upgrades

Clients often miss opportunities for upgrades, migrations, and/or bundling discounts. Experts like Miro can review and inform clients of options available prior to renewal.

5. Inefficient contract management

It is very difficult to manage 20-30 support contracts with sporadic due dates. Miro can customize the renewals and renewal invoices for our clients to align contracts to a singular, or multiple due dates to assure contracts are managed efficiently and easily. Miro can also assist with charge backs given our ability to bundle or un-bundle line items from renewals.

6. Missing cost allocation

It can be difficult to allocate costs to specific departments, especially if the multiple departments have pulled funds and purchased licenses at a single point in time. Miro can identify and customize renewals so clients can easily allocate renewal costs to the proper departments.

7. Not evaluating 3rd party support options or possible cloud options

Many clients are unaware there are companies offering third party support. These companies usually offer support at a much lower cost than Oracle and generally offer a higher level of customer service. The drawback is you lose the rights to bug fixes, upgrades, etc. There are also opportunities to upgrade to cloud offerings that can capitalize on your on-premise investment.

Miro can prevent these common mistakes.

Leveraging 17 years of experience solving Oracle Support issues, we may turn your Oracle Support renewals from an expensive hassle to an easy turn-key operation. We handle everything including contract preparation, negotiation and cost allocation.

Contact Miro to schedule a brief 15 minute phone call to learn how your organization can save significant time, money and effort by letting Miro manage the process for you.

Please call us at 732.738.8511 x1208 to quickly determine your support savings potential.


AWS Cloud Crash Shows Why Some IT Assets Should Stay On-Premise

The Amazon Web Services (AWS) cloud located in the company’s Virginia data center crashed on February 28, 2017, causing many of the largest sites and apps on the internet to slow or stop working entirely.  Amazon referred to the incident as an “increased error rate” at the time and has now traced the issue to a mistyped command by an Amazon employee.

The outage highlights what many cloud vendors don’t want their clients to know, that some assets are actually better kept on-premise.  While the cloud may be extremely beneficial to certain applications and technologies, others are ill suited or currently impossible to move to a cloud environment.

Without careful planning of cloud migrations, organizations can lose substantial value in their previous investments in hardware and application licenses & subscriptions as they develop their future strategies.  Opportunities for substantial savings can be easily missed when transition teams are unaware of unpublicized special deals that many vendors are willing to accept.

Eliot Colon, Senior VP at Miro said “Companies are increasingly coming to Miro to ask about the ‘pros and cons’, as well as potential ‘gotcha’s’ of moving from on-premise to cloud deployments.   They are mostly concerned about ROI, cost and contractual jargon.  Unexpected outages and security issues are real and occur even in the largest and most secure cloud deployments.”

Migrating assets from on-premise solutions to the cloud can cause problems as well as solve them.  Cloud architecture can lower costs through increased efficiencies, but it also can spread risks in terms of security and downtime.  Where on-premise assets are small, isolated targets, the new cloud platforms are high profile opportunities for hackers.  Even if it’s not your IT assets being targeted, they can suffer collateral damage when sharing space with affected systems.

The cost advantage of using cloud solutions has also decreased over time.  As cloud vendors have seen their licensing profits decrease, they are increasing their cloud costs to make up for the lost revenue.

Customization is also an increasingly difficult issue for organizations looking to migrate to the cloud.   Where the one-size-fits-most model of cloud services works well for many organizational needs, it does not meet them all.  Cloud products often don’t provide the detailed performance information in many cases needed to maximize efficiencies and understand exactly how the systems are running.

If you’re considering a cloud transition or moving to a hybrid environment, contact Miro consulting to learn which assets work best in the cloud, which assets should stay on premise, and how to get the best possible price and terms.

About Miro:

Miro consulting specializes in software audit defense, license management, subscription management and cloud services for Oracle, Microsoft, IBM and Adobe.  Contact Miro by emailing, or by phone at 732-738-8511 x1208 or online at


Compliance Risk – Oracle alters license allocation rules for Microsoft Azure and Amazon Web Services Environments

Oracle has introduced new rules on how to apply on premise licensing for use in Microsoft Azure and Amazon Web Services environments. The changes result in an effective doubling of requirements for most Azure and AWS environments, while keeping Oracle Cloud requirements the same.

Compliance risk to current clients who use Oracle within AWS and Azure environments still remains unknown at the time of this writing, but expect this to definitely impact any future deployments of Oracle on Azure or AWS platforms.

To find out how these changes affect your environment, contact Miro Consulting at <a href=””></a>.


New Updated Rules Make Oracle Cloud Less Expensive than Amazon AWS

On January 23, 2017, Oracle introduced significant updates to their “Licensing Oracle in a Cloud Environment” guidelines document. Miro has been reviewing the document to identify the key changes, and how they relate to current environments and decisions for future environment plans.

As is typically the case with Oracle, the document does not express a clear view of the true comparative impact of the changes they made against the previous guidelines. The changes appear to favor the Oracle Cloud over AWS and Azure environments when calculating the requirements when applying on premise Oracle licenses. With Oracle’s announcement, using the same configuration in other provider’s clouds, or even on premise, can pose a substantial cost increase, both in terms of licensing as well as perpetual support. The impact may be significant; we are working with Oracle to confirm the conclusions we have made. Once confirmed, we will send you details of the changes and their impact for current and future environments.

Miro will be communicating the analysis of the changes this week, so until that time, we highly recommend that you hold off on expanding any use of Azure or AWS until we confirm the impact. Cloud licensing is very complex. Members of the Miro Support Network are encouraged to contact Miro to discuss your current environment, as well as any plans for transitioning to the cloud.


Adobe Has A New Way of Tracking Non-Licensed Software

Adobe’s new Genuine Software Integrity Service validates installed Adobe Software.  It automatically checks for counterfeit software, invalid licenses and alerts Adobe of fraudulent use. The process looks for illegitimate serial number and if it includes software hacks. Once verified, Adobe notifies the company/violator that their software is not genuine.

Companies still should have a program in place to track the full lifecycle of their software assets, to have full control and understanding on:

  • Software requests vs Actual software need
  • Centralized procurement process to manage the acquisition of software through a standardized channel vs multiple sources.

One key point is to stop users from purchasing from non-qualified resellers.  The service is still very new. We will share more information as we learn more.


Warning: Your Software Asset Management (SAM) Tool is NOT Certified

IT professionals must remember that a tool does not understand the rules

Many software license management tools claim to be certified by Oracle, Microsoft, IBM and others, but none actually are. For example, Oracle’s LMS page does list a number of tools, but only as supplements, not as certified tools, and they often miss 90% of Oracle products.

“Tools from the following vendors have been verified to provide the required data set to supplement a LMS engagement. The scope of the verification process only covers the data collection related to the installation and usage of specific Oracle products, namely Oracle Database and the associated Options. The verification does not include any other Oracle products or the overall capabilities of the vendor’s solution… Please note that the installation and usage of a tool from a verified vendor does not replace an Oracle License Audit or True Up engagement or revoke Oracle’s contractual right to perform a License Audit or True Up.”

IBM has similar language in their rules. “ILMT is a mandatory IBM requirement for all IBM customers who take advantage of sub-capacity licensing, regardless of whether they utilize third party reporting tools.”

Microsoft’s Software Asset Management (“SAM”) program is an audit, albeit a “friendlier” one. In such an engagement, Microsoft will tend to accept the output of virtual any tool. However, if this information is inadequate or incomplete or otherwise not acceptable to Microsoft, the customer could be compelled to use a Microsoft product. These might come in the form of the for-fee subscriptions or products of Enterprise Mobility Suite, Intune, or System Center. Or, in their absence, the Microsoft Assessment & Planning (“MAP”) Toolkit which a free of charge.

But in the case of a formal audit involving a partner (e.g., KPMG, Deloitte, etc.), Microsoft will equip the auditor with a discovery tool. These scripts are typically executed by a member of the audit term (versus by the customer). Sometimes the audit partner has a tool that Microsoft has certified for use in lieu of the Microsoft tool. In this type of engagement, the output of these tools is the only acceptable one.

IT professionals must remember that a tool does not understand the rules. They can lead to false positives, identifying assets as licensed, even when they are not. Most importantly, software asset management tools don’t understand the context of the software as it’s being used in the business, or if the product is being over used or underutilized.

Don’t let these SAM tools give you a false sense of assurance. No tool is a substitute for expert research, evaluation and validation. If you’d like to speak with a Miro Expert about your use of SAM tools, and how Miro can help evaluate your risk of an audit, contact us today.


Microsoft Replaces CRM Online with Dynamics 365 and Increases Prices

In October 2016, Microsoft announced that it was no longer going to sell the CRM Online suite.  Current users of the product will now be forced to buy Dynamics 365.  For some users this may amount to a small decrease in the price of the subscription, but for many it will be much more.

CRM Online offered different per user, per month prices for different levels of functionality:

  • Professional – $50
  • Basic – $23
  • Employee Self Service – $2

Now new customers will have to buy the Dynamics 365, which combines CRM, ERP, and other apps. Existing customers of Dynamics CRM can continue to use and purchase additional licenses of these older applications, but when they renew their agreement, they must transition to Dynamics 365 SKUs.

The new offerings of Dynamics 365 are:

  • Business Edition – $50
  • Enterprise Plan 1 – $115
  • Enterprise Plan 2 – $210

These plan prices can be discounted with the right timing and strategy.  To discuss your software licensing situation, and find out how to save on your next purchase, including cloud purchases, contact Miro at


Office 365 Price Tiers Provide Less Value Than Other Microsoft Product

Price tiers for Office 365 represent only a 3% difference from the preceding level rather than the more traditional 7+% for other products.

Both of these are reflective of cost and budgeting.

For Windows Server / System Center, the cost of licensing larger servers (that is, with more cores per processor) will increase. Organizations may have opted – or are contemplating – these denser servers as a way to increase capacity and workload while constraining additional software license investment. That’s the point I was making here.

For Office 365, the notion of determining cost by ascribing a routine 7% discount from one price level to the next does not work. So if an organization is considering going for that extra 100 seats in order to attain Level “C” pricing, for example, Microsoft’s proposal may come as a surprise. So consider Office 365 Plan E3. At Level “B”, the monthly fee is $18.80. Thus, 5,900 licenses would cost $110,920. If the organization opted to license 6,000 users, the unit cost is $18.20 – the 3% variance – and the monthly cost is $109,200 – just $1,720 less.

What the customer might have been expected is the traditional 7% price variance, which would result in a $17.84 monthly unit cost, which, in turn, translates into a monthly total of $104,904 – over $6,000 less!

So the price variance by month is nearly $4,300. The annual variance is over $51,000. That could be a hard nut to crack if not budgeted.