Microsoft News Summary – 1 August 2014

Talk about crappy timing. A federal court in the USA has determined that emails are not actually emails, and therefore Microsoft must turn over emails business records stored on Email servers in the Dublin region to the FBI. One must wonder why the FBI didn’t contact the Irish authorities who would have jumped at once if the case was legitimate and issued an order locally. Maybe the case is not actually legitimate?

On the eve of Azure going big through Open licensing, a federal judge has stuck a stake through the heart of the American IT industry – this is much bigger than Microsoft, affecting Google, Apple, Oracle, IBM, HP, Dell, and more. Microsoft has already lodged an appeal.

Microsoft Azure Now Available Through Open Licensing

It is August 1st, and today is the very first day that you can buy credit for usage on Azure through Open Licensing. This includes Open, OV, and OVS, as well as educational and government schemes.

How Does It Work?

The process is:

  1. A customer asks to buy X amount of credit from a reseller – the next bit of stuff is normal licensing operations that the customer does not see.
  2. The reseller orders if from a distributor.
  3. The distributor orders the credit from Microsoft.
  4. A notification email is sent out to the customer with a notification to download an OSA (online services activation) key from their VLSC account (used to manage their Open volume licensing). The customer is back in the process at this point.
  5. The customer/partner enters the OSA key in the Azure Account Portal.
  6. The customer/partner configures Azure administrator accounts and credit alerts.

Credit is purchased in blocks of $100. I believe that it is blocks of €75 in the Euro zone. So a customer can request $5000 in credit. They don’t get 50 OSA keys: they get one OSA key with a value of $5000.

Who’s Account Should We Use?

If you are a customer and the MSFT partner wants to set you up under their Azure account, tell them to frak right off. The VMs will be THEIR property. The data will be THEIR property. We have seen this situation with Office 365. Customers have lost access to data for months while MSFT’s legal people try to determine who really owns the data. It is MESSY.

The MSFT partner should always set up the customer’s Azure deployment using a Microsoft Account that is owned by the customer. Additional administrators can be configured. Up to 5 alerts can be configures to send them to the reseller and the customer.

Using Credit

“How much will doing X in Azure cost?” and “How much Azure credit do I need to buy?” will be the two most common questions we distributors will hear in the next 12 months. Ask me and I’ll respond with one of two answers:

  • If I’m in a good mood I’ll tell a consultant to go do some frakking consulting. How the frak am I meant to know what your customer’s needs are? And that’s if I’m in a good mood 🙂
  • If I’m in a bad mood I might award you with a LMGTFY award and make you famous 😀

The answer is based on how credit is used. You buy credit, and everything you do in Azure “burns” that credit. It’s like having credit on a pay-as-you-go (aka “burner”) phone. If you do A then is costs X per minute. If you do B is costs Y per month. Go look at the Azure pricing calculator.

Not all “Azure” services can be purchased via credit. Examples include Azure AD Premium and AD RMS that are licensed via other means, i.e. SaaS like Office 365. Their branding under the Azure banner confuses things.

Credit Time Limits

Your credit in Azure will last for 12 months. It will not roll over. There are no cash-backs. Use it or lose it.

My advice is that you start off by being conservative with your purchasing, determine your burn rate and purchase for X months, rather than for Y years.

Topping Up Credit

You should have configured the email alerts for when credit runs low. If credit runs out then your services shut down. I hope you reserved VIP and server IP addresses!

When you get an alert you have two options:

  • Normal procedure will be to purchase additional credit via the above reseller model. With alerts, the MSFT partner can initiate the conversation with their customer. Obviously this takes a little while – hours/days  (I have no idea because I’m outside of the logistics of licensing).
  • If the customer runs out of credit and the reseller process will take too long or it’s a weekend, the customer can use a credit card to top up their account in the Azure Account Portal. This should be an emergency operation, adding enough credit for the time it will take to top up via the reseller.

