I started working with LANDesk about 8 months ago and started provisioning machines about 6 months ago. When I first started with it I just followed the templates that were out there for LDMS 9 SP3 and didn't make many changes at first. During this time when I would schedule a prvisioning task and turn a machine on it would automatically begin the provisioining process without having to press the F12 key. These were all machines that had been on our network before and we always configure the BIOS to network boot last in the boot order, yet they still automatically PXE booted if they were in a scheduled provisioning task.
I had to stop working on this for about 3 months and have really just gotten back into it since about the first of the year, and now machines will not PXE boot without physically forcing them with F12. I have no idea what has changed. I'm the only person that deals with this part of LANDesk and I didn't make any changes as far as PXE reps or anything else goes and honestly the other two people that work with LANDesk with me don't even use it yet, so I'm fairly confident that neither one of them made any changes. The only changes I made are I finally nailed down how to get the "golden image" captured and set up the way we need it, I now have a detailed unattend file that runs, and we just upgraded to 9.5 a couple of days ago, but the problems started well before the upgrade. I use the same provisioning script, same reps, etc that I've been using from the beginning. The problem is, now we are getting ready to do a mass reimage of about 1000 machines to upgrade from XP to Win 7, and there is no way that we can touch every one of them to change the BIOS to configure network boot as the first boot option, as I work in a very small department. We would also like to be able to provision machines when we get them straight out of the box and only have to hook them up to the network and power them on and off they go. I already use the csv file to import all of the machines I'm going to image rather than doing them one at a time. I even use it for single machines, seems to work better for some reason.
I'll be the first to admit that when I started working with LANDesk I had never even heard of it and was pretty much told "Here Learn how to use this and start working with it". In our training provisioning isn't something we focused very much on either, so I don't really have a granular understanding of how exactly it works and haven't been able to find any explanations that have helped, at least not as far as my issue described above is concerned.
One thing that popped into my head as I was writing this is I used a boot.wim that I pulled off of a windwows 7 disc and I'm not sure if that is the one that was being used before. I remember reading about there being one on the LANDesk core and maybe that one is "special" for this purpose.?.
I should probably also add that we are a HP shop and use the mid-enterprise level HP models; the 6200 pro sff is our highest model desktop and the 4530s is the highest laptop model.