Hi,
I'm somewhat lost with this one, when I PXE boot a HP ProOne 440 G5 AIO Computer the sequence is set to discover that its that model and implement the task sequence called HP 440 G5 AIO, now looking at the issue it appears the sequence is looking for this name with package ID PS500005, when i look in the task sequences in SCCM there is a package named HP 440 G5 AIO but its package ID is PS500095,I believe that this is why the task sequence then fails.
I have done some digging through SCCM, I have a windows 10 task sequence that is set to look for the new HP BIOS package ID, this references a task sequence called TALLIS-HP BIOS, TALLIS-HP BIOS links to a HP-BIOS source folder and a hidden config pointing towards HP Config64.exe.
Looking at the device collection the HP computer is in that references a task sequence called HP 440 G5 AIO (the same name as the one that fails), this references another sequence called HP ProOne-440-G5 Bios and that's linked to a package called HP ProOne-440-G5-AIO-213.
HP ProOne-440-G5 Bios also links to the TALLIS-HP BIOS task sequence.
I removed and re-added the task sequence link in the device collection but that didn't make a difference, I'm now leaning towards the MDT creation, anyone know how i can update the package ID?
Exact steps:
PXE Boot = Working
WinPE = Working
WinPE Task Sequence password = Working
Confirmation - the requested task sequence will be run:
HP ProOne-440-G5-BIOS
Click Next
Next Message:
Failed to run task sequence
This task sequence cannot be run because the program files for PS500005 cannot be located on a distribution point.
I'm somewhat lost with this one, when I PXE boot a HP ProOne 440 G5 AIO Computer the sequence is set to discover that its that model and implement the task sequence called HP 440 G5 AIO, now looking at the issue it appears the sequence is looking for this name with package ID PS500005, when i look in the task sequences in SCCM there is a package named HP 440 G5 AIO but its package ID is PS500095,I believe that this is why the task sequence then fails.
I have done some digging through SCCM, I have a windows 10 task sequence that is set to look for the new HP BIOS package ID, this references a task sequence called TALLIS-HP BIOS, TALLIS-HP BIOS links to a HP-BIOS source folder and a hidden config pointing towards HP Config64.exe.
Looking at the device collection the HP computer is in that references a task sequence called HP 440 G5 AIO (the same name as the one that fails), this references another sequence called HP ProOne-440-G5 Bios and that's linked to a package called HP ProOne-440-G5-AIO-213.
HP ProOne-440-G5 Bios also links to the TALLIS-HP BIOS task sequence.
I removed and re-added the task sequence link in the device collection but that didn't make a difference, I'm now leaning towards the MDT creation, anyone know how i can update the package ID?
Exact steps:
PXE Boot = Working
WinPE = Working
WinPE Task Sequence password = Working
Confirmation - the requested task sequence will be run:
HP ProOne-440-G5-BIOS
Click Next
Next Message:
Failed to run task sequence
This task sequence cannot be run because the program files for PS500005 cannot be located on a distribution point.
Last edited: