What version of LANDesk are you running with what service pack? You said the agent loads ok but I dont see you even installing it in your template. Look at the provisioing history of this machine and pull up the template there. It will show exactly what point the template errors.
I am running on Landesk 8.8 SP3. I am installing the agent in the sysprep portion of the template. Here is the contents of the sysprep.inf:
FullName=The Midland Company
OrgName=The Midland Company
Command2="net use \\landesk2\ldlogon xxxxxxx /u:mid7000nt\landesk"
Command4="cmd /q /c \\landesk2\ldlogon\wscfg32.exe /F /NOUI /NOREBOOT /DONTSTARTSVCS"
Command5="net use \\landesk2\ldlogon /d /y"
Command6="cmd /q /c del /q c:\ldsleep.exe"
Command7="cmd /q /c del /q c:\ldiscan.cfg"
I looked at the History and it looks like it is either failing on the Copy LDProvision or on Outlook 2007. I have included a screenshot.
history.gif 19.2 K
Try installing the mini-rollup LD-88-07-09. There is suppose to be a fix in there for this issue. if you check your provisioning log you will probably see something like.
ERROR ProvisioningService 8/21/2009 11:18:48 AM : Unable to export the task XML
STARTUP ProvisioningService DEBUGGING 8/21/2009 11:18:59 AM Logging started
VERBOSE ProvisioningService 8/21/2009 11:18:59 AM : GetTaskXML, SIDS:
I would be interested to know if this works for you.
There are a few other provisioning-related hotfixes that aren't included in the rollup. If it's still not working after the rollup open a case with LANDesk to get the other hot-fixes.
That is very interesting to hear Tom. Since I've had a ticket open for over a month because the rollup did not fix my provisioning issue which started after SP3 was applied like other people. So do you happen to know what the other hot fixes address?
The mimi-rollup did in fact contain the patch I was thinking of, but there is another that may be relevent.
PRV-2604088.3 Provisioning is unable to obtain the correct pullcmds snippet for MSI packages. This causes the provisioning task to fail.
Ask support for that patch.
Also, it would be good to see if the issue is with the Outlook package itself. Try removing that one from the template and see if it still fails.
Also on the machine after the failure see if c:\ldprovisioning exists. That tells us if Provisionign resumed after the reboot. If it does exist, grab the ldprovision.log from it. Provisioning is supposed to delete the folder when it exits successfully so you might have to log in as soon as it boots to windows to see if the folder is created before it is removed.
C:\LDProvisioning does not exist after I provision a new machine. Is there anywhere else I can pull the log from? Also, where do I get the rollup. I looked at the landesk patches I have downloaded in Security and Patch manager, but it is not available there. Do I need to contact support to get the rollup?
Maybe I am missing it, but I do not see where you are configuring the OS (Injecting a temp agent). Is this taking place? Also, you are using provisioning. Take the dang agent out of the image. There are far greater risks to having it in there vs taking it out. With provisioning you get to add the full agent as part of the tasks on the fly. You will always get the latest agent this way. It is just best practice.
The last action of "Post OS installation" must be a "Configure Target OS" (CBA injection) action.
The first action of "System Configuration" must be a "Configure Agent" (Agent installation) action. I suggest you to put a reboot action after agent installation.
Be sure that when XP starts network drivers are correctly installed.
Did you apply LD-88-VCUpdate-08-09? This patch broke "Configure Target OS" in all provisioning tasks. We have a ticket open for it already.
no, I haven't applied this patch or the others mentioned yet. I haven't had much time to mess with this as of lately, but I am going to attempt to try some of the suggestions. I will let you know what works or doesn't work and post results and logs.
Looks like it broke our Provising too in our test lab. NO templates get to installing software in the System Configuration part. We get the reboot after adding the provisioning agent but that is it. It was work before, that was the only change.
i've got the same problems with provisioning after patching my Core to 8.8 SP3 + LD-88-Rollup-07-09 now.
I don't get it to work anymore. Everything was fine before installing SP.
Provisioning stops after the "scripted install" action in the "OS installation" part. The "System configuration" part stays untouched.
How can i fix this? This is really a problem here
Thanks a lot ... Dirk
I recieved word last week that they may have a patch ready this week.