Note that old credit is used first, to limit wastage because of the 12 month life of credit.

The Benefits of Open

For the customer, they can use Azure in a controlled manner. You don’t have to buy thousands of dollars of credit through a large enterprise EA license program. You don’t have unmanageable payment via a credit card. You buy up front, see how much it costs, and deploy/budget accordingly.

For the partner it opens up a new world of business opportunities. Resellers have a reason to care about Azure now, just like they did with Office 365 when it went to Open (and that business blew up overnight). They can offer the right solution for customers, private (virtual or cloud), hybrid cloud or public cloud. And they can build a managed services business where they manage the customers’ Azure installations via the Azure Management Portal.

Distributors also win under this scheme by having another product to distribute and build services around.

And, of course, Microsoft wins because they have a larger market that they can sell to. MSFT only sells direct to the largest customers. They rely on partners to sell to the “breadth market”, and adding Azure to Open gives a reason for those partners to resell Azure on Microsoft’s behalf.

KB2989384 – Hyper-V Best Practice Analyzer (BPA) Does Not Close

Microsoft published a KB article to help you when the Hyper-V Best Practice Analyzer (BPA) does not exit or appears to hang/crash.

Symptoms

Hyper-V Best Practice Analyzer (BPA) does not exit under the following conditions:

  • A virtual machine already exists.
  • The virtual machine is connected to a vhd or vhdx as the hard disk drive. However, the vhd or vhdx file itself is renamed or deleted, and does not exist in reality.

Cause

The PowerShell script as seen here runs internally when running the Hyper-V BPA:

C:\Windows\System32\BestPractices\v1.0\Models\Microsoft\Windows\Hyper-V\Hyper-V.ps1

However, due to a defect in the script, the information retrieval process goes into a loop, and the BPA does not exit until timeout.

Workaround

You need to delete the non-existing vhd or vhdx from the virtual machine settings, and then rerun BPA for Hyper-V by following these steps:

  1. Start Hyper-V Manager.
  2. Select the virtual machine that is connected to a non-existing vhd or vhdx, then right-click and open Settings.
  3. From the virtual machine settings window, click on the non-existing hard drive, and then click Delete.
  4. Click OK to close the virtual machine setting window.
  5. Rerun BPA for Hyper-V from Server Manager.

The article claims to apply to Windows Server 2012 (WS2012).

Microsoft News Summary – 30 July 2014

Very quiet 24 hours in the Microsoft world. The only bit of news I have for you is Microsoft’s newest (48 hours old) statements regarding the US government trying to spy on non-USA located emails.

Microsoft News Summary – 30 July 2014

The big news here for MSFT techies are the releases of update rollups for SysCtr 2012 SP1 and SysCtr 2012 R2. Please wait 1 month before deploying to avoid the inevitable issues (history indicates that I am probably right) and use that time to carefully review the installation instructions.

My Site Appears To Be Healthy Again

I do not know what the root cause of my location-specific outage last Friday was. I know that my Vodafone Ireland broadband at home was affected. I also know that Sky Ireland broadband was affected. But others internationally and the ISPs at work had no issues. It was all very strange … and the problem appears to have sorted itself out today (the following Wednesday).

Anywho, business (and sarcy posts) as normal!

Microsoft News Summary – 29 July 2014

Another slow 24 hours:

Microsoft News Summary – 28 July 2014

It was a quiet weekend. Note a useful scripts for health checking a Scale-Out File Server (SOFS) by Jose Barreto.

KB2986895 – VMs Lose Network Connection on WS2012 or WS2012 R2 Hyper-V When Using Broadcom 1GbE NICs

If you’re affected by this issue then you should have read this post. Microsoft posted a KB article for when virtual machines lose network connectivity when you use Broadcom NetXtreme 1-gigabit network adapters on Windows Server 2012 Hyper-V or Windows Server 2012 R2 Hyper-V.

Symptoms

