Using User Readiness Records to Schedule Users for OS Deployment
App Portal’s User Readiness feature can be used to extend user self-service functionality of operating system images, as well as required applications. It can be used to control which users are permitted to select an OSD catalog item, and to specify when they can schedule a deployment. You can set a start and end date to establish a deployment window for each user, including recommended blackout dates, and notify the users of these constraints via email.
For example, you could use these user readiness constraints to prevent all enterprise users from requesting and scheduling an OS deployment at the same time. You could also use these constraints if you wanted to perform an OS deployment in a controlled manner over a period of time, but you still wanted to allow the users to initiate the installation.
Note:User Readiness is only applicable if the requester selects the Reimage my computer (MACHINENAME) with a new Operating System or Build an unknown computer and migrate my data from MACHINENAME to the new computer options on the Choose Target panel of the Checkout Wizard. User Readiness is not applicable if the requester selects the Image a new computer or existing computer option.
To learn more about App Portal’s User Readiness feature, see the following topics:
| • | About User Readiness |
| • | Creating a User Readiness Record |
| • | Modifying a Task Sequence Catalog Item to Require a User Readiness Record |
| • | Bulk Import of User Readiness Data |