Actually it doesn't automatically replicate on its own. When you update the boot.wim file, it will need to be copied out to your pxe reps or you can redeploy the pxe reps all at once but that's a bit unnecessary in my opinion. A simple script to copy the file would be ok. This would be a good enhancement request.
At the very least, if I'm concerend about replicating out a bad file, it should prompt me if I want to replicate out the changes after saving additional drivers, auto-backup the old file, and then replicate out.....
WIll validate as I got conflicting answers on the auto-replication via another source. If your correct, I'll mark yours as the answer.
1 of 1 people found this helpful
Yeah as far as I know it doesn't replicate on its own. I do agree that this functionality should exist but I haven't seen any evidence of that.
HA, unless both of us are working in a broken state.
I'm waiting to get confirmation from our TAM, he is out on site today, so expectedly slower to respond then normal and I already have his backup chasing down other issues.
thats a really good enhancement request! but my LANDesk server does not do such a thing. Whenever I update drivers to my boot.wim or change the wallpaper or do any type of modification, it just saves it back to the default location which is C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot
I then have 2 choices to replicate it out to my PXE reps. I can redeploy the PXE Deployment script on all the PXE servers, which uninstalls, reinstalls the PXE applications including the boot.wim or I can just manually copy the file to \\pxeserver\c$\Program Files\LANDesk\PXE\System\images\boot
Here is a script that will help you deploy to your PXE reps
"Updating WindowsPE Image
Any time that a driver is added to the WinPE image, or the WinPE image is modified in any way, those changes have to be transfered to all PXE representatives. Normally this is done by simply re-deploying the PXE representatives."
Got my vote