Video Screencast Help

PXE boot image keeps getting deleted

Created: 28 Nov 2012 • Updated: 05 Dec 2012 | 9 comments
This issue has been solved. See solution.

I have an issue with Deployment Solutions 6.9 where the boot image is deleted for some reason. I imagine that it can only be removed manually by someone. Does DS 6.9 have a log file of all changes being made somewhere to show who's doing this or not? Can this be caused by rebooting the server that DS 6.9 lies on? Something is very fishy.

Comments 9 CommentsJump to latest comment

JHBPJF's picture

If my memory serves me correctly, when I added a new PXE server last time, it did the exact same thing. Looks like someone across the country did the same recently. Anyone experience this, and how do I fix this?

Nelo's picture

This might happen with the PXE manager is not in sync wit hthe PXE server part.  Stop the PXE server (Helper service) then restart the PXE manager service. This should clear up manager.  Start PXE helper service. The PXE image might still need to be deleted once and it should stop from then on.

JHBPJF's picture

What do you mean that the PXE image might still need to be deleted once?

What I've done right now since the image was no longer there on the Shared Configuration was recreate it. I'm going to go ahead and leave it like this since it's working -- but say this happens again. If I stop the PXE Helper Service, then restart the PXE manager service, will the image that was "deleted" reappear?

And is my assumption correct that the image is removed because someone added a new PXE server? If so, is there a way to lock this part of the configuration down?

Nelo's picture

\\dsserver\express\pxe\masterimages  masterimages is the source of truth of PXE images for all PXE servers.

All PXE servers when connecting to the PXE manager will determine to download the shared PXE images and local PXE images if any.

Each PXE image in the images folder has a number, think of it as a version of the PXE image, if this number does not match the one on the masterimages one then it gets removed and a new version of the PXE is downloaded.

the image could get removed if there is an updated one or the PXE configuration is removed.

JHBPJF's picture

I see the one that I know is the one that got deleted. Menuoption 164 -- the only difference I see with this one is that in this folder, there is no BDC folder and validate.sig like all the others.

Is this the reason why it's being deleted, and if so, how do I fix this?

Nelo's picture

ok you do not want to delete menuoption164 out of the MasterImages folder.  If it is under the images folder go ahead and delete it (the whole folfer).

If it is in the masterimages folder. Delete the PXe confifguration from the PXE Configuration tool. Click Save and you should see a progress bar.

Make sure you are not inside the folders either via comand prompt and or Windows Explorer as this might lock files and cause issues.

Good Luck


JHBPJF's picture

Nelo, I want to thank you for all your support and knowledge. I'll go ahead and take a look at this tomorrow. I tried googling the difference between masterimages and images folder, but didn't find anything. Why are there 2 folders with the menuoptions?

The images folder shows what is really depicted as far as I see in PXE Configuration. Is that what it is & masterimages is just everything that has been created? I believe we use to setup individual boot images per PXE server until recently I went ahead and just combined them all into the shared configuration.

Nelo's picture

masterimages is only located where the PXE manager service runs so it has all the PXE configurations.

yes, as far as the second paragraph you are correct. Play with it just ask away if you have questions.


JHBPJF's picture

I just ran a install job, and loaded up the boot menu & found a PXE image that isn't in the PXE Configurator.

I personally don't want to mess with it since our imaging is working, but I feel everything is out of sync.