The OS Installation section is just terminology and does not mean you can only deploy an image in there. You could actually capture an image immediately followed by deploying an image in a backup then migrate type scenario. So don't get hung up on the section heading.
The path to the image file asks for the image file name as well. So if you have chosen a Capture Image action in your template, point to the UNC path where you want to store is and give the image a name. Unlike OSD scripts, provisioning doesn't auto-name the image file but you could use an inventory variable using global variables such as %computer - device name% to auto-name the image.
Admittedly, provisioning isn't as simple to get going because it doesn't have a wizard-driven interface, but if you look at your OSD script and consider how to replicate the steps it follows then you won't go far wrong. Also, it is quite common for a capture to be done using an OSD script but deployment via template just because a capture rarely needs the advanced features of provisioning.
Mark McGinn
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
Update - New v2.3 Adds Process Monitoring & Historical Analysis for Concurrency and Device Based
The One-Stop Shop for LANDesk Enhancements
- Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing