Nutanix: stop and remove tasks

Sometimes it happens that Tasks in a Nutanix environment take like forever.
It is not recommended but there are occasions that a Task needs to STOP!
And it happens that this is not possible via the GUI (Prism Element or Prism Central).

So to get the current running tasks:
(from PE or PC)

ecli task.list include_completed=false

And to stop the Task:
(there are 2 dashes before task…)

ergon_update_task --task_uuid='TASK_UUID' --task_status=aborted

And verify with the above command again (ecli task.list include_completed=false)

BTW –task-status can have following values:

  • running
  • succeeded
  • aborted
  • suspended
  • failed

Windows 10 (and Windows 7) License key – retrieve and report

Recently I got a question about Embedded License keys for Windows client OS systems.

These are systems with a Windows license key embedded in the BIOS.
If you install Windows on a system with an embedded key, it will automatically install this key and activate it.

There are several ways to get the Original License Key from a Windows machine.
  • Powershell (PS);
  • Command Prompt (CMD);
  • Windows Scripting Host (VBS).

But there is a little problem here. The key is stored as an encrypted registry key. With the first three tools this is not a problem, but with Windows 7 only the last tool, vbs scripting, is possible.
And then we have to do a little conversion
I will show how!

  • Powershell (PS)Open an administrative Powershell windows and type:
    (Get-WmiObject -query ‘select * from SoftwareLicensingService’).OA3xOriginalProductKey

  • Command Prompt (CMD)Open an administrative Powershell windows and type:
    wmic path softwarelicensingservice get OA3xOriginalProductKey

  • Windows Scripting Host (VBS)

    If you run these commands in a pre-Windows 10 environment then you get a blank result!
    But the key will still be there, if you have a activated device.
    This can come in very handy with CMDB or other inventarisation purposes.

    So where is it and how to handle this?

    This script reads the Registry key and converts this to the correct format.
    You will get the product Key which is installed on that system! GOOD

    Set oShell = CreateObject(“WScript.Shell”)
    Set oFSO=CreateObject(“Scripting.FileSystemObject”)

    outFile=”C:\Temp\Key.txt”
    Set oFile = oFSO.CreateTextFile(outFile, True)
    oFile.Write ConvertToKey(oShell.RegRead(“HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DigitalProductId”)) & vbCrLf
    oFile.Close

    Function ConvertToKey(Key)

    Const KeyOffset = 52
    i = 28
    Chars = “BCDFGHJKMPQRTVWXY2346789”

    Do
    Cur = 0
    x = 14

    Do
    Cur = Cur * 256
    Cur = Key(x + KeyOffset) + Cur
    Key(x + KeyOffset) = (Cur \ 24) And 255
    Cur = Cur Mod 24
    x = x -1

    Loop While x >= 0
    i = i -1
    KeyOutput = Mid(Chars, Cur + 1, 1) & KeyOutput

    If (((29 – i) Mod 6) = 0) And (i <> -1) Then
    i = i -1
    KeyOutput = “-” & KeyOutput
    End If

    Loop While i >= 0
    ConvertToKey = KeyOutput
    End Function

Happy Reading keys.

How-to: Fix Windows Update error 0xca00a000

So recently I ran into a Windows Update error. I am in the WindowsInsider rings, so it is not uncommon to me that errors can occur!

But this one was new, so what can I do?
The error at hand was: Error 0xca00a000 

2019-04-14 18_51_20

Well the first thing I normally do in cases like this is:

  • Stop the Windows Update service
  • Delete the C:\Windows\SoftwareDistribution folder
  • Start the Windows Update service
  • Check Windows Updates again
  • Et Voila! There we go!

Easy enough, and what happened? It all started working again, so that was an easy one this time!

I read some posts on Twitter that the Seach service was involved. I checked but that was not the case here..

Me happy WindowsInsider again 🙂

HOW-TO Microsoft Windows Store apps fail to update – Error 0x803FB002

Sometimes when you have a Windows Store app on Windows 10 there is an update available. So you get a nice fly-out that there is one.

And you think, ok let’s do this update!

You click ‘Okay’ to update, and then: ERROR

But why? And how to resolve this error…

First what happens:

2019-02-27 08_35_59

2019-02-27 08_35_40

2019-02-27 08_36_09

And then how to fix this.

Well because it is a Windows Store app we can go to the Store and see what is going on with the app. In this case I see an error with the Feedback Hub app. Click on the ‘See details’ to reveal what is going on!

2019-02-27 08_46_37

The Details page:

2019-02-27 08_46_19

Aha an error 0x803FB002

This usualy indicates a problem with a Store app and it needs a Reset.

After giving the app a Reset (that is the round arrow associated with the app) all is functioning again!

2019-02-27 08_47_31

Have a good one!

Announcing Windows 10 Insider Preview Build 18342 – And why it may fail to present itself!

A nice and happy message from the Windows Insider Program website, another Build (#18342) is available.

So I rushed to my Windows Insider machines and, huh wait no update on 1 device. That’s odd, the other devices in the Fast Ring are ok, but this one is not…WHY?

Wel then there was the update on the website:

Hello Windows Insiders, today we are releasing Windows 10 Insider Preview Build 18342 (19H1) to Windows Insiders in the Fast ring.

[UPDATED] PCs with the following chipsets processor model numbers will not receieve this build due to an issue with Connected Standby: Intel64 Family 6 Model 142 and Intel64 Family 6 Model 158. To check to see if your processor falls into these two buckets:

1: Open Device Manager by right-clicking on the Start button on your taskbar.
2: Open up the Processors group and right-click on one of the processors listed (you will see multiple for each core of the processor in your PC).
3: Click properties and go to the Details tab.
4: Choose “Hardware Ids” in the property dropdown. This will give you the model number of your processor.

Hmm let’s check 🙁

2019-02-21 19_03_48

Ow well I guess I will have to skip this Build on this machine. Luckely I have some more machines 🙂

Skip ahead is open – for a short time, so be quick #WindowsInsiders

As Microsoft is getting ready for the release of another feature realse of Windows 10, coming April 2019, the development for the next Build has already started.

And if you are in the Windows Insider Preview you can apply for the Skip Ahead option.

This means that you don’t get this current Build anymore but start with the new one, OW yeah! But as said, it’s a limited seats program. If you want in, be fast!

2019-01-31 13_54_54

You can change your setting at ‘Settings‘ – ‘Update and Security‘ – ‘Windows Insider Program

Happy testing!

2019-01-31 13_56_48

2019-01-31 13_56_57

Bitlocker wizard – brought to you by Microsoft Intune

If you enroll a Windows 10 device in Microsoft Intune you can manage this device as a Mobile Device, hence the name Mobile Device Management (MDM). And of course you can do all sorts of fantastic things with it!

You can trow policies at the device, configuration items, software, updates et cetera et cetera!
And most of this can be done transparant (i.e. invisible) to the user of this device.

But sometimes it good to show something to a user. Recently I was in a little discussion with a collegue about enabeling Bitlocker on a managed device. Of course you should do it when preparing a device, but this was a migration and the devices where not Bitlockered 🙁

So you can do this invisible, but I stated that it would be a GOOD thing to show the user that the drive would be encrypted so they know that their data is protected.

So and how does this look like?

So first the user is informed that his or her device needs to be encrypted.

2019-01-17 22_32_36

And if the user clicks on the flyout or message a Bitlocker Wizard starts.

2019-01-17 22_40_29

It could be that the device the user is using doesn’t meet the requirements of Bitlocker. Found here: https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq

And then this baby will pop-up!

2019-01-17 22_43_50

But if we are all set and good to go we can continue with the wizard. Backing up the recovery key. I can say that the first option – Save to your cloud domain account is by far the best option!

2019-01-17 22_51_58

Saving the key 🙂

2019-01-17 22_52_43

To encrypt your disk you have tweo options, self-explaning I think!

2019-01-17 22_52_53

And off we go!

2019-01-17 22_53_03

You can monitor the progress

2019-01-17 22_53_14

And if you close the screen above, well you find the progress in the taskbar. Nice.

2019-01-17 22_53_29

And after a while, it’s pretty quick on those nice SSD’s, your disk is encrypted. Safe.

2019-01-17 22_53_46

Enroll in Olympia corp – Upgrade your Windows 10 edition from Pro to Enterprise (2) #WindowsInsiders

Find the Apply phase here.

Microsoft has a test and acceptance environment for the Windows 10 Insiders. It’s called Olympia. It’s a complete solution, with a website, Office 365, Intune et cetera.

You will find the website here: https://olympia.windows.com

In a previous blog  we applied for the Olympia corp, and now it is time to enroll in it!
To keep your Windows 10 edition read this blog!

Enroll

So you got the message that your Olympia account and it is time to Enroll! Find the details here!

There are 2 ways to Enroll:

Choose one of the following two enrollment options:

– Keep your current Windows 10 edition

Please see Olympia Corp enrollment – keep current edition.

– Upgrade your Windows 10 edition from Pro to Enterprise

Please see Olympia Corp enrollment – upgrade to enterprise edition.

* Please note that your Windows 10 Enterprise license will not be renewed if your PC is not connected to Olympia.

The first option will keep your system almost as it is, you add an Olympia account and the policies to your system. With the second option you get an Olympia managed system, logon with your Olympia account and so on! It will also give you a Windows 10 Enterprise for Insiders license. So more to do and test, me happy 😉

So what is the experience you get with Option 2 – Upgrade your Windows 10 edition from Pro to Enterprise?

Go to Start > Settings > Accounts > Access work or school. To see this setting, you need to have administrator rights to your device (see local administrator).

2019-01-17 20_25_52

If you are already connected to a domain, click the existing account and then click Disconnect. Click Restart Later.

Click Connect, then click Join this device to Azure Active Directory.

2019-01-19 23_15_22

Enter your Olympia corporate account (e.g., username@olympia.windows.com). Click Next.

2019-01-19 23_15_47

Enter the temporary password that was sent to you. Click Sign in. Follow the instructions to set a new password.

2019-01-19 23_16_02

Update it 😉

2019-01-17 22_24_44

When asked to make sure this is your organization, verify that the information is correct. If so, click Join.

2019-01-19 23_16_17

Setting up some things 😉

2019-01-19 23_16_31

Restart and you can login with your Olympia account. The device is now a Olympia managed device. You will get policies and stuff 😉
Jippie!

First thing you will notice is the Bitlocker wizard stating that you will need to encrypt your harddrive.

You can find the proces here!

IMPORTANT NOTICE:

Your Windows 10 Enterprise license will not be renewed if your device is not connected to Olympia.

So and then you logon!

2019-01-19 23_26_31

2019-01-19 23_26_412019-01-19 23_26_562019-01-19 23_27_02