|
1 | 1 | --- |
2 | | -author: mestew |
3 | | -ms.author: mstewart |
| 2 | +author: aczechowski |
| 3 | +ms.author: aaroncz |
4 | 4 | ms.prod: configuration-manager |
5 | 5 | ms.technology: configmgr-core |
6 | 6 | ms.topic: include |
7 | 7 | ms.date: 01/27/2022 |
8 | 8 | ms.localizationpriority: medium |
9 | 9 | --- |
| 10 | + |
| 11 | +## <a name="bkmk_tsico"></a> Custom icon support for task sequences and packages |
| 12 | + |
| 13 | +<!--12486335--> |
| 14 | + |
| 15 | +Previously, task sequences and legacy packages would always display a default icon in Software Center. Based on your feedback, you can now add custom icons for task sequences and legacy packages. These icons appear in Software Center when you deploy these objects. Instead of a default icon, a custom icon can improve the user experience to better identify the software. |
| 16 | + |
| 17 | +### Try it out! |
| 18 | + |
| 19 | +Try to complete the tasks. Then send [Feedback](../../../../understand/product-feedback.md) with your thoughts on the feature. |
| 20 | + |
| 21 | +1. If needed, [create a task sequence](../../../../../osd/deploy-use/manage-task-sequences-to-automate-tasks.md) or [create a package and program](../../../../../apps/deploy-use/packages-and-programs.md#create-a-package-and-program). |
| 22 | + |
| 23 | +1. Open the properties of a task sequence or package. |
| 24 | + |
| 25 | +1. For a task sequence, switch to the **More Options** tab. For a package, the icon option is on the **General** tab. |
| 26 | + |
| 27 | + > [!NOTE] |
| 28 | + > The existing task sequence property page for **Performance** is now renamed to **More Options**. |
| 29 | +
|
| 30 | +1. In the section for the icon, select **Browse**. Select an icon from the default shell library, or browse to another file in a local or network path. |
| 31 | + |
| 32 | + - It supports the following file types: |
| 33 | + - Programs (`.exe`) |
| 34 | + - Libraries (`.dll`) |
| 35 | + - Icons (`.ico`) |
| 36 | + - Images (`.png`, `.jpeg`, `.jpg`) |
| 37 | + - The file doesn't need to be on clients that you target with the deployment. Configuration Manager includes the image with the deployment policy. |
| 38 | + - The maximum file size for an image is 256 KB. |
| 39 | + - Icons can have pixel dimensions of up to 512 x 512. |
| 40 | + |
| 41 | +After you save the properties, deploy the task sequence or package, if it's not already deployed. For more information, see one of the following articles: |
| 42 | + |
| 43 | +- [Deploy a task sequence](../../../../../osd/deploy-use/deploy-a-task-sequence.md) |
| 44 | +- [Deploy packages and programs](../../../../../apps/deploy-use/packages-and-programs.md#deploy-packages-and-programs) |
| 45 | + |
| 46 | +When clients receive the deployment policy, they'll display the icon in Software Center. |
| 47 | + |
| 48 | +> [!NOTE] |
| 49 | +> To take full advantage of new Configuration Manager features, after you update the site, also update clients to the latest version. While new functionality appears in the Configuration Manager console when you update the site and console, the complete scenario isn't functional until the client version is also the latest. |
| 50 | +
|
| 51 | +### Known issues with icons for legacy packages |
| 52 | + |
| 53 | +- To change the icon on an existing package that's already deployed, change another setting of the package or create a new deployment.<!-- 13040507 --> |
| 54 | + |
| 55 | +- Custom icons only appear for legacy packages that you deploy to device collections. They don't yet support user-based deployments. |
0 commit comments