Ok i have worked out how to do this.
You can edit the main boot images path using the PXEconfig utility on the PXE Rep. This can be told to obtain the sdi and wim files and all other required files from a specified location.
The problem is we would like a preferred server type mechanism to get the main boot.sdi file and boot.wim file from the local share to the machine being built. While still retaining a central PXE server..
this would get around the boot files being copied over the WAN for all provisioning builds.
i think i need to try and use a variable of some sort but still trying to work out the best way or indeed if this is possible at all.
How could i get the PXE Server to tell the machine to copy its boot files from a local ' preferred' server share?
Anyone done this?
Do you have DFS configured in your shop?
no we dont but it could be an option - trying to avoid active directory but if needs must..
How would it work with DFS? I assume you can add the root into the Base Images path in PXEconfig..
the problem is adding 500 sites to DFS would mean management of that replication - if it had any issues its not just the WinPE data that wont replicate its the errors in AD replication which would impact user accounts / GPOs etc
Is there a way of not using DFS ?
Can you explain how you did this. I am attempting to add another PXE boot choice and want it to start a different boot.wim file then what came with LANDesk. I managed to get the menu item added and it shows up but can't figure out how to point it to the boot.wim file that I want it to use. Thanks in advance.
you can only specify one path in the PXEConfig utility.
Its in there.
You need to Right Click the Boot Server on the left and choose - Configure Boot server
In there you will see a Base Directory for (M)TFTP files
this you can point to any network location. You must have the path after this point to match the path found in
must have exactly the same files in it as your PXE images directory in the same format too.
Hope that helps.
This still only gives you one location for boot files though..
I got that part. I pretty much followed the guide from http://community.landesk.com/support/message/46712#46712
That allowed me to get the additional menu item setup - I called it MDT and created a folder under undi called MDT.
Inside my MDT folder I put my boot.wim file that I want to use but I can't figure out how to change the settings to get it to launch. Inside the pxe config for the files if I just put boot.wim it tacks on the .0 piece, so I have tried a variety of different .0 files and even tried the syslinux piece like the person in the article did. I would prefer not to have to go down that road. Any help is much appreciated.