Microsoft Licensing Issues may Require a Tool Called MGADiag or the Web Version of Genuine Microsoft Advantage!

Good day,


A friend of mine hit me up looking for an application called MGADiag. Wow what an old tool!! But yes, I still have a copy.

I sent it to him. After review, I decided not to include a copy to this article. I did post a link to it, but i want to let people know

they should really look a the new web based tool.(Here) The new tool does not do the same thing, at first glance. but on further review, the

web page relies on a plugin, which seemingly collects similar information.

We don’t have much choice on newer Systems. Just look at figure 1. MGADIAG doesn’t work too well with Windows 10.  Other tabs have worse errors, but some tabs work OK.  .


Figure 1.

Reason for most failures

Hey, In its time, this was a great tool. It collected a lot of the licensing information, all in a few tabs. Great for Windows XP and maybe Vista and Windows 7. Beyond that, let the caveat emptor!

It looks like MGADiag was retired for a reason. So my evaluation of MGADiag in 2017 is its in need of a re-vamp

Well the revamp is basically this article and the web tool. here.

Basically there is a 90% chance your activation issue is captured in this simple document ( here). Did you activate the key from this server already? One License equals one machine. These are basic Tenants, that will tell you if you are genuine or not.

So My Licensing is really Broke

If everything checks out against the article, then go ahead and check licensing with the Genuine Advantage Web tool. If that checks out, then you can check with MS.

What to do about Activation (MS)

If you end up with MS, Microsoft, where you are not in the wrong, you should use standard procedures to get activation and license issues fixed.  So lets get that out of the way.

So you can just do the right thing. Just go to a command line and type  SLUI 3 or SLUI 4. This is command line activation and Voice Activation. When the Voice Activation answers the phone, you will be made to explain why you think your license is genuine. This may require a supervisor. Only the supervisors apparently have the information to make a determination, or perhaps, only the supervisors have the ability to fix a wrong determination in their job description.

So here is the thing. Microsoft can see all license keys. they can see if they are activated. So your story needs to explain why a license would be activated in their system. If your story makes sense, and you don’t mind a deactivation to activate your machine, or multiple activation’s are justified for the key you are using, they will generally make good on your license. .

To conclude, we have MGADiag, Genuine Advantage website, and we have SLUI as tools we can use to work on licensing issues.

But Be careful! MGADiag is no longer a public MS download

For example, look at this link, its wrapped in another application completely! Beware!

Here is the Newer tool, in all its glory:


and Finally, Another Blog example of the basic activation steps as they have not changed much over the years


Louis Reeves

Update all of your Skype For Business Servers



Good Morning Class, Today I just wanted to put into your hands a needed cheat sheet that puts together all of the update changes in SFB into one simple upgrade document for any set of SFB servers.  So lets begin.

Pre-Requisite Install work for Skype for Business Updates

Updates should be done in the following groups, in the following order:

  • Standard Edition Servers
  • Front End Servers
  • Mediations Servers, Director and Edge Servers
  • Back End SQL Servers

To begin, If you have Skype for Business (SFB) Standard Edition, you will follow this process:

Standard Edition Updates for SFB Server Environment

  • 1 Stop-CsWindowsService
  • 2 net stop w3svc
  • 3 SkypeServerUpdateInstaller.exe
  • 4 Once this is complete move to step 5
  • 5 Open a new SFB Shell after closing the update window
  • 6 Stop-CsWindowsService
  • 7 net start w3svc
  • 8 Depending on your Database setup- you may run one or the other
    1. Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn <SQL Server FQDN>
    2. Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn <SQL Server FQDN> -ExcludeCollocatedStores
    3. Install-CsDatabase -Update -LocalDatabases

If you have Standard SFB, Stop. You have completed all you need for your Deployment. If you have SFB Enterprise, Follow the Steps Below.

SFB Enterprise Updates of Servers and SQL

Front End Servers Patched First. Patch One Pool At a time, One Server at a time.

Run: 1. Get-CsPoolUpgradeReadinessState

Only if you get a failure, and only if your results show a missing replica, then you run this command:

    • Get-CsPoolFabricState -PoolFqdn <PoolFQDN>
    • Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery

Otherwise Continue

  • 2. (Ignore if non Clustered or Mirrored) Invoke-CsComputerFailOver -ComputerName <Front End Server to be patched>
  • 3. Get-CsWindowsService (services will be running) & Get-CsPoolFabricState (Fabric will show 1 less server in the pool)
  • 4. Run the latest Installer package
  • 5. Don’t Be impatient!!!
  • 6. Only when the updates are done, move to step 7 or 8
  • 7. (Ignore if non Clustered or Mirrored) Invoke-CsComputerFailBack –ComputerName <Front End>
  • 8. You may check for the pending restart. Be aware you may want to do the restart before moving to the next server

Mediations Servers, Director and Edge Servers Patch One at a time

The Steps are the same for this group of servers as well. However, they need to be completed as a separate group. So begin with the same steps and when complete, Make sure you have restated your servers if needed.Edge Servers should be done together as well.

Back end SQL Servers and other SQL Servers

Once all of these servers in your deployment are updated, You need to update the SQL instances:

  • 1.On the Back End SQL machines OR On the Master FE sever of your Pool (RTClocal) or Monitoring Database

      • Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn
  • If any of #1 is on the back end with the root BE database instance, Use:
      • Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn <FEBE.FQDN> -ExcludeCollocatedStores -Verbose

Once you have completed the final step, you can then run the command Start-CSPOOL, and that should cause the SFB Pool to verify the pool fabric is happy and all will e started up again properly.

Thus having done this, you will have successfully updated you Skype for Business Environment. I hope this makes it a little easier to carry out Your updates.

Yours Truly.


Windows Update Fails Lead you to Troubleshoot around update KB2919355 or other failed 2012 updates.




Hello everyone. I had a strange series of events lead me to this solution. I had three installs of windows, done on three different media, with a different version of Server 2012 on every install.

This includes all versions of Server 2012 and 2012 R2. The minimum media was RTM.  In every single install, Server updates failed, no matter what I did.

There is a variance of things seen in windowsupdate.log. However, you are ultimately going to find yourself looking at updates to remove, install or otherwise. If updates cannot be installed, manually, or otherwise, why don’t you go ahead and try this first. If it doesn’t work, go on with your troubleshooting. I think you will be surprised.


  • 1. Run GPEDIT.MSC
  • Choose Computer Configuration
  • Administrative Templates
  • Windows Components
  • Windows Update
  • Chose the 5th selection from the top in the center pane
    • “Specify Intranet Microsoft Update Service Location”
    • The policy default is not configured
    • Change this to disabled.

Now close the policy and restart the MS update service. Then go back to the Windows Update center, and you should notice that the screen has changed. If not, then go ahead and click the check for updates button.


In my case, There was a change that said MS update needs to update itself. It automatically send a file down and repaired itself. Then updates worked normally after that!!

I wanted to share this one, as it looks to me that this could be a very large call driver for support centers.

I hope this fix finds you and I hope you fixed your customer in a quick timeframe.

As Proof I have had a lot of windows update failures late, I present the weirdest one I have seen. It is called Audit Mode Failures to update. Take a look at that one, if this article does not fix you up. It does have some basic troubleshooting steps in it.

Thank you,


Microsoft Updates does not complete Initial Update on Server 2012 or Server 2016



Hello Everyone,

It’s a lovely night in late 2016, and I am in no shortage of topics to write articles about. I think I’ll choose an issue which actually got me for several hours before I could put together what it was.

Lets start with the customer. Mr. Customer calls in with Windows Server Updates failing. So I know that he had manually updated the server, so the updates done were not from Windows Updates. This is a case where Microsoft Updates never worked. This is a famed situation where you can claim that the customer is not supported if the feature never worked.

I don’t believe in no win scenarios, so I dive In. I hit the basic windows update items.  I am going to try to bulletize these so you have some troubleshooting steps in a normal situation:


  • 1. Go to the Windows Update log. Mine was in the windows folder. Other places exist
  • 2. Look for any error or use the link above to find any errors.
  • 3. How to resolve Update issues article from TechNet
  • 4. Check to make sure there is not WSUS server locally.
  • Even if there is not, check the registry to make sure WSUS IP and port is not listed.
  • Check group Policy for WSUS and or issue the Detect now command switch with Wuauclt. See Link

Now is the time to let you in on the fact that two errors have been in the back of my mind in the Windows Update.log They are:

  • Windows OOBE is still in progress.
  • Failed to get network cost from NLM

So somewhere in the middle of the bullets above, I did think of taking the server out of the OOBE mode. There was no setup going on and it seemed the right thing to do. Surprisingly, after I set the registry key and rebooted, I found the error persisted.

So in the end, I really did find this solution on a Microsoft blog. Why am I reposting this story? Because you have to know what Audit Mode is, to find the article! The solutions are posed under audit mode. My article is on the internet as a Updates failed article. I just hope it finds its way into the hand of someone who fell into audit mode, without realizing it.

So I have to be honest and tell you the customer would not let me apply the solution. he decided to reinstall!!! That’s why its even more important to make sure the solution for this gets out.

From the MS Blog:

  • 1. log in as administrator
  • 2. turn UAC off
  • 3. make sure the user you plan on logging in has administrative rights
  • 4. reboot and login as that user
  • 5. System should have a dialog box for OOBE/reboot and Audit/reboot, choose OOBE, system will restart
  • 6. Audit mode will be off and will ask for language selection etc.


So now realize, you may need to create the new Administrator user name, so please be aware of that.

In closing, Please be aware of the two telltale signs of audit mode:

  • If you get a message that says OOBE\boot and Audit\Boot, pick OOBE every time!
  • If Windows Update will not work, look in the windows Update log, to see if you have the OOBE issue. It will not show up anywhere else!


I hope this has been helpful and educational!