Hi All, i tested a workaround to deploy OEM images or images without having to use sysprep, meanwhile it could be useful in bypassing issues on ConfigureTargetOS action in provisioningMaybe it’s not really a supported procedure but it worked for me, I hope you will appreciate.
CONSIDERATIONS
Maybe it’s not more useful and a bit old-fashioned deploying non sysprepped images, but someway I found many customers with this need for a back-up, for their OEM environment to avoid some boring post OS configuration or software distribution.
My principal mean was to underline the step in which we bypass the Configure Target OS action that often caused issues and get guys crazy working on it.
CTOS is finally,once for all, perfectly, explained in doc http://community.landesk.com/support/docs/DOC-6948)
"The CTOS prepares the machine to resume provisioning after the client boots into the target OS, then restarts the machine, leaving WinPE and allowing the computer to boot normally. In order for the CTOS action to work, the image that was deployed to the client MUST be sysprepped..”
If the LANDESK agent is already installed on the image you have to capture, you can copy ldprovision files and then force ldprovision.exe to run at startup using Actions.ini file of CBA.
The ldprovision agent does not need to be installed because it uses the CBA services that are already active, so it’s enough copy the few files that ldprovision.exe needs in a folder to the C: drive of the computer and then run ldprovision.exe at the right time.
When the new OS boots I select few files from \\core\ldlogon\provisioning\windows and it worked.
Why you cannot schedule template as all other tasks or distribution? It will be a marvellous thing, combining software distribution with system-configuration with reboot and so on.. also for managed devices non only for OS deployment.
I attach the file with my work
Regards all
DISCLAIMER: This process is not supported by LANDesk Support. Use this process at your own risk.