have you redeployed your PXE reps?
Yes, I redeployed twice thinking that might be the problem.
Just so we are trying to troubleshoot the right process, can you clarify exactly what you mean by 'normal' provisioning and which option you are choosing from the PXE boot menu when you have the problem? Do you mean you select 'WinPE provisioning' and it works but you select 'WinPE Menu' and it doesn't?
It used to be that if the 'LANDesk Management Agent' service was stopped or not installed correctly on the core server you could see this behaviour. The menu would just disappear and nothing further would happen. Could be something to check? Do you see that service installed and running on the core server?
Checked the service on the core and it is running.
By normal provisioning, we can schedule a Provisioning task and drop a computer on it and it works.
Whats not working is choosing Provisioning on the Pxe Boot Menu, it goes to the window to put in username and password then it goes to template window, after choosing a template a window comes up for the provisioning to start but times out and keeps trying over and over for 40 times.
The log file prov_schedule_exe.log says it trys to connect using ip, fails, trys to connect by hostname, fails, ERROR cannot start task for this device.
I can ping it and the ip is correct and the hostname is correct. I can remote control it.(using inspector) Something changed in 9.5.
Does anyone out there use Pxe boot provisioning? If not can you try it on your system and see if yours works?
According to the Startcmd file it installs residentagent but the icons don't show in the console.
Review the log files found in the x:\ldprovisioning folders. It may provide the information you need to determine the cause of the problem. If there is no ldprovision folder on drive X (Machine botted form Windows PE), it is likely an issue with the WIndows PE setup or it cannot communicate via HTTP with the core server.
We do the majority of our imaging using Provisioning after PXE boot and our staff login to gain access to the images they have to install.
I believe sometimes when Provisioning Task fail to start it can be caused by issues with the Scheduler Services Account.
When we upgraded to 9.5 for some reason our Scheduler Service Account was blank, had to go back and add the Service Account.
Hope you find your answer.
Can you open the provisioning template and save it again (not cancel)? The Deploy Image action has been changed from 9.0 to 9.5 and it seems to interfere sometimes with the PXE boot Provisioning if you don't apply the settings for 9.5 while running fine by pushing it.
The log file is kind of useless.
Heres's what is says before failure, also I see it downloads files from a http address successsfully.
Starting background thread to check for tasks
Start Tryallwebservice Attempt 0
End Tryallwebservice Attempt 0 Exit code 0
(repeats the above 40 times)
I checked that and its still good.
I tryed that and it still won't work.
When I had the problem I restarted the Scheduler service and it worked. The other time there was a package in the template that no longer existed and it tried 40 of 40 until I removed that package.
In order to compare it all and make sure that I am in sync with what you are doing I will address how we use PXE deployments.
1) A preferred server is made a PXE rep and placed in a broadcast domain where one of our "satallite tech centers" is located.
2) I create a UNIQUE (DO NOT COPY or CLONE OSD scripts!!) script in OSD and then place that script in the PXE Boot Menu
2b) I run the INSTALL PXE rep script on our target machine
3) A technician boots a PC and then interrupts the boot process to use the NIC to boot from
4) The computer connects to the PXE boot menu and the tech hits F8 and selects the "WinPE Menu" in order to boot the machine to LANDesks WIM
5) The tech selects the appropriate Image to impress on the PC at the menu and the image is deployed to the PC
6) The PC is placed into the domain and the LANDesk agent is loaded onto the new installation
Is this the process which your team generally follows? Escuse the use of a preferred server, please.
I tryed restarting scheduler. I went into the template and made sure all packages were there and image was there saved template and it still fails
What you say is how I pxe boot to do a normal image job. What I am having trouble with is instead of selecting "Winpe Menu" I select "Provisioning".