When you have Hyper-V running on Microsoft Windows Server 2012 or Windows Server 2012 R2 together with Broadcom NetXtreme 1-gigabit network adapters (but not NetXtreme II network adapters), you may notice one or more of the following symptoms:

  • Virtual machines may randomly lose network connectivity. The network adapter seems to be working in the virtual machine. However, you cannot ping or access network resources from the virtual machine. Restarting the virtual machine does not resolve the issue.
  • You cannot ping or connect to a virtual machine from a remote computer.

These symptoms may occur on some or all virtual machines on the server that is running Hyper-V. Restarting the server immediately resolves network connectivity to all the virtual machines.

Cause

This is a known issue with Broadcom NetXtreme 1-gigabit network adapters that use the b57nd60a.sys driver when VMQ is enabled on the network adapter. (By default, VMQ is enabled.)

The latest versions of the driver are 16.2 and 16.4, depending on which OEM version that you are using or whether you are using the Broadcom driver version. Broadcom designates these driver versions as 57xx-based chipsets. They include 5714, 5715, 5717, 5718, 5719, 5720, 5721, 5722, 5723, and 5780.

These drivers are also sold under different model numbers by some server OEMs. HP sells these drivers under model numbers NC1xx, NC3xx, and NC7xx.

Workaround

Broadcom is aware of this issue and will release a driver update to resolve the issue. In the meantime, you can work around the issue by disabling VMQ on each affected Broadcom network adapter by using the Set-NetAdapterVmq Windows PowerShell command. For example, if you have a dual-port network adapter, and if the ports are named NIC 1 and NIC 2 in Windows, you would disable VMQ on each adapter by using the following commands:

Set-NetAdapterVmq -Name “NIC 1” -Enabled $False
Set-NetAdapterVmq -Name “NIC 2” -Enabled $False

You can confirm that VMQ is disabled on the correct network adapters by using the Get-NetAdapterVmq Windows PowerShell command.

Note By default, VMQ is disabled on the Hyper-V virtual switch for virtual machines that are using 1-gigabit network adapters. VMQ is enabled on a Hyper-V virtual switch only when the system is using 10-gigabit or faster network adapters. This means that by disabling VMQ on the Broadcom network adapter, you are not losing network performance or any other benefits because this is the default. However, you have to work around the driver issue.

Get-NetAdapterVmqQueue shows the virtual machine queues (VMQs) that are allocated on network adapters. You will not see any virtual machine queues that are allocated to 1-gigabit network adapters by default.

Sigh. I hope Broadcom are quicker about releasing a fix than Emulex (customers are waiting 10 or 11 months now?).

How My Site Went Offline On Friday, July 25th 2014

My site is hosted on Azure in the Dublin (Europe North) region. On Friday morning, I was checking something when I saw my site was not loading correctly – it was either offline or VERY slow. So I check the Azure status and saw it was offline. I restarted the application pool and the problem remained. I rebooted. MySQL took an age to load, but the site was still not loading … from home.

I have endpoint monitoring configured. Notice that Amsterdam was showing an issue and Chicago was not. Strange, eh? I’ve worked in hosting and I know how localised these problems can be. So it was time to start digging.

I asked online and people in Denmark were OK. Folks in Belfast and Netherlands had connection problems. Later, Denmark went offline and Amsterdam came back!

image

 

From Home (Vodafone Ireland – very slow/no access) I ran a tracert:

image

From the lab at work (Magnet ISP – access OK) I had different results:

image

From a VM with an ISP (Blacknight – access OK) I had different results again:

image

It was very odd. Nothing was red on the Azure status site. I’m guessing there was a localized issue within Azure that affected just a subset of us, or there was an external routing issue that affected some ISPs.

It’s still like this as I post … in other words, the site is fine for some and offline for others.

EDIT (30/7/2014):

I came home today to find that my site was once again available via my ISP.

 

Technorati Tags: ,