K2000 - How to Deny PXE Boot after initial Successful PXE Boot
We have recently purchased the K2000 and are trying to setup a Windows 7 Deployment using scripted install, and we are close to completion. We are going into the PC's to install to, and changing the primary boot to PXE instead of a temporary PXE boot because we are currently going through a transition/acquisition phase in the company and have to re-image every PC in the business. It is easier to just touch each PC to change the primary boot to PXE, shutting them down until they are all done, then booting each up to do batch installs, easier monitoring. Is there a way inside of the Kace appliance that will deny a PXE boot at the PXE boot screen after the initial successful PXE boot? This would help in the process of deploying these installs as the PC has to reboot numerous amount of times, and not having to press escape at each PXE boot attempt afterwards would be beneficial.
Community Chosen Answer
If your workstations are dells, you can change the PXE boot to hdd first as a post install task via the cctk. And use the k1000 to change the boot back to pxe first when needed via cctk.
We do a WOL, push k1000 script to the needed machines, force an update, and the machines take off and do the assigned task in the k2000. It Staff shows up about 1-2 hours later(time depends on how many rooms are imaging), the machines are joined to the domain and logged in waiting to get pushed any other needed software and then deepfreeze.
We push a 17-25 gig image to 30-100 machines at one time so this causes the image time to vary, we usually just check the image deploy log to see when they finish.
K2000 post bat