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/dev-box/how-to-write-image-definition-file.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,8 +68,8 @@ Projects can help you manage Dev Box resources efficiently. By assigning each de
68
68
69
69
### Assign permissions for project admins
70
70
71
-
To attach a catalog to a project, you must have Project admin or Contributor permission for the project.
72
-
To learn how to assign Project admin permission, see [Grant administrative access to Dev Box projects](how-to-project-admin.md).
71
+
To attach a catalog to a project, you must have Project Admin or Contributor permission for the project.
72
+
To learn how to assign Project Admin permission, see [Grant administrative access to Dev Box projects](how-to-project-admin.md).
73
73
74
74
### Enable project-level catalogs
75
75
@@ -102,9 +102,9 @@ You can create and test image definition files by using Visual Studio Code. In a
102
102
1. The image definition file runs and applies the specified tasks to your test dev box. Inspect the changes and check the Visual Studio Code terminal for any errors or warnings generated during the task execution.
103
103
1. When the image definition file runs successfully, upload it to your catalog.
104
104
105
-
### System tasks and User tasks
105
+
### System tasks and user tasks
106
106
107
-
You can use both System and User tasks in your image definition file. The tasks section of the image definition file is divided into two sections: System tasks and User tasks. Both sections share the same parameters based on the task definitions in your catalog.
107
+
You can use both system and user tasks in your image definition file. The tasks section of the image definition file is divided into the following sections. Both sections share the same parameters based on the task definitions in your catalog.
108
108
109
109
-**System tasks**: These tasks run as `LocalSystem` during the provisioning stage of the dev box. They're typically used for system-level configurations, such as installing software or configuring system settings that require administrative privileges.
110
110
-**User tasks**: These tasks run as the user after the user's first sign-in to the dev box. They're typically used for user-level configurations, such as installing user-specific applications or configuring user settings under user context. For example, users often prefer to install Python and Visual Studio Code under user context instead of systemwide. Put WinGet tasks in the `userTasks` section for better results when they don't work under tasks.
@@ -194,4 +194,4 @@ You can make adjustments to the customization file and create a new dev box to t
194
194
Now that you have an image definition file, upload it to a catalog and attach the catalog to a project. The image definition file is used to configure and create dev boxes for your development teams.
195
195
196
196
> [!div class="nextstepaction"]
197
-
> [Configure imaging for Dev Box team customizations](how-to-configure-customization-imaging.md)
197
+
> [Configure imaging for Dev Box team customizations](how-to-configure-customization-imaging.md)
0 commit comments