This is a brand new core server with LANDesk SP2 installed. We do have a case open but I wanted to post this to the community to see if anyone else has seen this.
HII runs normally and is sucessfull then CTOS fails with the following erro from the log:
2014-04-29 22:40:13(1512-1992) ldProvision:********* Begin an action - Configure_target_os
2014-04-29 22:40:14(1512-1992) ldProvision:Do EnvironmentCheck
2014-04-29 22:40:14(1512-1992) ldProvision:Is WinPE Action=1, Is WinPe Environment=1
2014-04-29 22:40:14(1512-1992) ldProvision:Report might reboot status to core.
2014-04-29 22:40:14(1512-1992) ldProvision:Call web service SetActionStatus()
2014-04-29 22:40:14(1512-1992) ldProvision:Start TryallWebService Attempt:0.
2014-04-29 22:40:14(1512-1992) ldProvision:End TryallWebService Attempt:0. ExitCode:0
2014-04-29 22:40:14(1512-1992) ldProvision:Session Data: <variables/>
2014-04-29 22:40:14(1512-1992) ldProvision:Caught exception in main: code=80001800H, file=..\shared\src\ProvisionAction.cpp, line=207
2014-04-29 22:40:14(1512-1992) ldProvision:Call web service GetStatusString()
2014-04-29 22:40:14(1512-1992) ldProvision:Start TryallWebService Attempt:0.
2014-04-29 22:40:14(1512-1992) ldProvision:End TryallWebService Attempt:0. ExitCode:0
2014-04-29 22:40:14(1512-1992) ldProvision:StatusString = An unknown action was specified: {0}.
2014-04-29 22:40:14(1512-1992) ldProvision:Call web service SetActionStatus()
2014-04-29 22:40:14(1512-1992) ldProvision:Start TryallWebService Attempt:0.
2014-04-29 22:40:15(1512-1992) ldProvision:End TryallWebService Attempt:0. ExitCode:0
I seaarched for the file ProvisionAction.cpp on the core and it does not exist
Also, the unattend.xml is at the correct location J:\unattend.xml
CTOS is not creating the directory LDProvision on the J:\ directory
So I thought ok I will put a wait command of 120 seconds before the CTOS command..
It failed also with the same type of error "An unknown action was specified"
I also tried to create an action to Make the Directory J:\Ldprovisioning which gave me the same error as above..
Has anyone seen this and offer a fix??