1 of 1 people found this helpful
Yes this is certainly do-able, this is an extract from a SP Install whitepaper that I wrote to provide assistance for our customers to same the LDVPE1 and restore it, the last step talks about a master image:
Protecting your OSD ldvpe1.img changes:
Be sure to back up your ldvpe1.img that you have modified with updated drivers for SATA Drives and NIC cards. You can use these steps to restore the old one post SP5.
In your SP5 core source directory you will find the osd.inf file, the section will show which files have been updated by SP5.
Open your backup copy of ldvpe1.img with Winimage and inject those files listed.
Example from OSD.INF -Execute section:
LANDESK\VBOOT\COPYFILE.EXE %CORE_PATH%\LANDESK\VBOOT\LDVPE1.IMG" "%CORE_PATH%\OSD\UTILITIES\RunBatch.exe" LDCLIENT\RunBatch.exe(WAIT),60000
In the above example the Runbatch.exe file from the file://..ldmain/osd/utilities directory would be injected into the LDClient dir in the image.
Inject the remaining files listed. And save the new file in file://..LDMain/LANDesk/Vboot
If you would like to create a master Image with all of your typical Drivers included and those not needed removed that can be used to migrate to any core follow these same steps and one more: RUN this command last
UpdatePXEBootImages.exe "c:\program files\Landesk\ManagementSuite" ;;( This assumes that the LANDesk installation is on the C drive)
This step will update the .0 certificate file in the image and changes the all.reg to point to the correct Core Server.
thank you for your answer. I'll check my SP5 download tomorrow in office...
But now, I fear I've some questions more
> 1. Inject the remaining files listed. And save the new file in
Which files must be injected, all files in Excecute-Section of osd.inf? What is the cause? Are they injected after installing SP5 on core too? (this is planned for the next week on the cores )
> RUN this command last UpdatePXEBootImages.exe "c:\program files\Landesk\ManagementSuite" ;;
Shall I do this on every core after copy the actual "master" to the cores?
My idea was, to store the "master" on a central store and deploy/sync it to the cores and PXE servers (with httpcopy, rsync, robocopy or something else).
If I've made (and verified) changes on the master (add some drivers or tools) I want to copy it to one place and then the rest will run automatic... (sometimes I've dreams... )
Yes those procedures are to restore an old copy to the new core after the SP installation so they dont loose the drivers etc.. In your case all you need to worry about it that all the cores are in the host file,a and all the certs are there, the just replacate as needed. No need to do anything but inject the certs with the command below...
sorry for the question again... I add all certs in one image and all coreserver in hosts file and that's all?
I'll try it after migration to SP5 next week.
Yes I believe that should work nicely