Please check these common issues:
Is the LDprovision map existing on c:\
Are your correct network drivers loaded when booted to windows?
Can you ping the core server?
Maybe there is a Windows Firewall issue?
Also, did you just put in a Reboot or the Configure Target OS action? CTOS should be the last action in WinPE that will initiate the passthrough of the ldprovisioning to Windows and reboots.
I just put in a reboot, ok i will add the CTOS then.
Dont forget, CTOS INSTEAD of the Reboot in PostOS configuration!!
Ok i don't forget ;-)
After checking, i don't have the LDprovision map on c:\, and i have choose CTOS instead reboot but always the same...
After reboot, i have the CRTL+ALT+SUPPR invite and no more....
Is your image sysprepped? If not, this omission is the exact cause of the problem. A reboot action (as Frank said) will not tell LDProvision to continue after the reboot. The CTOS action will allow provisioning to continue into Windows ONLY if the deployed Image is sysprepped before capture and a sysprep answer file is present on the PC (c:\sysprep\sysprep.inf for XP) when it runs. It does this by modifying this Sysprep file to add a number of RunOnce commands to Windows to force LDProvision to run again and continue the task.
In short, ensure your Image is sysprepped, or you'll get this problem every time.
1 of 1 people found this helpful
Sounds like you are getting pretty close with the help you have had. It might be worht you taking a look at this article as well to see information about Best Known Methods and some sample templates. I have used these in the past and while they are not perfect they are good to show the different sections and how they should be used.
LANDesk Silver ESP
The One-Stop Shop for LANDesk Enhancements
I am having an issue when provisioning the pc the name changes. LANDesk already has a good name but after image loads and syspreped it takes a different name something and mac address. Can you point me in the direction to correct this?
This one looks like either an omission in your Sysprep answer file, or a provisioning variable that is pointing at the wrong DB value. If you can post your answer file (remove passwords, XP key etc first) I can look for the common faults
For me the biggest problem with sysprep action is that you can not run it, as much as you could need it. For windows XP you can ran only 3 times. So sometime, you need to create again your master image. That is the reason why I choose to create one master without sysprep it. When I deploys the master on a new computer, I copy all the files I needs to run the sysprep, then I executes "Configure OS" action, and then, after the first reboot, I launch a batch file running the sysprep in the startup folder. When it is done, the computer reboot itself. Then I can install the Landesk agent, and then I can install as many softwares I needs.
By this way, we have one master per computer type, with windows only, and we just update it when we need. As all the provisionings templates use the same method, changing one package, or one file, will update all the templates using it, without modify all the templates. It is easy to use, and a fully updatable.