wimboot - sccm tsbootshell.exe
|
2017-11-20, 14:04
Post: #3
|
|||
|
|||
RE: wimboot - sccm tsbootshell.exe
thanks so much for this -
I got it working with this: HKLM\SYSTEM\CurrentControlSet\Control SystemStartOptions " MININT RDIMAGEOFFSET=8192 RDIMAGELENGTH=3161088 RDPATH=NET(0)\\SMSIMAGES\\SS10010B\\BOOT.SS10010B.WIM" and this one HKLM\SYSTEM\CurrentControlSet\Control FirmwareBootDevice "ramdisk(0)" the TsBootClient also had complaints about missing values at HKLM\SYSTEM\CurrentControlSet\Control\PXE so I copied these. im not convinced it actually does anything with the DHCPServerACK and BootServerReply values other than uses these to satisfy itself that it was a PXE boot. for the benefit of anybody else reading, these registry entries are bundled into a fix.cmd script and this is called by modifying the \windows\system32\winpeshl.ini to call this before firing up the agent. [LaunchApps] %SYSTEMDRIVE%\windows\system32\fix.cmd %SYSTEMDRIVE%\sms\bin\x64\TsBootShell.exe finally I have these files present in the boot image by injecting them using wimboot. :wim0010B set winpeurl ${rooturl}/winpe kernel ${winpeurl}/wimboot initrd ${winpeurl}/sources/SS10010B/fix.cmd fix.cmd initrd ${winpeurl}/sources/SS10010B/winpeshl.ini winpeshl.ini initrd ${winpeurl}/boot/bcd BCD initrd ${winpeurl}/boot/boot.sdi boot.sdi initrd ${winpeurl}/sources/SS10010B/boot.wim boot.wim boot || goto failed thanks again for the help! Regards Muzz |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
wimboot - sccm tsbootshell.exe - muzz - 2017-11-16, 18:59
RE: wimboot - sccm tsbootshell.exe - NiKiZe - 2017-11-16, 20:01
RE: wimboot - sccm tsbootshell.exe - muzz - 2017-11-20 14:04
RE: wimboot - sccm tsbootshell.exe - NiKiZe - 2017-11-20, 18:22
RE: wimboot - sccm tsbootshell.exe - muzz - 2017-11-27, 19:53
|
User(s) browsing this thread: 1 Guest(s)