With LDMS 8.8 SP2 I'm using italian sysprepped images too and I haven't this issue.
1) How are you deploying your image? Remember that using block-based imaging tool you need to restart your pc before be able to read/write something from your FS.
2) I'm not sure but I remember that LD files will be written on %programfiles%\LANDesk during minisetup by the .cmd file added to cmdlines.txt
Are you sure that the cmdlines path specified in sysprep.inf file exists?
Make a copy of "LDProvision.com" (launched by cmdline.txt during mini-setup sysprep) and check if the line "VCredit_86.exe" is present.
If not, this is a bug reported to landesk support.
Install "VCredit_86.exe" on your Master can be help you...
Maybe Thomas means "ldprovision.cmd"....
Sorry it butt in, We just upgraded to 8.8 SP2 and I am trying to get the agent to install. How do you get the agent to install? I have added it as a step in the post OS part of the template.
Hi, after many tests i resolved the issue:
The termplate i created was correctly built but it defects in one thing:
1)OS Installation - deploy image action : sysprepped XP image (LANDesk img) OK
2)Post OS Installation - inject script action : sysprep.inf in C:\sysprep\sysprep.inf (inject script action need to be here in Post OS Installation) OK
3)Post OS Installation - Configure Target OS action : i call it ldprovision the action isert the provision agent and need to be inserted as the last action of Post OS Installation because it includes a reboot. Note that, as sysprep.inf, the provision agent must be inserted before the first reboot after deploy image because when the new OS boot you need to speak with it via Provisioning agent. _Here i had the issue**_
4)Configure OS - here you can insert quite all kind of actions first i suggest LANDesk Agent and then other software OK
***= When i configure Bare Metal device in console i add a device: Mac address and device name for example PC01; in the configure targte OS action for the provision agent i check to use Device ID already present in Database so when the template works it takes the device ID for PC01 but in the ssysprep.inf i choose to assign another PC name (PC02) so provision agent cannot install because it found a different machine. It was easy bu i did not know!!
I hope it is helpful, it has been for me!
what did make the name in the sysprep.inf? %ldDeviceId%