You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/image-builder-json.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to create a Bicep file or ARM JSON template to use with A
4
4
author: kof-f
5
5
ms.author: kofiforson
6
6
ms.reviewer: erd
7
-
ms.date: 03/15/2023
7
+
ms.date: 04/11/2023
8
8
ms.topic: reference
9
9
ms.service: virtual-machines
10
10
ms.subservice: image-builder
@@ -677,7 +677,7 @@ If there's an error trying to download the file, or put it in a specified direct
677
677
678
678
### Windows update customizer
679
679
680
-
The `WindowsUpdate` customizer is built on the [community Windows Update Provisioner](https://packer.io/docs/provisioners/community-supported.html) for Packer, which is an open source project maintained by the Packer community. Microsoft tests and validate the provisioner with the Image Builder service, and will support investigating issues with it, and work to resolve issues, however the open source project isn't officially supported by Microsoft. For detailed documentation on and help with the Windows Update Provisioner, see the project repository.
680
+
The `WindowsUpdate` customizer is built on the [community Windows Update Provisioner](https://developer.hashicorp.com/packer/docs/provisioners/community-supported) for Packer, which is an open source project maintained by the Packer community. Microsoft tests and validate the provisioner with the Image Builder service, and will support investigating issues with it, and work to resolve issues, however the open source project isn't officially supported by Microsoft. For detailed documentation on and help with the Windows Update Provisioner, see the project repository.
681
681
682
682
# [JSON](#tab/json)
683
683
@@ -735,7 +735,7 @@ If Azure Image Builder creates a Windows custom image successfully, and you crea
735
735
736
736
#### Default Sysprep command
737
737
738
-
```powershell
738
+
```azurepowershell-interactive
739
739
Write-Output '>>> Waiting for GA Service (RdAgent) to start ...'
740
740
while ((Get-Service RdAgent).Status -ne 'Running') { Start-Sleep -s 5 }
741
741
Write-Output '>>> Waiting for GA Service (WindowsAzureTelemetryService) to start ...'
@@ -791,7 +791,7 @@ You can distribute an image to both of the target types in the same configuratio
791
791
792
792
Because you can have more than one target to distribute to, Image Builder maintains a state for every distribution target that can be accessed by querying the `runOutputName`. The `runOutputName` is an object you can query post distribution for information about that distribution. For example, you can query the location of the VHD, or regions where the image version was replicated to, or SIG Image version created. This is a property of every distribution target. The `runOutputName` must be unique to each distribution target. Here's an example for querying an Azure Compute Gallery distribution:
793
793
794
-
```azurecli
794
+
```azurecli-interactive
795
795
subscriptionID=<subcriptionID>
796
796
imageResourceGroup=<resourceGroup of image template>
0 commit comments