you are talking about two different things in your request.
Do you want to know how to CAPTURE (Create) an image in provisioning?
Do you want to know how to DEPLOY an image in provisioning?
I want to know how to create the build the image that i want to deploy!
I think that my template should work, but what are the important steps to build an image!
Install the workstation --> create a sysprep folder ---> ....
what else do i have to look for??
Hi,I just can give you the way but for LD 8.8 SP3I hope that you can retreive informations.And it's in French.Click on the Windows Script Button on the top bar.In the windows, you have to name the scriptGive user domain informationYou have to specify the UNC where you want to save the image and you have to give the UNC where the IMAGEW.EXE isThen you have to save the script, andclick-move the script in the PXE startup menu.
You capture script is done.
Hope i help you.
After do that, you have to launch PXE menu from computer, you choose WINPE menu and when the WINPE image is load, you can see a menu and choose to capture image.
Thanks for this anwser. That brings me a few steps futher.
I found the HII whitepaper by Mike Ybarra und Jan Buelens which looks promising.
I will leave a status after triing!
Trenkel, you mentioned creating a template and provisioning but the screenshots above are for OSD. The only thing that this would help you with is having LANDesk automatically build an XML that you can later import as an action if needed in one of your templates. You could also start off with OSD to create your image but I believe that this would defeat your purpose of wanting to work with provisioning.There have been many users from the community that have posted sample provisioning templates to get you started depending on what imaging type you will be using. Are you looking to use ImageX, ImageW / ImageW2 or Ghost? The two provisioning links below are a great place to start. The first one has an entire section of links for sample templates to start with. We used a sample template for ImageW2 and have customized it to our needs.
OK, I've found the whitepaper as a said above. See attached file!
That almost solved my problem! Everything works fine except the Configure Target OS action!
I think that could be depending an my Sysprep.inf
i've atteched the SysPrep.inf and the error from the provision task.
Does anybody see any mistake in my Sysprep?
1/ Where is your CTOS action in your template ?
2/ Can you translate in english your screen problem ? (and see us click on CTOS action to see problem)
do you have at least C:\sysprep\i386\ created in your image?
even better would be C:\sysprep\i386\$oem$
If the CTOS action is failing and you are still in WinPE, open up a new console and browse to:
and do notepad configuretargetoshandler.log
and it might give you a better understanding of why that action is failing.
The CTOS Action is failing and the client reboots until the screen where you can choose between " Normal Start" or "Safe Mode" and so on!
If I want back to WinPE I have to force the client via Network-Boot!
Is it possible that the CTOS action is running but the cliet couldn't handle with the drivers!
It said that the cmdline.txt is missing but i can not ind any discription about a cmdline.txt in the HII manual!
Is it possible to force LANDesk to write the configuretargetoshandler.log to the target client hard drive so i ccan read it after reboot????
in the provisioning template action properties, there should be a check box that says something like "Stop Processing Template If Action Fails", make sure that is checked and it should halt
So you dont tell us .. It's not CTOS action failing.. If CTOS action failed, your computer stay on WinPE and dont reboot..
So here, in WinPE, your computer reboots et you go on 'normal mode' or 'safe mode'...
You probably have a blue splash screen with 0x...007 and your problem is AHCI drivers..
No drivers create blue splash screen, exept the disk controller drivers...
Go on BIOS and search from controller mode.. You must have AHCI, or SATA emulation.. Change this with 'IDE' and save and try to boot.
If thats working you dont comply the HII document and AHCI section. You must have a folder 'MSD' with your controller drivers : iaStor.sys, iaStor.inf and a reg file with definition of controller to load it begin of boot sequence.
Try this and tell us
OK I will try this tomorrow
Thanks for so long....