I am referencing the following document as I try to troubleshoot why my my image deployment provisioning template is hanging/failing at CTOS.
Troubleshooting Configure Target OS action in Provisioning template
calling out some language in the document:
"Files are injected to the root of the OS drive (C:\ldprovision) and commands are added to the appropriate files such that they are run during the mini-setup just prior to booting into the target OS."
"The unattend.xml is modified and commands are added to call ldprovisioning.cmd from the C:\ldprovisioning directory"
"Sections are added to the unattend.xml in the Specialize section. This is a special section of the unattend.xml that can also be used for things like setting the home page for Internet Explorer, etc. In this section, RunSynchronousCommand action is added calling ldprovisioning.cmd from C:\ldprovisioning\."
This all leads me to believe that the CTOS part of the template will make ALL necessary changes to affect the launching of the provisioning agent once the system has booted into the new OS. Said another way, I should not have to change anything-I just need to confirm that CTOS is in the template at the end of the Post-OS Installation portion of the template. <- Please confirm this assumption.
It also describes the CTOS action as this:
When run, ldprovisioning.cmd installs the basic LANDesk CBA agent in C:\Program Files\LANDesk\LDClient and configures it as a service to start on OS boot. It also modifies the actions.ini file in C:\Program Files\LANDesk\Shared Files\cbaroot to contain a line pointing to C:\ldprovision\ldprovision.exe with the needed command line options. The actions.ini file is used by the LANDesk CBA agent as instructions when starting, so the commands contained therein are run when the service starts
I have verified the presence of the ACTIONS.INI file in the appropriate folder, however the references to C:\LDPROVISION do not exist in the INI file.
In further troubleshooting actions, the document suggests 3 things for Windows 7
- Change to C:\ldprovisioning directory. Verify the ldprovisioning.cmd is in the folder and the folder is populated. It should contain over 20 files.
- Verify that the unattend.xml exists in C:\Windows\Panther
- Verify that the commands calling ldprovisioning.cmd exist in the unattend.xml for the platform (x86, amd64, ia64) you have deployed.
These are supposed to be done in WinPE, but my machine has booted into WIn7 already.
#1 can't be validated because the directory doesn't exist after Win7 boots; I can't say if it existed in WinPE
#2 is validated
#3 is validated, sort of; the command is in the unattend.xml doc, but it appears in the middle of the doc rather than towards the end as I expected.
-Any thoughts on where the break down is?