cleanups

content/posts/2022/AVS-to-internet-able-or-not/index.md

@@ -21,7 +21,7 @@ As you all (probably) know by now Azure VMware Solution is a managed service off
 By default, after initial deployment of Azure VMware Solution, virtual machines do not have the ability to egress to the Internet. One of the options to enable Internet access is to "flip" the "Internet Enabled" toggle in the connectivity pane of the management blades in the Azure Portal:
 
 
-{{< figure src="/images/blogImages/2022/avs-to-internet-or-not/AVS-Connectivity-Settings-InternetEnabled.jpg" alt="internet enabled switch" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/avs-to-internet-or-not/AVS-Connectivity-Settings-InternetEnabled.jpg" alt="internet enabled switch" >}}
 
 Looks easy, but what does it do?
 

content/posts/2022/arc-ssh-windows-linux/index.md

@@ -47,7 +47,7 @@ Now you can click, "Connect in browser". This will launch an [Azure Cloud Shell]
 ## GOTCHA
 
 You may hit your first error here.
-{{< figure src="/images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-linux-vm-error-1.png" alt="Connect via portal to linux Azure Arc machine button - connection error" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-linux-vm-error-1.png" alt="Connect via portal to linux Azure Arc machine button - connection error" >}}
 
 The error may seem a little strange, it seems it is using port 66535 to dp a port lookup - like a proxy lookup - see [here](https://serverfault.com/questions/915724/connection-closed-by-unknown-port-65535-when-ssh-using-ad-creds-on-rhel-machine) as an example of this. It is still wanting to connect to port 22, the normal ssh port. _So how do we fix this?_
 
@@ -58,15 +58,15 @@ azcmagent config set incomingconnections.ports 22
 ```
 
 Run this command on your linux machine (sudo will be needed)
-{{< figure src="/images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-linux-vm-fix1.png" alt="Update port number from azcmagent" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-linux-vm-fix1.png" alt="Update port number from azcmagent" >}}
 and then we can connect  
-{{< figure src="/images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-linux-vm-connect-1.png" alt="Connect via portal to linux Azure Arc machine is successful" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-linux-vm-connect-1.png" alt="Connect via portal to linux Azure Arc machine is successful" >}}
 
 ### Windows VM
 {{< figure src="/images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-windows-vm.png" alt="Connect via portal to Windows Azure Arc machine" height="300" width="900" >}}
 
 The steps for connection from the portal and the required **Az**ure **c**onnected **ma**chine **agent** commands are the same. However we do need to get SSH working on the Windows Server, this is actually quite easy and simply needs some copy and paste, see [here](https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse?tabs=powershell). Once you have done that, your connection will work.
 
-{{< figure src="/images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-windows-vm-connect-1.png" alt="Connect via portal to Windows Azure Arc machine is successful" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/arc-ssh-windows-linux/connect-button-portal-windows-vm-connect-1.png" alt="Connect via portal to Windows Azure Arc machine is successful" >}}
 
 So there you have it, an SSH connection from the Azure portal to a Windows AND Linux Arc-enabled machine.

content/posts/2022/openssh-powershell/index.md

@@ -50,7 +50,7 @@ $pubKey
 
 Example output from $pubkey below, this is what you need to copy and paste within the Azure Portal when creating a Linux VM.
 
-{{< figure src="/images/blogImages/2022/openssh-powershell/ssh-key-example.jpg" alt="ssh-key-example" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/openssh-powershell/ssh-key-example.jpg" alt="ssh-key-example" >}}
 
 If you want to use this key with an existing, you can. :smile: . We can perform a task similar to ssh-copy-id. Update the ***$destinationIp*** as needed.
 

content/posts/2022/poc-vwan-avs/index.md

@@ -47,9 +47,9 @@ param deployExRConnection bool = true
 What to expect when deploying?
 
 1. You will get an ExpressRoute gateway. I set this as a "true" boolean value to cater for this.
-1. The deployment will happen over 2 resource groups - if deploying the "vnetconnection" option.  {{< figure src="/images/blogImages/2022/vwan-avs-poc/2resourcegoups.jpg" alt="deployment screenshot showing the 2 deployed resource groups" >}}
-1. It will look like nothing is happening in the Virtual WAN resource group. Show hidden items here.  {{< figure src="/images/blogImages/2022/vwan-avs-poc/showHiddenTypes.jpg" alt="deployment screenshot showing hidden items checked" >}}
-1. The deployment, if choosing anything Gateway related (VPN Gateway or ExpressRoute gateway) will take some time - up to 35 minutes.  {{< figure src="/images/blogImages/2022/vwan-avs-poc/vHubDeploy.jpg" alt="deployment screenshot showing times" >}}
+1. The deployment will happen over 2 resource groups - if deploying the "vnetconnection" option.  {{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/vwan-avs-poc/2resourcegoups.jpg" alt="deployment screenshot showing the 2 deployed resource groups" >}}
+1. It will look like nothing is happening in the Virtual WAN resource group. Show hidden items here.  {{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/vwan-avs-poc/showHiddenTypes.jpg" alt="deployment screenshot showing hidden items checked" >}}
+1. The deployment, if choosing anything Gateway related (VPN Gateway or ExpressRoute gateway) will take some time - up to 35 minutes.  {{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/vwan-avs-poc/vHubDeploy.jpg" alt="deployment screenshot showing times" >}}
 1. The deployment will deploy a VPN Gateway (on-premises to Azure)
 1. The deployment will deploy a ExR Gateway (Azure to AVS)
 

content/posts/2022/using-arg-tolock-resources/index.md

@@ -145,6 +145,6 @@ foreach ($queryItem in $queryItems)
 
 Results can be seen below. Our Locks are now in place. Since my account is an **owner**, I can delete the lock(s), *non-owner(s)* would **NOT** be able to delete locks.  
 
-{{< figure src="/images/blogImages/2022/using-arg-tolock-resources/resulting-locks.jpg" alt="resulting locks in azure" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2022/using-arg-tolock-resources/resulting-locks.jpg" alt="resulting locks in azure" >}}
 
 This code and concept can be easily updated or modified to meet different your specific requirements.

content/posts/2023/avs-ldaps-configure-part2/index.md

@@ -31,7 +31,7 @@ Before we can configure integration with an external identity store (e.g. Active
 The first step in configuring DNS name resolution from the Azure VMware Solution networks (management and workload segments) is to add a DNS zone for Azure VMware.
 Login to the Azure Portal and select the Azure Active Directory tenant and Azure subscription where you have deployed your Azure VMware Solution Private Cloud.
 
-{{< figure src="/images/blogImages/2023/avs-ldaps-configure-part2/open-DNS-configuration-pane.jpg" alt="Open DNS Configuration" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2023/avs-ldaps-configure-part2/open-DNS-configuration-pane.jpg" alt="Open DNS Configuration" >}}
 
 As depicted in the image above:
 
@@ -44,7 +44,7 @@ The Azure Portal blade for configuring the Azure VMware Solution DNS configurati
 
 The Azure VMware Solution DNS configuration pane opens the section where "conditional DNS forwarder" zones are configured.
 
-{{< figure src="/images/blogImages/2023/avs-ldaps-configure-part2/configure-the-required-DNS-zones-details-1.jpg" alt="Advanced DNS Configuration" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2023/avs-ldaps-configure-part2/configure-the-required-DNS-zones-details-1.jpg" alt="Advanced DNS Configuration" >}}
 
 As shown in the image above:
 
@@ -57,13 +57,13 @@ As shown in the image above:
 
 After a few minutes, the DNS FQDN zone, **avsemea.com**, will be listed in the DNS blade for your Azure VMware Solution Private Cloud as shown below:
 
-{{< figure src="/images/blogImages/2023/avs-ldaps-configure-part2/configure-the-required-DNS-zones-details-2.jpg" alt="Advanced DNS Configuration 2" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2023/avs-ldaps-configure-part2/configure-the-required-DNS-zones-details-2.jpg" alt="Advanced DNS Configuration 2" >}}
 
 ## Attach the DNS zone configuration to the NSX-T DNS forwarder service ##
 
 Now that we created the DNS conditional forwarder zone we need to attach this zone to the NSX-T DNS service running in Azure VMware Solution to enable NSX-T to actually use the DNS conditional forwarder zone for use.
 
-{{< figure src="/images/blogImages/2023/avs-ldaps-configure-part2/Attach-the-DNS-zone-configuration-to-the-NSX-T-DNS-forwarder-service-1.jpg" alt="DNS and NSX-T Forwarder" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2023/avs-ldaps-configure-part2/Attach-the-DNS-zone-configuration-to-the-NSX-T-DNS-forwarder-service-1.jpg" alt="DNS and NSX-T Forwarder" >}}
 
 In the Azure VMware Solution DNS blade:
 
@@ -74,7 +74,7 @@ In the Azure VMware Solution DNS blade:
 
 When the change to the NSX-T DNS service is effectuated the **avsemea.com** DNS zone will now be listed in the DNS service configuration:
 
-{{< figure src="/images/blogImages/2023/avs-ldaps-configure-part2/configure-the-required-DNS-zones-details-2.jpg" alt="Advanced DNS Configuration 2" >}}
+{{< figure src="https://raw.githubusercontent.com/fskelly/cloud.fskelly.com/main/static//images/blogImages/2023/avs-ldaps-configure-part2/configure-the-required-DNS-zones-details-2.jpg" alt="Advanced DNS Configuration 2" >}}
 
 After this step the configuration of the Azure VMware Solution DNS service is complete.
 The next article in this series will describe the detailed steps in configuring LDAPS integration through the Azure portal or automation where possible.