In scenario 4 described above, it was assumed that the IT administrator populated the ComputerPackages table in advance of the operating system deployment to that computer. An alternative approach would be to set up a Zero Touch Provisioning service to allow users themselves to populate the tables. Approvals could be obtained for each application requested; once the approval has been granted, a RunScript building block or equivalent business rule could be used to store a record on the ComputerPackages table (retrieving the MAC address of the computer from the SMS database, as the provisioning request would only know the name of the computer). A similar service could be defined to allow the user to remove existing records from the table. In effect, this service would be the equivalent of the software delivery sample services included with Zero Touch Provisioning except that instead of telling SMS to deliver the package to the computer now (by adding the computer to the appropriate collection for the package requested), it stores the request in a table where the Zero Touch Installation process can act on the request during the deployment process. The actual implementation of these services is beyond the current scope of this document.
| 
