1 of 1 people found this helpful
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.
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
I have imaging with Provisioning working great with a Hardware independent image that I layer software onto. Because of the amount of different variations of software as well as several larger software installs that we'd rather not deploy, I have to capture a Hardware specific image to include in the templates. Up until now, like you had mentioned, I have been using the OSD Capture script to capture my images, but I was asked to research the capture in the provisioning templates. What is happening is that sometime when we capture an image, the osd capture process causes issues with the image on the captured computer so we have to go back and reimage the machine. One of our guys was told that capturing with provisioning would alleviate this issue, so I was going to give it a try.
I've tried to assign a generic name to the proposed captured image and when it gets to imagew it asks for the specified file as if it's trying to image the machine with it. It's pretty confusing. I will try the variable to see if that helps.
Just an FYI I got it. It actually was a boneheaded mistake on my part. I had the wrong command line perimeters, once I changed them to the correct ones it works! I initially had them as the deplyment commands /r /o /d:0 /f: etc... They needed to be /b /d:0 /rb:0 /f: etc...