Administrator Guide

in the group immediately or at a scheduled time before the device check-in, you must schedule the policy. After you
schedule the policy, the job status displays the count of devices that are already present in the group.
NOTE: The job status of the newly added device count that is checked in to Wyse Management Suite is not displayed.
12. Specify the number of minutes the message dialog box should be displayed on the client in the Timeout (1-999 min) box.
Timeout displays a message on the client that gives you time to save your work before the installation begins.
13. To stop the installation process after a defined value, specify the number of minutes in the Application Installation
Timeout field. The default value is 60 minutes.
14. Click Save to create a policy.
A message is displayed to enable the administrator to schedule this policy on devices based on group.
15. Select Yes to schedule a job on the same page.
16. Select any of the following options:
● Immediately—Server runs the job immediately.
● On device time zone—Server creates one job for each device time zone and schedules the job to the selected date or
time of the device time zone.
● On selected time zone—Server creates one job to run at the date or time of the designated time zone.
17. To create the job, click Preview and schedules are displayed on the next page.
18. You can check the status of the job by going to the Jobs page.
Create and deploy advanced application policy to Dell Generic
Clients
Steps
1. Copy the application and the install scripts (if necessary) in the genericClientApps folder of the local repository or the
Wyse Management Suite remote repository.
NOTE:
You can deploy and install only Dell-signed applications and scripts (DHC Fish scripts, DCA-Enabler packages,
DHC Bundles, or DHC ISO Image files) on Dell Generic Clients.
2. Go to Apps & Data > App Inventory > Generic Client and verify that the application is registered.
3. Go to Apps & Data > App Policies > Generic Client.
4. Click Add Advanced Policy.
Add Advanced App Policy page is displayed.
5. Enter the Policy Name.
6. From the Group drop-down list, select the group.
7. Select the Sub Groups check box to apply the policy to sub groups.
8. From the Task drop-down list, select the task.
9. From the OS Type drop-down list, select the operating system.
10. Select the Filter files based on extensions check box to filter the applications.
11. Click Add app, and select one or more applications under Apps.
12. If you want the system to reboot after the application is successfully installed, select Reboot.
13. Click Add app and repeat the step to add multiple applications.
NOTE:
To stop the application policy at first failure, select Enable app dependency. If this option is not selected,
failure of an application affects the policy implementation.
If the application files are available on multiple repositories, then the number of repositories is displayed next to the file name.
14. To deploy this policy to a specific operating system or a platform, select either OS Subtype Filter or Platform Filter.
15. Specify the number of minutes the message dialog box should be displayed on the client.
A message on the client that gives you time to save your work before the installation begins.
16. To enable delay in implementation of the policy, select the Allow delay of policy execution check box. If this option is
selected, the following drop-down menus are enabled:
● From the Max Hours per Delay drop-down list, select the maximum hours (1–24 hours) you can delay running the
policy.
● From the Max delays drop-down list, select the number of times (1–3) you can delay running the policy.
84
Apps and data