none
Dispensing with Task Sequence Media

    Question

  • We've only had SCCM for a short period of time but we're already making good use of Task Sequences for deploying new systems and performing various other tasks.  So far we've been using USB-based Task Sequence Media and this has worked quite well.

    My question though - is this.

    Is it possible to convert the contents of a USB-based Task Sequence Media into a format which can be PXE-booted?  The aim here would be to be able to PXE boot and from the menu choose the option which would boot into the Task Sequence environment - from here any advertised task sequences could be executed, thus removing the need for USB or CD-based media.

    Is what i'm asking even possible?

    Thanks

    Pete

     

    Thursday, May 20, 2010 8:21 AM

Answers

  • You just have to set up a PXE service point (on WDS server) and distribute the x86 and x64 bootimage to it. The client will retrieve available advertisements based on it's collection membership. You will be able to select between different tasksequence if there are multiple optional advertisements available for a client (MAC address).
    • Marked as answer by Peter J West Thursday, May 20, 2010 2:48 PM
    Thursday, May 20, 2010 10:16 AM

All replies

  • You just have to set up a PXE service point (on WDS server) and distribute the x86 and x64 bootimage to it. The client will retrieve available advertisements based on it's collection membership. You will be able to select between different tasksequence if there are multiple optional advertisements available for a client (MAC address).
    • Marked as answer by Peter J West Thursday, May 20, 2010 2:48 PM
    Thursday, May 20, 2010 10:16 AM
  • Thanks for the suggestion Torsten - I think we've almost got it working.

    The machines will now PXE boot but when the client attempts to retrieve the task details we get an error saying 'Failed to run task sequence' and error code 80004005.

     

     

    Thursday, May 20, 2010 1:15 PM
  • smsts.log is the place to look for errors. And the tasksequence related webreports.
    Have you configured a network access account?
    Thursday, May 20, 2010 1:25 PM
  • Thanks Torsten,

    A network access account is already defined and in place.

    When it comes to vieweing the smsts.log file what is the easiest method for doing this?  If the client concerned hasn't received an OS yet (the task sequence we're running is to deploy XP) then we don't have an easy method to view the contents of any files dropped onto the machine.

     

    Thursday, May 20, 2010 1:35 PM
  • You can enable command support http://technet.microsoft.com/en-us/library/bb680515.aspx in the boot image. Open a command (F8) when the TS fails. You can then launch notepad.exe to open logs (or put trace32.exe on the boot image).
    Thursday, May 20, 2010 1:50 PM
  • That makes life a lot easier ;)

    The smsts.log file has these entries:

    The request has succeeded. 200 OK TSPxe 20/05/2010 15:00:46 1192 (0x04A8)
    pNext != NULL, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2072) TSPxe 20/05/2010 15:00:46 1192 (0x04A8)
    reply has no message header marker TSPxe 20/05/2010 15:00:46 1192 (0x04A8)
    DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,5010) TSPxe 20/05/2010 15:00:46 1192 (0x04A8)
    Failed to get client identity (80004005) TSPxe 20/05/2010 15:00:46 1192 (0x04A8)
    ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,815) TSPxe 20/05/2010 15:00:46 1192 (0x04A8)
    failed to request for client TSPxe 20/05/2010 15:00:46 1192 (0x04A8)
    Exiting TSMediaWizardControl::GetPolicy. TSPxe 20/05/2010 15:00:46 1192 (0x04A8)

    A little digging around online has thrown up a few people who had similar issues so i'll make a start on working through these.

    Thursday, May 20, 2010 2:16 PM
  • A reboot of the SCCM Server seems to have fixed the problem, although strangely the WDS Service failed to start at boot-time and needed to be given a shove to get it going.

    All working fine now though - any tasks advertised through SCCM appear when PXE-booting the client and run as expected.

    Thanks again for your help.

     

    Thursday, May 20, 2010 2:48 PM