2018-12-24

Using a Custom FQDN (ExternalDomainSuffix) for you Azure Stack Development Kit (ASDK) version 1811

I used to only write my blog in Swedish, but since I think that this info might be of interest outside this quite narrow language it will be in English

There are many reasons for why you would like to use a custom FQDN for you Azure Stack Development Kit (ASDK) installation. One of them might be that you have more than one ASDK running and want to be sure not to make changes to the wrong one (off cource I would never do something like that... but other might *cough*).

We have been using this method for quite some time to have different names on the different ASDK installations.

So what we want to do is have a custom domain suffix (marked with green) but running version 1811 (marked with blue)


Why this blogpost

Well basically the reason is that in the 1811 version of the ASDK Microsoft changed quite alot in the installation script (that happens alot we have seen :), so why not share this info if we can.

If you are in a hurry just read the "Disclaimer" and the "TL;DR" in the end. :)

Disclaimer

This is no fun to write, but we all know this.

The method described here is NOT supported in any way. We have been using this (or a similar method) for quite some time (more or less since TP3) and it has been working for us. This does not mean that we can guarantee that it will work for you. It will not be supported by us. Neither will Microsoft support this.
If you get in trouble, the only answer I can give you is to do a clean reinstall (and if you work with ASDK then you are use to do reinstalls.. we do that ALOT :))

So how to change the ExternalDomainSuffix (FQDN)

Well. You dont... 
At least you don't change it on a running installation. You set it when you install the ASDK and here I'll show you how.

What the Externaldomainsuffix (FQDN) should be is hardcoded in the installation files. And the exact place has changed a bit in the different builds of ASDK.


1. Make sure that you have finalized the "Download and extract the ASDK"-step, and also the "Prepare the ASDK host computer".

2. When booted into CloudBuilder.vhdx image you should log in as administrator (Basically this should be done when at step 1 in "Deploy the ASDK - Installer")

3. Open an elevated PowerShell console and go to "C:\CloudDeployment\". There we should search for "azurestack.external" in the install-files.
The thing is that we won't find anything. That's because the install-files are still not expanded.

4. To expand the install-files we need to go to "C:\CloudDeployment\Setup\" and there run the "BootstrapAzureStackDeploument.ps1"
This will expand quite a lot of new files (have a look around if you like. You can learn ALOT from just browsing these files).

5. Anyways... Now we have all the files then if we do the same search again then we get quite a lot of hits.
Here I should explain.. I took the screenshots from two different installations of one of the ASDKs I run. On one installation I used Powershell for searching, and on the other I used Command Prompt... Off course I messed up and some of the screenshots got lost (I actually think I never saved them... Yeah, I feel so smart sometimes) and therefore this one is a Command Promt.
To do a new screenshot would either make me fake the entire thing, or do some fancy MS Paint cut-and-paste, or make me do another reinstall of the ASDK just to get one screenshot with the correct background color.. Nope, It's christmas now... I have presents to attend to...

The files we are interested in are the .ps1 files in the beginning. The .psm1 files are interesting to, but if you look in them you'll see that these rows are just examples and not used in the script so there is no harm leaving them as is..

6. Open "C:\CloudDeployment\Setup\Common\DeploySingeNodeCommon.ps1" and change the $ExternalDomainSuffix to the one you want instead.
eg: If you want the normal user portal to be "https://portal.local.mypersonalasdk.contoso.com" then you should type
  $ExternalDomainSuffix =" mypersonalasdk.contoso.com",

7. Open "C:\CloudDeployment\Setup\DeploySingeNode.ps1" and change the $ExternalDomainSuffix to the one you want instead (this needs to be the same as in step 6)

8. Continue your normal installation from step 1 in "Deploy the ASDK - Installer"
When you are finished with the installation then you should be able to connect to "adminportal.local.[yourdomainsuffix]" and it should look something like this:


TL;DR

1. Download and save the file "UpdateExternalFQDN.ps1" in the "C:\CloudDeployment\Setup" folder when you are booted into CloudBuilder.vhdx image and logged in as administrator. (Basically this should be done when at step 1 in "Deploy the ASDK - Installer" )

2. Open an elevated PowerShell console and go to the "C:\CloudDeployment\Setup" folder

3. Run the "UpdateExternalFQDN.ps1" script  (that you downloaded in step 1) and specify your desired FQDN

4. Continue your normal installation as you normally do. :)

5. After a successful installation then connect to the admin portal as "adminportal.local.[yourFQDN]" and the user portal as "portal.local.[yourFQDN]".
Like this:

(and here you see the my domain and the new ASDK version).

Here is the script:

And here is the command to run the script:



Inga kommentarer:

Skicka en kommentar

Related Posts Plugin for WordPress, Blogger...