I've been doing testing in 8.8 and have sysprep being injected in the Post OS installation right before the Inject Agent Files/Configure OS. We are not using Ghost though. When you say you imported the file, do you mean you went to Install Scripts and added it there?
I have also tested injecting the script in the post os section before the CTOS action. It still fails.
What I said I imported the file, I meant the .inf answer file used for the unattended sysprep install. So yes, I went to install scripts and added it there.
http://community.landesk.com/support/message/5100#5100 This thread has a lot of good information you may want to give it a look, I believe there is even a working .xtp file posted there. There is also a link for turning on Logging. If you do not get your answer post the provisioning.log file here....
Great, I will check the link out... I will probably even just post the provisioning log file as well.
Sounds like you probably have some variables set that LANDesk can't seem to parse. Try removing all variables in the sysprep file and replace them with the static information for your particular test PC. If it is successful after that, you can start reinserting the variables until it fails and then you will know where LANDesk is getting hung up.
great advise bnelson. I will try that. That may be the reason the script is failing. I will keep you all updated as I do more testing today.
So I removed all of my variables from the .inf file being injected for sysprep and it is still failing. I am not sure if it is failing because it cannot copy the file down or if it is failing because of the script. I am posting both my .inf script file as well as my provisioning .xtp template. Keep in mind that I starred out the areas containing private data.
We had a similar problem. In the end I worked around the issue by creating the image as FAT and not NTFS.
The other thing we had to do was have
in the sysprep under Unattended and ensure this directory exists on the system before imaging.
My next problem is to extend the partition to fill the disk.
Using sysprep options:
Does not work and neither does the PARTITION action..
I have tested the template after adding the InstallFilesPath to the script and it still fails. It seems as though it is failing to copy the script. Creating the images as FAT instead of NTFS is not an option for us since all of our images have already been created.
I had the same issue... As ever found that a workaround is much quicker to come by than a fix!
I used a Copy File command instead of the traditional Inject Script command - told it to copy the .ini from the LDMain\landesk\files folder (from which I originally injected the script into Provisioning anyway) instead of injecting said script.
Workaround worked. Yes, it accepts that injecting scripts doesn't work on this core, but I've found that at the end of the day, so long as it can do what we need, it matters little how it does it!!!
Your inf still has the %computername% wild card. Try removing that and put a * in it's place.
GREAT!! Thanks Thats a good work around that I did not think of. I agree, sometimes it is easier to find a work around. I will try that and let you know.
I did not notice that I left that variable there. I will remove it and try again.
Thanks for all of the responses!!
I tried copying the file rather than using the inject sysprep, and the template still fails at this action. I believe that the problem is the copying of the file rather than the execution. I don't know if Ghost is causing problems with the mounted drive or if it is simply unable to copy the file to the folder. I can physically copy anything over to the C:\ drive after the image is done so I don't know where the problem lies. I am going to try using a different utility to blast down the image and see what happens.
I had to go back to having NTFS images...
I also found that I needed to give the PE environment more space. 15 Mb seems to be needed. Don't forget to re-deploy the peboot.img file from the Landesk staging area to the PXE servers
Once this was done I got a different message "Web service responded with an invalid call". - See http://community.landesk.com/support/docs/DOC-2358 for a solution.
After that it still failed to inject. Checking the logs revealed:
2008-05-06 22:34:26(1800-1808) InjectScriptHandler.exe:Could not move X:\ldprovision\000043_15.cfg to c:\sysprep\sysprep.inf
Checking the c: drive explained the reason. There was no c: drive It looks like the inject part does not work unless the partition is mounted. When using FAT it seems the partition is available but not when using NTFS.
I found that I needed to add a partition action before the inject. Add action, Give name, type - Partition. Action Type - Mount, Disk: 0, Partition id: 1, Logical drive letter - c:. Once that was done the inject seemed to work.