Category: Development

How to delete an Azure Active Directory (ADD) Tenant

You may have discovered that deleting an Azure Active Directory is a particularly frustrating experience that ultimately ends in failure. The new portal have improved things a bit, by running through a series of check before the delete button is enabled.

You may need to go back to the Classic portal (https://manage.windowsazure.com) to see some of the objects/resources to delete.

However, although this will help you remove ‘most’ of what you need to, unfortunately NOT all!

In this case I got a “Unable to delete directory

Continue reading “How to delete an Azure Active Directory (ADD) Tenant”

How to add Open Source License to your GitHub repository

When you first create a new repository in GitHub, you get a very handy drop down of Open Source Licenses options to add. This is really useful and saves you trying to find the standard copy somewhere.

If you don’t choose one when you create the repo, then there is a sneaky way to get that drop down back and easily add a standard license file later. Continue reading “How to add Open Source License to your GitHub repository”

Azure App Service – Force redirect from HTTP to HTTPS the easy way!

Once you have uploaded your SSL certificates to your Azure App Service and then configured the bindings (if you are using your own custom domains), there are two ways to force ALL requests to be redirected  from HTTP to HTTPS. The ‘Developer way‘ and the ‘Easy, no code way‘! Continue reading “Azure App Service – Force redirect from HTTP to HTTPS the easy way!”

“Resource group not found” when using PowerShell with Azure (especially DSC)

I have been banging my head against a wall wondering why my Azure PowerShell DSC commands like

Publish-AzureRmVMDscConfiguration  ".\MyDSCConfig.ps1" 
            -ResourceGroupName "VM-Training" -StorageAccountName "hmsvmtraindsc"

was failing with a “Resource Group not found“, even though other commands worked with that Resource Group and my current context.

The answer is do NOT use the x64 build of PowerShell or the “Windows PowerShell ISE”!

Use the x86 versions for now!

I found this advice at the bottom of this page https://azure.microsoft.com/en-us/blog/turn-on-windows-feature-using-dsc-cli/, and switching to the x86 ISE worked for me!

However, when I tried to reproduce the issue on the x64 ISE, the command worked fine??? However, by that time the Blob container had been created by the x86 version, so who know?

If I get time I will try to reproduce the error, otherwise please post a comment if the same thing happened to you.

 

Bulk update EXIF ‘Shot Taken Date’ on JPG photos using ‘ImageProcessing Console’.

If, like me, you have digital photo’s stretching back to the early days of digital cameras and even scans of film and slides, then you may have the same issue I had attaching the right date to the file. I have over 35,000 digital images, so developed a little command line tool to help called ‘Image Processing Console‘ (https://github.com/nrogoff/ImageProcessingConsole).

Continue reading “Bulk update EXIF ‘Shot Taken Date’ on JPG photos using ‘ImageProcessing Console’.”

Finding Azure VM Images using PowerShell

I have been trying to write a PowerShell command that would help me find the right Azure VM Image to use when creating a new Virtual Machine.

In the Portal UI you get something not very useful like the following when search for a VM Image. No unique identifying information to locate the image from script.

2016-12-09_09-55-17

However, when using such a simple search in PowerShell, you get a lot more data returned and working out which one you want is a bit of a pain.

After a few iterations I thought I would share it and save others the time.

The first thing is how to filter the huge list to just the images that contain what I am after, whether that’s a service or OS. It turns out that there is not much consistency to help here, but two fields stand out for searching.

  • Label – The publicly visible name of the image
  • ImageFamily – A sometimes useful category that can be used to filter, but depend on the type of image. Often this value is either the same as the Label or some cryptic value.

Once filtered, there seemed to be a number of additional fields that may vary and influence your decision as to which VM Image you want when creating a new VM.

  • OS – This is usually repeated in the Label so have left this off the listing.
  • PublisherName – Was hoping this may match the Portal listing, but no!
  • PublishedDate – The date the image was published. I have use this to sort the list, showing the latest first.
  • Category – I was also hoping this would match the Portal listing, but no! This seems to only indicate if the image is public or …something else! I am only interested in Public ones.
  • IsPremium – This indicates if the image includes any licensing. If false, it’s more than likely a ‘Bring You Own License’ (BYOL)
  • ShowInGui – I assume when this is ‘true’ then the image is available in the portal. Again I think unless you have a very specific image in mind, this should also be ‘true’.
  • RecommnededVMSize – sows the recommended VM size to use

I was looking for a simple “Windows Server 2016 Datacenter”. Ideally the recommended or default. For this case it was possible to filter by the ImageFamily. However I noticed this was not going to be so easy for other things such as ‘SQL Server’ images as some ImageFamily were return with text like ‘Windows SQL14-PCU-MAIN-12.0.5000.0-SQLENTCORE.ENU.Nov-WS2012R2-127gb.09.27.16.01.042’ , so opted for filter on the Label instead.

$searchTerm = "*Windows Server 2016*"
Get-AzureVMImage | Where-Object {$_.Label -like $searchTerm -and $_.Category -eq "Public" -and $_.ShowInGui -ne $false} | Sort-Object PublishedDate -Descending | Select-Object Label,PublisherName, PublishedDate,IsPremium,RecommendedVMSize,ImageName | Format-Table

The line above will produce a table output as shown below, but the ImageName, which is probably what you are after, may well be truncated.

2016-12-09_12-02-07
$searchTerm=”*SQL Server 2014*”

 

2016-12-09_12-05-55
$searchTerm=”*Windows Server 2016 Datacenter*”

So, once you have honed your search term down, then run this smaller table version.

Get-AzureVMImage | Where-Object {$_.Label -like $searchTerm -and $_.Category -eq "Public" -and $_.ShowInGui -ne $false} | Sort-Object PublishedDate -Descending | Select-Object Label,ImageName | Format-Table

which produces something like the listing below, from where you can copy the full ImageName.

2016-12-09_12-12-58